hi folks, the scenario is like below
- have Enterprise security (ESS) in Splunk cloud + ESCU (content updates) as part of it
- if we enable a ESCU detection it works all good.
- we need to modify the ESCU slightly with a standard field and also the name of the search to fit existing organisation policy
- The uuid remain the same
What will happen when the next ESCU update comes?
Hi @koshyk
Are you currently using the rules from ESCU without modification at all (e.g. just enabling the search)?
If you make changes to the ESCU rule/search then the changes will be applied to the ./local/savedsearches.conf on your Splunk deployment. These changes will not be overwritten with future changes to the published ESCU app, however note that this could have the opposite effect as changes made to resolve issues might not take affect.
Only the modified keys will be updated in savedsearches.conf - so if you modify the actual search then future changes to the search from ESCU will not be applied.
A lot of users opt to clone the ESCU rules and apply their organisation name as a prefix to the rules, this means they can always compare between the current and their custom ESCU rule.
There is also an app on Splunkbase (ESCU Companion App) which looks like a good way to monitor changes between cloned rules and the current ESCU definitions.
🌟 Did this answer help you? If so, please consider:
Your feedback encourages the volunteers in this community to continue contributing
THANKS for the ESCU companion app hint. That's quite a good idea alongside an automatic merge concept I'm developing and producing a report for Analyst what to do. thanks for that and will mark as answered
Hi @koshyk
Are you currently using the rules from ESCU without modification at all (e.g. just enabling the search)?
If you make changes to the ESCU rule/search then the changes will be applied to the ./local/savedsearches.conf on your Splunk deployment. These changes will not be overwritten with future changes to the published ESCU app, however note that this could have the opposite effect as changes made to resolve issues might not take affect.
Only the modified keys will be updated in savedsearches.conf - so if you modify the actual search then future changes to the search from ESCU will not be applied.
A lot of users opt to clone the ESCU rules and apply their organisation name as a prefix to the rules, this means they can always compare between the current and their custom ESCU rule.
There is also an app on Splunkbase (ESCU Companion App) which looks like a good way to monitor changes between cloned rules and the current ESCU definitions.
🌟 Did this answer help you? If so, please consider:
Your feedback encourages the volunteers in this community to continue contributing