Section 15
Metrics
Do it in the browser Check coverage and alert load
Remember
- Define each metric once, and treat a change to a definition as a release.
- Report robustness-weighted coverage beside the raw detection count.
- Measure precision for each detection against that detection's own floor.
- The incident detection rate is the share of confirmed incidents a live detection caught first.
- Ingestion delay and the schedule set the floor under detection latency.
The program measures its health with 31 metrics. Each has one definition and one owning stage, except the 15 that belong to the program as a whole: robustness_weighted_coverage, incident_detection_rate, silent_source_hours, priority_technique_gaps, misses_by_cause, open_detection_fixes_age, false_close_rate, time_to_scope_hours, time_to_contain_minutes, notifications_on_time, playbook_coverage, playbook_minutes_saved_per_alert, playbook_actions_unattended, playbook_actions_reverted, and incidents_without_followup. The agent metrics in section 10 sit outside this set. The repository produces the build-side ones from score.yml and the file layout. The pull request system and the backlog's entry dates supply the durations. The rest come from what analysts record about each alert and the engineering hours logged on each pull request. The definitions are in Appendix C.
The Check coverage and alert load tool opens on a chart that puts the raw detection count beside robustness-weighted coverage. On a 30-detection sample program run through the repository's own metrics code, Execution has the most detections and Credential Access has the most weighted coverage. A detection mapped to more than one tactic is counted under each, so the detection column adds up past 30, and the sample includes two ICS tactics, Evasion and Impair Process Control:
| Tactic | Live detections | Robustness-weighted |
|---|---|---|
| Execution | 7 | 3.2 |
| Persistence | 5 | 3.0 |
| Privilege Escalation | 5 | 3.0 |
| Credential Access | 4 | 3.4 |
| Stealth | 3 | 1.6 |
| Command and Control | 3 | 0.8 |
| Defense Impairment | 2 | 1.4 |
| Impact | 2 | 1.4 |
| Lateral Movement | 2 | 1.4 |
| Initial Access | 2 | 1.2 |
| Discovery | 2 | 1.0 |
| Exfiltration | 2 | 0.8 |
| Evasion | 1 | 1.0 |
| Impair Process Control | 1 | 1.0 |
The coverage numbers answer different questions, so report the one that answers the question asked:
| Number | The question it answers | How it is computed | Where it tops out |
|---|---|---|---|
| Detection count | How many live detections name a technique in this tactic? | One per live detection, counted under every tactic it maps to. | Never. A brittle detection adds to it as much as a strong one. |
| Robustness-weighted coverage | How much evasion-resistant work sits in this tactic? | Each live detection counts as its robustness divided by 5, summed per tactic. | Never. Five detections at robustness 1 equal one at robustness 5. |
| Weighted share | What share of the matrix is covered, and how well? | Each technique scores its strongest live detection's robustness divided by 5, averaged across every technique. | 100%, when every technique has a detection at robustness 5. |
| Covered count | How many techniques are covered at all? | A technique counts once its strongest live detection is at robustness 4 or 5. | The technique count of the pinned ATT&CK release. |
Both per-tactic numbers keep growing, which is what makes a bare detection count easy to inflate. Both per-technique numbers cap at the matrix, so a weighted share of 40% is a figure a board can compare quarter to quarter. The ATT&CK coverage workbook lists every Enterprise ATT&CK 20.1 technique and sub-technique and computes all four. The site's coverage app runs the same rules in your browser, keeps your team's data on your own machine, and exports to Excel, PNG, or PDF. It also reads the log sources each of ATT&CK's analytics names. A technique counts as ready to build only when one analytic has every log source it reads collected. From that the app reports which uncovered techniques you could build today, which have some of the telemetry, which are blind, and which log source would make the most of them ready. For every technique it also says how many of the detection library's open-source rules are tagged with it, and links to them.
On this page
15.1Checks from outside
Four of the site's claims are checked against something other than its author, and the numbers are republished with each run. MITRE's own ATT&CK library reads the same STIX bundle the site parses; on 2026-11-06 the two agreed on every technique, platform, analytic, and data component in ATT&CK 20.1. D3FEND's own API returned the same count of defenses as the coverage map for 5 of the 5 techniques checked on 2026-10-20. The library's robustness draft is run against the 72 SigmaHQ rules that MITRE's CTID scored by hand for Summiting the Pyramid. It matches the hand score on 55 and stays at or under it on 66. The library's Windows Sigma rules run against 107 recorded attacks from OTRF's Security-Datasets; of the 1,695 rules with a recording of their technique, 139 fired on it. The site's evidence page lists what each check shows, what it doesn't, and which claims remain opinion: the score model, the lifecycle's numbers, the maturity levels, and the ceilings.
15.2Performance and risk
A KPI says how well the program does its work, and the team sets a target for it. A KRI says how exposed the program is, and the team sets a tolerance for it: the level at which someone has to act. The tolerances here are defaults to replace once a quarter of the team's own numbers exists. Of the 31 metrics, 10 are KRIs:
| KRI | Amber | Red |
|---|---|---|
detection_latency_median |
over 15 minutes | over 60 minutes |
rule_debt |
over 10% | over 20% |
silent_source_hours |
over 4 hours for a source behind a live detection | over 24 hours |
priority_technique_gaps |
over 20% | over 40% |
misses_by_cause |
the same code twice in a quarter | the same code in two quarters running |
open_detection_fixes_age |
over 30 days | over 60 days |
false_close_rate |
any confirmed wrong close in a quarter | a wrong close on a detection rated impact 4 or 5 |
notifications_on_time |
any internal notification late | any regulator or customer deadline missed |
playbook_actions_reverted |
any reverted action in a quarter | a reverted tier 4 action, or a refused close on an impact 4 or 5 alert |
incidents_without_followup |
any incident in a quarter | the same responder twice, or any incident in two quarters running |
Section 19 adds ai_false_close_rate as a KRI for a program that lets an agent close alerts. The quarterly report lists every KRI against its tolerance, red ones first.
15.3ATLAS and D3FEND
ATT&CK covers attacks on hosts, networks, identities, and cloud services, and two other MITRE knowledge bases extend it. ATLAS 2026.09 lists 120 techniques and 88 sub-techniques against AI systems, and 44 of the 208 are adopted from ATT&CK. ATLAS names no log sources, so the coverage map can't score its techniques. A score.yml accepts an ATLAS id beside an ATT&CK one, and the kit checks both. ATLAS ties 48 of its techniques to a mitigation that, by this site's reading, detects an attack in progress, most often AI telemetry logging, which records a deployed model's inputs and outputs. Collect that log first, because a detection for prompt injection or for exfiltration through an inference API has nothing to read without it. ATT&CK 20.0 added direct and indirect prompt injection too, and a detection for a technique both list carries both ids.
D3FEND 1.6.0 links 387 current Enterprise and ICS techniques to the defenses that counter them, through an artifact both touch, such as a process, a file, a network flow, or a credential. Of the 156 defensive techniques it links, 56 detect. The coverage map lists those for each technique by the artifact they analyze, so a hypothesis can start from a named analysis such as process spawn analysis. D3FEND 1.6.0 maps to ATT&CK 19.0. The extract moves the 22 ids ATT&CK has since revoked to their replacements, and the techniques ATT&CK added after 19.0 have no D3FEND links yet.