- Get Started with Outcomes Navigator
- Use Outcomes Navigator with the MITRE ATT&CK® Framework
- Use Outcomes Navigator with the Threat Detection, Investigation, and Response (TDIR) Use Case Categories Framework
- Use Outcomes Navigator for Compliance
- Use Outcomes Navigator with the OWASP Top 10 for Agentic Applications Framework
- View Recommendations for Improving Your Configuration
- Share Information in Outcomes Navigator
- Outcomes Navigator Coverage Calculation
- The Role of Parsed Fields in Coverage Calculation
- Prerequisites for Calculating Coverage
- Types of Coverage Scores
- Use Case Coverage Score
- MITRE Coverage Score
- Compliance Framework Coverage Score
- Control Coverage Score
- OWASP Agentic AI Coverage Score
- OWASP Risk Coverage Score
- Analytics Rules Coverage Calculation
- Correlation Rules Coverage Calculation
- Advanced Analytics Rules Coverage Calculation
- Dashboards Coverage Calculation
- Coverage Over Time Calculation
- Outcomes Navigator Parser Calibration Tier Average Calculation
Analytics Rules Coverage Calculation
Learn how Outcomes Navigator calculates Threat Detection Management analytics rules coverage for a use case, MITRE ATT&CK® technique, OWASP Top 10 for Agentic Applications security risk, or compliance control.
Analytics rules coverage is a metric of how well your environment is configured so analytics rules can detect a use case, ATT&CK technique, or OWASP Top 10 for Agentic Applications security risk, or meet the requirements of a compliance control. At a glance, you can summarize the strength of analytics rules detection without analyzing the numbers and details yourself.[17]
Defining Satisfied Rules
To calculate analytics rules coverage for a use case, ATT&CK technique, OWASP Top 10 for Agentic Applications security risk, or compliance control, Outcomes Navigator uses analytics rules that can trigger, also called satisfied rules. Outcomes Navigator uses satisfied rules because an analytics rule has coverage only if it can trigger; if an analytics rule can't trigger, then it doesn't provide coverage.
To determine if an analytics rule is satisfied, Outcomes Navigator checks two conditions in the following order:
If the analytics rule has triggered in the last 30 days, it is considered satisfied.
To determine if an analytics rule has triggered in the last 30 days, Outcomes Navigator queries events in Search from the last 30 days where
activity_typeisrule-triggerand compares the returned rule IDs to the analytics rule ID. If the analytics rule is present in the search results, it has triggered in the last 30 days, and is considered satisfied.If the analytics rule hasn't triggered in the last 30 days, Outcomes Navigator checks the analytics rule configuration to determine if the analytics rule could potentially trigger given how your environment is configured. It checks the analytics rule:
applicable_eventsdefinition for four specific event fields:product,subject,activity_type,outcomerequiredFieldsdefinition for the fields that must exist in an event for the analytics rule to trigger.
It then compares these analytics rule fields against the configuration for your enabled parsers. If your enabled parsers are configured to:
Support the defined
productOutput an event of a specific
subject, oractivity_typeandoutcomeExtract the specific fields defined in
requiredFields
the analytics rule is considered satisfied.
Calculating the Score
Your analytics rules coverage score for each use case, ATT&CK technique, OWASP Top 10 for Agentic Applications security risk, or compliance control is the percentage of satisfied analytics rules out of all analytics rules.
The percentage is calculated by:
where P is the percentage, SR is the number of satisfied rules, and ER is the total number of enabled analytics rules.
[17] MITRE ATT&CK and ATT&CK are trademarks of The MITRE Corporation ("MITRE"). Exabeam is not affiliated with or sponsored or endorsed by MITRE. Nothing herein is a representation of the views or opinions of MITRE or its personnel.