Splunk Enterprise Security

Why not getting Notables?

timsheets13
Loves-to-Learn

I'm new to ES.  I have taken the ES Admin course so I probably shouldn't have to ask for help but I'm pulling my hair out.

I have a linux host running sshd, no firewall.  This host has the universal forwarder sending events to the index cluster.

I have another linux host running a brute force attack against it.

Search in Splunk clearly shows the failed attempts, thousands of them.

In ES, I have enabled the "Brute Force Access Behavior Detected" correlation search, and added a Adaptive Response Action to create notable.

However, even though there are thousands of matching events, I never get a notable created.

SA_AccessProtection app is installed.

Any ideas of how to troubleshoot this, or what might be wrong greatly appreciated.

 

Labels (2)
Tags (1)
0 Karma

tscroggins
Champion

@timsheets13 

Does the "notable" index exist?

0 Karma

timsheets13
Loves-to-Learn

Yes, once I installed the TA_ForIndexers the indexes where all created.

I can create manual notables no problems.  And if I create an alert in Splunk and make the alert action to create a notable, that works.

However, attempting to create a notable based on a correlative search in ES is not working.

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...

Modernize your Splunk Apps – Introducing Python 3.13 in Splunk

We are excited to announce that the upcoming releases of Splunk Enterprise 10.2.x and Splunk Cloud Platform ...

Step into “Hunt the Insider: An Splunk ES Premier Mystery” to catch a cybercriminal ...

After a whole week of being on call, you fell asleep on your keyboard, and you hit a sequence of buttons that ...