Splunk Enterprise Security

Reduce notable events

lucanzano
Loves-to-Learn Everything

Hello, we have created many custom correlation searches in our client's deployed instance. Right now they are creating too many notable events even with the "window limitation". Can somebody help?

Labels (2)
0 Karma

richgalloway
SplunkTrust
SplunkTrust

Consider disabling less-useful correlation searches, especially information and low-priority events.  Re-enable them when the NE volume is under control

Tune the CSs so they only trigger when there is an event requiring attention.

Fix the problems that are triggering the NEs.

---
If this reply helps you, Karma would be appreciated.
0 Karma

lucanzano
Loves-to-Learn Everything

@richgalloway wrote:

Tune the CSs so they only trigger when there is an event requiring attention.


How do I do it?

Thank you for the answer

0 Karma

richgalloway
SplunkTrust
SplunkTrust

It depends on the searches.  Generally speaking, adjust thresholds within the search before triggering a notable event.  For example, instead of triggering when a single interesting event is found, trigger when 3 or more are found within some period of time.

---
If this reply helps you, Karma would be appreciated.
0 Karma
Get Updates on the Splunk Community!

Automatic Discovery Part 1: What is Automatic Discovery in Splunk Observability Cloud ...

If you’ve ever deployed a new database cluster, spun up a caching layer, or added a load balancer, you know it ...

Real-Time Fraud Detection: How Splunk Dashboards Protect Financial Institutions

Financial fraud isn't slowing down. If anything, it's getting more sophisticated. Account takeovers, credit ...

Splunk + ThousandEyes: Correlate frontend, app, and network data to troubleshoot ...

 Are you tired of troubleshooting delays caused by siloed frontend, application, and network data? We've got a ...