Duplicate risk notables are triggered unexpectedly under Incident Review page

Available Languages

Updated:September 29, 2026
Document ID:SPLK047064

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Applicability

Splunk Enterprise Security Splunk Cloud Splunk On Premise

Description


Under app Enterprise Security > Incident Review, more than one risk notables were displayed for the same risk object in a 24 hour period, for example, splunktest@domain.com. 

6:02PM - Notable #1

10:12PM - Notable #2

However only one notable should be triggering in a 24 hour period for the same risk object.

 

notable.png


Investigation

To investigate what is happening:

1.Review the notable trigger condition by expanding the notable and click on the search link under "Correlation Search"

 

Correlation Search.png

 

2. Review "Time Range", "Trigger Conditions", and "Throttling" sections, for example:


Condition.png 

 

3. In this case, the conditions define that a new notable will be triggered in a 24 hour period when the below field group combination changes:

normalized_risk_object
risk_object_type
source_count
mitre_technique_id_count
mitre_tactic_id_count
 
4. Next, open "Risk Event" page to investigate further by clicking on the number under "Risk Events".
 
notable.png  
In this case, notable #1's "Risk Event" displays one event at 5:34 PM:
 
first.png
 
Notable #2's "Risk Event" displays 5 events:

second.png 
Noticed the same event at 5:34PM triggered both notables. The reason is because a new risk rule "Risk Rule 2" triggered at 9:58PM, so notable #2 now consists of two risk rules (source_count=2) with a new field group combination:
 
Notable #2:
normalized_risk_object = x
risk_object_type = x
source_count = 2
mitre_technique_id_count = x
mitre_tactic_id_count = x
 
Notable #1:
normalized_risk_object = x
risk_object_type = x
source_count = 1
mitre_technique_id_count = x
mitre_tactic_id_count = x
 
5. Use correlation search to confirm the behavior. To review above field groups for the notables in question, open up the correlation search query and add the necessary filtering logic. For example in this case, add: 

 

| search risk_object="*splunktest@domain.com*"

 

So the complete query may look like:


| tstats `summariesonly` mode(All_Risk.risk_object) as risk_object, sum(All_Risk.calculated_risk_score) as risk_score, count(All_Risk.calculated_risk_score) as risk_event_count,values(All_Risk.annotations.mitre_attack.mitre_tactic_id) as annotations.mitre_attack.mitre_tactic_id, dc(All_Risk.annotations.mitre_attack.mitre_tactic_id) as mitre_tactic_id_count, values(All_Risk.annotations.mitre_attack.mitre_technique_id) as annotations.mitre_attack.mitre_technique_id, dc(All_Risk.annotations.mitre_attack.mitre_technique_id) as mitre_technique_id_count, values(All_Risk.tag) as tag, values(source) as source, dc(source) as source_count, values(All_Risk.risk_object) as all_risk_objects, values(All_Risk.cim_entity_zone) as cim_entity_zone from datamodel=Risk.All_Risk by All_Risk.normalized_risk_object,All_Risk.risk_object_type | `drop_dm_object_name("All_Risk")` | eval "annotations.mitre_attack"='annotations.mitre_attack.mitre_technique_id', risk_threshold=100 | where risk_score > $risk_threshold$ | `get_risk_severity(risk_score)`
| search risk_object="*splunktest@domain.com*"
 
The fields will display as below for review:
 

risk datamodel.png

 


Resolution

Following above troubleshooting steps, the behavior of triggering two notables for the same risk object is expected in this case.


https://docs.splunk.com/Documentation/ES/7.3.2/RBA/HowRBAWorks

Revision History

Revision Publish Date Comments
1.0
29-Sep-2026
Initial Release

Was this Document Helpful?

FeedbackFeedback

Contact Cisco

This Document Applies to These Products