CSEC_PUBLIC/securityonion
1
0
Fork 0
mirror of https://github.com/Security-Onion-Solutions/securityonion.git synced 2026-04-26 14:37:49 +02:00
Code Issues Packages Projects Releases Wiki Activity

Remove comments to avoid confusing config viewers within SOC

Browse Source
This commit is contained in:
Jason Ertel
2022-09-13 12:08:19 -04:00
parent d2fc712400
commit d12ff79af0
3 changed files with 5 additions and 43 deletions
Download Patch File Download Diff File Expand all files Collapse all files
salt/soc/files/soc/custom.js
-17
View File
@@ -1,17 +0,0 @@
// Copyright Jason Ertel (github.com/jertel).
// Copyright Security Onion Solutions LLC and/or licensed to Security Onion Solutions LLC under one
// or more contributor license agreements. Licensed under the Elastic License 2.0 as shown at
// https://securityonion.net/license; you may not use this file except in compliance with the
// Elastic License 2.0.
/*
*** WARNING *** WARNING *** WARNING ***
Future upgrades of Security Onion are NOT guaranteed to work
with any content added to this file. Knowing this, it is strongly
suggested to avoid and/or minimize the extent of any
content placed here so that upgrading to newer version of
Security Onion do not become a burden.
*/
salt/soc/files/soc/custom_roles
-23
View File
@@ -1,23 +0,0 @@
# Define custom business role mappings, or remove mappings that come with
# the default SOC deployment.
#
# IMPORTANT: This file should be copied from the salt/default tree into
# the salt/local tree (preserving the same directory structure).
# Failure to do this will result in the customizations being
# overwritten on future upgrades.
#
# Syntax => prebuiltRoleX: customRoleY: op
# Explanation => roleY and roleZ are adjusted permissions of roleX, op is:
# + add the new permissions/role mappings (default)
# - remove existing "explicit" prebuilt permissions. This
# does not work with implictly inherited permissions.
#
# 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: westcoast_analyst, eastcoast_analyst
# roles/read: user-monitor:-