Splunk Enterprise Security

How to create ES correlation search that triggers only when action X is repeated by the same user 20 times in 5 minutes?

Sven1
Path Finder

Thanks in advance for any assistance you can please lend. 

Can someone please tell me how I can configure an Enterprise Security correlation search that triggers only when a specific action is repeated by the same user 20 times in 5 minutes?

Labels (2)
0 Karma
1 Solution

richgalloway
SplunkTrust
SplunkTrust

Bin the events into 5-minute intervals and count the number of events for each user in each bucket.  Keep only the results where the count is at least 20.  Trigger the CS when the number of results is not zero.

<<your search for action X>>
| bin span=5m _time
| stats count by _time,user
| where count >= 20
---
If this reply helps you, Karma would be appreciated.

View solution in original post

richgalloway
SplunkTrust
SplunkTrust

Bin the events into 5-minute intervals and count the number of events for each user in each bucket.  Keep only the results where the count is at least 20.  Trigger the CS when the number of results is not zero.

<<your search for action X>>
| bin span=5m _time
| stats count by _time,user
| where count >= 20
---
If this reply helps you, Karma would be appreciated.

Sven1
Path Finder

richgalloway,

Thank you very much. 

0 Karma
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.


Introducing Unified TDIR with the New Enterprise Security 8.2

Read the blog
Get Updates on the Splunk Community!

SOC4Kafka - New Kafka Connector Powered by OpenTelemetry

The new SOC4Kafka connector, built on OpenTelemetry, enables the collection of Kafka messages and forwards ...

Your Voice Matters! Help Us Shape the New Splunk Lantern Experience

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...

Building Momentum: Splunk Developer Program at .conf25

At Splunk, developers are at the heart of innovation. That’s why this year at .conf25, we officially launched ...