DETECT hunt Run and measure

Section 13

Maturity levels

Framework v0.136.0, updated November 17, 2026.

Do it in the browser Score your maturity

Level 0Ad hocDetections exist. Nothing about them is written down in a place a second person can find.
Level 1RepeatableEvery detection has a record and a defined way in. Two people would build the next one the same way.
Level 2MeasuredThe program counts its own work: definitions of done carry numbers, the backlog carries scores, alerts carry outcomes.
Level 3EnforcedMachines enforce the definitions of done. A skipped step fails the build.
Level 4Self-correctingMeasurement drives change: detections retire themselves on evidence and coverage claims can be falsified.
Every dimension is scored on this ladder, and the program sits at the lowest rung any dimension reaches.

Remember

  • Claim a level only for what is true today at that level and every level below it. A pilot counts for nothing.
  • Your overall level is your lowest dimension, never the average.
  • Use evidence someone outside the team could check.
  • Work on the lowest dimension first. The Score your maturity tool lists the dimensions in that order.

The maturity model scores a program at five levels on each dimension: seven for detection, and four for response that a team scores only if it owns response. Your overall level is your lowest scored dimension and never the average, so a strong pipeline can't make up for a missing inventory.

Every cell is an evidence test somebody outside the team could run, so a level is a claim an auditor can check and a self-assessment can't inflate.

Score a level only if every statement at that level and below is true today. A pilot earns no credit. The gap between your lowest dimension and your highest is the work queue.

13.1The dimensions

Detection

Detection dimensions cover how the program finds attacks: what it collects, what it builds, and how it keeps its detections honest.

Dimension The question it answers 0. Ad hoc 1. Repeatable 2. Measured 3. Enforced 4. Self-correcting
Telemetry Do you know what you collect, and do you know within a day when a source stops? No inventory. A source can stop and nobody finds out until a detection is needed. An inventory exists with an owner per source, refreshed at a stated interval. Every source has a measured normal rate, and readiness is scored 0 to 5 on the backlog. The silence alert covers every source in the inventory and fires to a real destination. New detections cannot reference an uninventoried source, and readiness drops automatically when a log source stops.
Backlog and order How is the order of detection work decided, and could you defend it to a skeptic? Order is whoever asked most recently, or whoever asked loudest. A single written backlog exists, ordered by hand. Every candidate carries six scores, six evidence lines, and a computed score. Scores are computed by the pipeline; a hand-typed score fails the build. Mandates carry their framework, requirement, and due date. The backlog re-scores on a schedule and the order changes without anyone arguing about it.
The detection record What does a responder have in front of them at three in the morning? The query, and whatever the author remembers. Each detection names its goal and its technique. Records carry goal, technique, log sources, and response steps. Records carry all 11 sections, the 10 ADS sections plus the retirement record, and the pipeline rejects a detection missing any of them. Records are versioned with the detection, and every change to the logic changes the record in the same commit.
Validation What proves a detection fires on the behavior, and that somebody other than the author agreed? It went live because it looked right in the console. Each detection is spot-checked by hand against one true event. Every detection has a true-positive fixture and a false-positive fixture stored with it. Fixtures replay in CI on every change, and a second engineer's approval is required to merge. Fixtures and golden query diffs run for every target, and a failing replay blocks the release.
Deployment How does a detection get from a text editor into production, and can you replay how? Edited directly in the SIEM console. Detections live in version control and are copied into the SIEM by hand. Deployment is a documented, repeatable procedure with a change record. The pipeline deploys; console edits are reverted or alarmed. Every release is reproducible from a commit, and a rollback is one revert.
Upkeep and retirement What removes a detection, and how long does a dead one keep costing you? Nothing. Detections accumulate. Detections are reviewed when somebody complains about the noise. Precision and triage minutes are measured per detection every month. Each detection has a floor, and a detection under its floor for two windows is proposed for retirement on the record. The precision check runs on a schedule and proposes retirements; replacements enter the backlog with a link to the retirement note.
Measurement What numbers does the program report, and would two people compute them the same way? Detection count, when asked. A handful of numbers are reported without written definitions. Every reported number has one written definition and one owning stage. The pipeline produces the build-side numbers, and coverage is reported weighted. Numbers change decisions on the record, and a claim about coverage can be falsified by pointing at a test.

Response

Response dimensions cover what happens after an alert fires. Score them only if the team owns response. A team that hands confirmed incidents to another group leaves them out, and its level is its lowest detection dimension.

Dimension The question it answers 0. Ad hoc 1. Repeatable 2. Measured 3. Enforced 4. Self-correcting
Triage Who works each alert, how long does it take, and would two analysts close it the same way? Alerts are worked by whoever sees them, and nothing records how they closed. Every alert goes to one queue, and each closed alert carries an outcome. Every alert closes with a code from a fixed list, and triage minutes and precision are measured per detection. Analysts calibrate each month on the same sampled alerts, and an alert closed as benign that proves malicious gets the miss code alert_closed. A weekly sample of closed alerts measures the false-close rate, and each wrong close changes a record or a runbook.
Investigation When an alert is real, how fast does someone establish what happened, and could a second person repeat the work? Investigations happen in chat and in people's heads. Every escalated alert opens a case with an owner and a timeline. The most frequent alert types have playbooks, and the hours from escalation to a known scope are measured. Each case records its queries and their time ranges, and a second person can repeat the investigation from the case alone. Every confirmed incident reaches the detection review, and its events become fixtures or intake items with a miss code.
Containment Once something is confirmed, how fast is it stopped, and who is allowed to stop it? Containment depends on who is online and what they can reach. The containment actions, and who may take each one, are written down. The common actions are scripted, and the minutes from confirmation to containment are measured. Actions that can be undone are approved in advance in playbooks, and each one is logged with who took it. Every containment action is tested each quarter, and a failed test is fixed before an incident needs it.
Communication Who hears about an incident, how soon, and does the program meet its reporting deadlines? Leadership and regulators hear about an incident when someone remembers to tell them. A notification list exists for each severity, with every deadline that applies. Every notification is timestamped and measured against its deadline. The notification path is rehearsed each year, and a late notification is reported with its cause. Reports are drafted from the case record, and no notification missed its deadline in the last year.

13.2Reading your own score

Score each dimension on what's true today, then take the lowest. A program at Enforced on deployment and Ad hoc on telemetry is an Ad hoc program with good deployment. Its coverage numbers may describe detections reading a log source that stopped last month.

Raise your lowest dimension first. Each dimension names the next action from where you stand, and the site's Score your maturity tool prints that list for the levels you select.

Dimension To reach Measured To reach Self-correcting
Telemetry Record whether each source's fields are parsed, and its normal event rate. Fail the pipeline when a detection cites a source that is not in the inventory.
Backlog and order Score each candidate on the six inputs, with one evidence line per input. Re-score the standing backlog on a schedule, so stale relevance falls away.
The detection record Add the log sources it reads and the response steps for the analyst. Version each record with its detection, so a change to the logic changes the record in the same commit.
Validation Capture that event as a fixture stored next to the detection. Diff the converted query for each target against an approved copy, so a conversion change cannot pass silently.
Deployment Write the deployment step down so two people do it the same way. Make every release reproducible from a commit, with a rollback that is one revert.
Upkeep and retirement Measure precision and triage minutes per detection over 30 days. Automate the check so the report arrives without anyone running it.
Measurement Write one definition per metric, with its unit and how it aggregates. Tie the numbers to decisions: what gets built next, what gets retired.
Triage Close every alert with a code from a fixed list, and measure triage minutes per alert. Sample a share of closed alerts every week, and send each wrong close back to the detection's record.
Investigation Write a playbook for each of the most frequent alert types, naming the queries to run. Send every confirmed incident's events to the detection review, as fixtures and intake items.
Containment Script the common actions, and measure the minutes from confirmation to containment. Test each containment action every quarter against a test host or account.
Communication Record when each notification went out, and measure it against its deadline. Draft the regulator reports from the case record, so the timeline is written before the clock starts.

Each detection dimension maps to one of the practices in section 3, so your level also tells you which practice to adopt or deepen next. Countable definitions of done is the one practice without a dimension of its own. I left it out because a definition of done is how every other dimension moves from Repeatable to Enforced.