Splunk Enterprise Security

Schedule correlation search not to run during weekly scheduled network scan

adamblock1
Explorer

We are currently running Splunk 5.0.5 together with Enterprise Security 2.4.1.

A weekly Nessus scan runs which triggers the "Brute Force Access Behavior Detected" correlation search when specific authentication attempts are made against Windows hosts. I am interested in tweaking this search so not to run during the time that the scan is running (Friday afternoon between 1600 - 1700).

I added the statement "NOT (earliest=@w5+16h latest=@w5+17h)" to the search, but the same alerts (incidents) were triggered during the time when the scan was running which indicated to me that the statement did not prevent the search from running.

If there is a different/better way to do this, please let me know.

Thank you.

0 Karma

jcoates_splunk
Splunk Employee
Splunk Employee

Hi,

You might be better off rolling back those changes and doing it this way instead.

0 Karma
Get Updates on the Splunk Community!

See your relevant APM services, dashboards, and alerts in one place with the updated ...

As a Splunk Observability user, you have a lot of data you have to manage, prioritize, and troubleshoot on a ...

Index This | What goes away as soon as you talk about it?

May 2025 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with this month’s ...

What's New in Splunk Observability Cloud and Splunk AppDynamics - May 2025

This month, we’re delivering several new innovations in Splunk Observability Cloud and Splunk AppDynamics ...