Splunk Enterprise Security

ESCU and Enterprise Security Incident Review- Why are results inconsistent?

beano501
Explorer

Not sure I am missing something, but the Correlation Searches provided by ESCU are not consistent in their results. Some result is the user being indentified as in a field user_id, some in a field UserID

This is inconsistent (which I could live with), but does not match up to the fields used (by default) to identify users within Enterprise Security - Incident Review. So I need to add them to the "Incident Review - Event Attributes". 

In addition, if I am using Data Enrichment, then I also need to add to "Incident Review - Event Attributes" fields like UserID_email, UserID_bunit, UserID_category, etc....

If the ESCU could have their correlation search return a more "standard" set of fields as results, then it would make things work more "out of the box"

 

I appreciate that I might have missed something obvious, I and I hope I have - I value all replies

Labels (1)
0 Karma

richgalloway
SplunkTrust
SplunkTrust

ESCU is a Splunk-supported app so you can submit a Support request about the lack of CIM support.  If that doesn't work, try https://ideas.splunk.com

---
If this reply helps you, Karma would be appreciated.
Career Survey
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!

Tech Talk Recap | Mastering Threat Hunting

Mastering Threat HuntingDive into the world of threat hunting, exploring the key differences between ...

Observability for AI Applications: Troubleshooting Latency

If you’re working with proprietary company data, you’re probably going to have a locally hosted LLM or many ...

Splunk AI Assistant for SPL vs. ChatGPT: Which One is Better?

In the age of AI, every tool promises to make our lives easier. From summarizing content to writing code, ...