Splunk Enterprise Security

Null value for urgency in incident_review lookup

evelenke
Contributor

Hi Splunkers,

when we save\close notable events without changing the Urgency we get no any value (null) for urgency in incident_review_lookup.
In ES Incident Review view the Urgency is shown and just has initial value (as expected).
Is it possible to get the default value for urgency in lookup in case we want to leave urgency as is?

alt text alt text

0 Karma

nswondem
Path Finder

One of my customers had this situation before and it turned out that the severity was being assigned an unknown value in the correlation search. Take a look at the ES documentation for determining urgency.

https://docs.splunk.com/Documentation/ES/5.3.1/User/Howurgencyisassigned

In the customer's case, the assigned priority was being overwritten in the correlation search. It was being set to a value that was not in the blue or gold sections of the urgency table (see link).

So for example ES expects the Assigned Priority to be Unknown, Low, Medium, High, or Critical. If your correlation search mistakenly sets a field called priority to Informational then ES cannot correctly calculate the urgency. You will get a NULL value.

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!

.conf25 Community Recap

Hello Splunkers, And just like that, .conf25 is in the books! What an incredible few days — full of learning, ...

Splunk App Developers | .conf25 Recap & What’s Next

If you stopped by the Builder Bar at .conf25 this year, thank you! The retro tech beer garden vibes were ...

Congratulations to the 2025-2026 SplunkTrust!

Hello, Splunk Community! We are beyond thrilled to announce our newest group of SplunkTrust members!  The ...