mirror of
https://github.com/Security-Onion-Solutions/securityonion.git
synced 2025-12-06 09:12:45 +01:00
Adjust custom_role examples to be more realistic
This commit is contained in:
@@ -9,12 +9,15 @@
|
||||
# Syntax => prebuiltRoleX: customRoleY: op
|
||||
# Explanation => roleY and roleZ are adjusted permissions of roleX, op is:
|
||||
# + add the new permissions/role mappings (default)
|
||||
# - remove existing prebuilt permissions
|
||||
# - remove existing "explicit" prebuilt permissions. This
|
||||
# does not work with implictly inherited permissions.
|
||||
#
|
||||
# In the example below, we will define a new role for junior analysts,
|
||||
# that is nearly identical to the analyst role that comes with SOC, with the
|
||||
# exception that it removes their ability to obtain details about other
|
||||
# analysts in the system.
|
||||
# In the example below, we will define two new roles for segregating
|
||||
# analysts into two regions. Then we will remove the ability for all
|
||||
# analysts to see the roles of other analysts. (Seperately we will need to
|
||||
# define these two new roles in Elasticsearch so that each analyst region
|
||||
# can only see data from their specific region's indices, but that is out
|
||||
# of scope from this file.)
|
||||
#
|
||||
# analyst: jr_analyst
|
||||
# user-monitor: jr_analyst:-
|
||||
# analyst: westcoast_analyst, eastcoast_analyst
|
||||
# roles/read: user-monitor:-
|
||||
Reference in New Issue
Block a user