On This Page

Home / Cribl Detect/ Build Detections (Preview)/View ATT&CK Coverage

View ATT&CK Coverage ​

Preview Feature ​

Cribl is still developing this Preview feature. We don’t recommend using it in a production environment, because the feature might not be fully tested or optimized for performance, and related documentation could be incomplete.

Access requires App Platform, the Cribl Detect feature, and a Role that grants Apps.Read access to the Cribl Detect app.

Please continue to submit feedback through normal Cribl support channels, but assistance might be limited while the feature remains in Preview.

The MITRE ATT&CK Framework map shows which ATT&CK tactics and techniques your detections cover. Use it to find coverage gaps, see which gaps your data could already support, inspect the detections that map to a technique, and open matching Templates.

The tab label includes the ATT&CK version the map uses, for example MITRE ATT&CK Framework v20.

Open the Map ​

In Cribl Detect, go to Detections > MITRE ATT&CK Framework.

The map is a matrix. Each column is a tactic. Each cell is a technique. Tactic headers show how many techniques in that column are covered, for example 16/22 covered.

Two summary cards sit above the matrix:

CardWhat it shows
DetectionsHow many detections the map is scoring.
MITRE Matrix coverageThe percentage of the matrix that those detections cover. The card name and value change with the coverage view.

Choose a Coverage View ​

Use Show to switch what the matrix measures:

ViewWhat it showsUse it to
Existing CoverageThe detections you already have. This is the default view.See what your current detections cover.
Potential CoverageYour existing detections, plus templates you haven’t used whose Event Readiness is Observed or Likely available.Find gaps you can close now, with data you already collect.
Telemetry GapsTemplates you can’t use yet because your environment doesn’t collect the events they need.Decide which data sources to onboard next.

Potential Coverage and Telemetry Gaps both use Event Readiness to decide whether a template fits your data.

Existing Coverage ​

Each technique cell shows how many detections map to it. An icon marks techniques that also have applicable templates you haven’t used yet. Hover over the coverage card to see the color thresholds.

Potential Coverage ​

The coverage card becomes MITRE Matrix Potential Coverage. Each technique cell shows two numbers as X + Y: X is your existing detections, and Y is applicable templates you haven’t used. Hover over a cell to see both counts.

Telemetry Gaps ​

The summary metric shows the share of templates you can’t use with the events you collect today. For example, if your data supports 1 of 10 templates, the telemetry gap is 90%.

Each technique cell shows applicable unused templates out of all unused templates for that technique. Color runs from red, for the biggest gap, to no color, for no gap.

Read Coverage on a Cell ​

Each technique cell shows:

  • The technique ID and name, such as T1584 / Compromise Infrastructure
  • A count for the coverage view you selected

Expanded sub-techniques don’t show their own counts in Existing Coverage or Potential Coverage. They do in Telemetry Gaps.

In Existing Coverage and Potential Coverage, cell color shows coverage at a glance:

  • Green: the technique is covered
  • Yellow: coverage is partial
  • Red: no detection covers the technique

Sort by Coverage orders techniques in each tactic so higher coverage sits near the top. Standard Map uses the ATT&CK matrix layout.

Inspect a Technique ​

Select a technique to open a details panel. The panel shows the tactic and technique name, and two tabs:

  • Detection Rules (N): Your existing detections that cover the technique. If none do, the tab says No detections cover this technique.
  • Potential Coverage Rules (N): Applicable templates for the technique that your data supports, with a link to Templates filtered to that MITRE path.

Expand a technique to list its sub-techniques. For example, T1584 Compromise Infrastructure expands to sub-techniques such as DNS Server, Domains, and Network Devices.

View Templates opens Templates filtered to that MITRE path. From there you can review Event Readiness and create detections in Inventory.

Filter the Map ​

You can narrow the matrix before you hunt for gaps.

Use the Search Field ​

The search field finds techniques by name, ID, or the detection rule’s condition (the matching expression inside a rule’s definition).

Search forDescriptionExample
NameThe human-readable title of the ruleIf you enter root console, the map narrows to the techniques the rule covers (in this example, T1078.004 and T1110) because that’s the rule’s ATT&CK mapping.
IDThe unique identifier of the ruleIf you enter T1072 or supply chain, the map shows precisely where the detection sits in the matrix. You can also enter partial IDs.
ConditionThe matching expression of the rule, which filters by how the detection works, not what it’s calledIf you enter metadata.product.name, the map shows all detections with rules containing that condition.

Use the Filters ​

Filters opens a panel with:

FilterWhat it narrows to
PlatformsTechniques and detections for a platform, such as Windows, Linux, macOS, SaaS, IaaS, Identity Provider, Office Suite, Network Devices, or PRE.
GroupsTechniques and detections associated with a MITRE group, such as an APT.
CommonalityTechniques by how commonly adversaries use them. This filter appears after you select at least two groups.

You can select more than one platform or group. The detection count, coverage metric, and matrix update together.

For example, filtering to macOS and Linux plus a group can drop the matrix to the tactics that group uses on those platforms. Coverage percentage can rise because out-of-scope techniques no longer count.

Next Steps ​