Skip to main content

Responses are generated using AI and may contain mistakes.

Outcomes NavigatorOutcomes Navigator Guide

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:

  1. 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_type is rule-trigger and 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.

  2. 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_events definition for four specific event fields: product, subject, activity_type, outcome

    • requiredFields definition 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 product

    • Output an event of a specific subject, or activity_type and outcome

    • Extract 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:

Equation 21. 
P=SRER⋅100P=\frac{SR}{ER}\cdot100


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.