DETECT hunt Run and measure

Section 11

Operating rhythm

Framework v0.136.0, updated November 17, 2026.

Remember

  • Run intake weekly, live review monthly, and coverage and capacity quarterly, and review detections within 5 working days of each incident.
  • Every role needs an owner, and one person can own several.
  • Check that the reviewer and SOC lead roles have owners. Gaps in those two take the longest to show.
  • Spend the first 30 days on the inventory, detection zero, and measurement, before you write new detections.
  • Report the incident detection rate even when it's low.
  • A playbook gets a record, the eight stages, and 14 days in propose mode before it acts. A person approves every containment.
  • Every incident ends in a candidate, a tuning pull request, or a log source request, and the report names the ones that ended in nothing.

The framework says what good looks like. Three standing meetings and a review after every incident keep the backlog scored, noisy rules tuned or retired, and leadership informed. Running a program also takes an owner for every role and the templates on the Templates and cadence page.

On this page

11.1Meetings

Meeting Time box Who is in it What it decides What it produces
Intake and order, weekly 30 minutes Detection lead, the engineers, whoever brought a candidate What enters build this week, and which candidates are blocked on telemetry A re-ordered backlog with every new candidate scored and every score carrying its evidence lines
Live review, monthly 60 minutes Detection lead, the SOC or triage lead, the engineer who owns each detection under discussion What gets tuned with a named exclusion, what gets retired, what gets left alone Tuning pull requests and retirement notes, each naming the trigger that fired and the number behind it
Coverage and capacity, quarterly 90 minutes Detection lead, SOC lead, the platform or data owner, the manager who owns the budget Next quarter's telemetry asks, whether the weights still match the threat picture, and which ceiling to spend against The quarterly report: the numbers, the ask, the lowest maturity dimension with the work that raises it, and next quarter's OKRs
Detection review after an incident, within 5 working days of every incident 45 minutes Incident responder who ran it, detection lead, the engineer who will build what comes out Which live detections get a fix carrying the incident's events as a fixture, which candidates enter intake with what threat relevance, and which rules put live by hand during it enter intake Intake items backed by your own incident with dates, the strongest evidence a candidate can have. A row in incidents.csv says who found the incident first and, when no live detection did, gives its miss code.

Each meeting prevents a specific failure:

Meeting What happens when it is skipped
Intake and order The loudest request wins, and blocked candidates sit in the queue looking like engineering work.
Live review Nothing leaves production. Analysts absorb the cost until they stop reading alerts.
Coverage and capacity The program grows until a ceiling breaks it, and you find out from a missed incident.
Detection review after an incident The most valuable intake source in the organization goes unread, and the same technique works twice.

None of these meetings needs a tool. The weekly takes half an hour. On a one-person team you spend it alone with a written backlog, which beats carrying the order in your head.

11.2Roles

On a small team one person owns several roles, and section 3 says which ones collapse at each size.

Role Owns Decides Stages it owns
Detection lead Intake, the backlog order, the metric set, and the quarterly report What is built next and what the weights are intake, deploy, retire
Detection engineer The hypothesis, the detection, the record, the fixtures, and the score's evidence lines How the behavior is matched, and what the detection will not catch hypothesis, research, build
Reviewer, a second engineer The approval on the change, and the argument with the blind spots section Whether it ships validate
SOC or triage lead The triage minutes, the alert outcomes, and half of the tuning decision What the analysts can absorb, which sets the triage ceiling tune
Incident response lead Investigation, containment, and the notification path When an alert becomes an incident, what gets contained, and who is told by when none; receives what triage escalates, and sends every confirmed incident to the detection review
Platform or data owner The log source inventory, the silence alerts, parsing and retention What gets onboarded and when, which sets telemetry readiness none; supplies readiness for research

What goes wrong when nobody owns a role:

Role What goes wrong with no holder
Detection lead Priority becomes whoever asked most recently, and no number is reported the same way twice.
Detection engineer Detections exist without records, and nobody but the author can triage or change them.
Reviewer, a second engineer Every detection carries its author's assumptions about the environment into production.
SOC or triage lead Run cost is a guess, the precision floor has no data behind it, and nobody notices alert fatigue until analysts leave.
Incident response lead Confirmed incidents never reach detection engineering, so the same technique works twice, and reporting deadlines depend on memory.
Platform or data owner Readiness scores are fiction, and detections are built on log sources that stopped last month.

Check the reviewer and the SOC lead first, because their absence takes the longest to notice. Without a reviewer, detections reach production built on an assumption the author didn't know they were making. Without a SOC lead, nobody measures run cost, and the backlog order becomes a guess.

11.3The first 90 days

This is for you if you've just been handed the function, with or without a team. A team starting from nothing begins with section 4 instead.

Days 1 to 30: See what you have

  • Inventory the log sources: source, owner, retention, parsed yes or no, normal event rate.
  • Ship the silence alert for every source that matters. This is detection zero.
  • List the live detections and find the ones nobody has looked at in a year.
  • Pull the last 12 months of incidents and tag each with the technique the attacker used and with whether a live detection alerted on it first.

Report at the end of the block: The inventory, the live count, and the share of incidents a detection caught first.

Refuse for now: Don't write new detections yet, and don't promise coverage percentages.

Days 31 to 60: Put the work in order

  • Score the open backlog on the six inputs, with an evidence line each.
  • Put the definitions of done into your ticket template so a detection can't close on judgment alone.
  • Start the weekly intake meeting and the post-incident detection review.
  • Measure precision and triage minutes for the 10 noisiest live detections.

Report at the end of the block: The ordered backlog, the first precision numbers, and the first retirement candidates.

Refuse for now: Don't buy a platform to fix a process problem, and don't adopt the CI pipeline before the records exist.

Days 61 to 90: Make it repeat without you

  • Build the first three detections through every definition of done, records and fixtures included.
  • Retire what the triggers say to retire, with a note each.
  • Run the monthly live review for the first time.
  • Score the maturity dimensions and publish the lowest one with the work that raises it.

Report at the end of the block: The quarterly report: coverage weighted by robustness, the three ceilings against the live count, the maturity score, and one ask.

Refuse for now: Don't report a detection count as progress, and don't commit to a coverage target before you know the telemetry ceiling.

11.4Common failure patterns

None of these failures takes a bad engineer. Each one is the reasonable thing to do on a busy day, which is why they keep happening. The table says what each looks like, what it costs, and what replaces it.

Pattern What it looks like, and why it happens What it costs What replaces it
The console edit A detection is changed directly in the SIEM to quiet an alert during a shift. It takes 30 seconds, and nobody reviews it. The change has no author, no reason, no test, and no way back. The next replay fails and nobody knows why. Deployment from the repository only; console edits reverted or alarmed. Tune through an allowlist variable.
The coverage heatmap A grid of ATT&CK techniques shaded green wherever a detection exists. It's the easiest artifact to produce and the easiest to present. Seven brittle detections and one solid detection both show green, with no way to tell which is which. Report coverage weighted by robustness beside the raw count, and report the gap between them.
The vendor pack 400 out-of-the-box detections enabled at once because they came with the platform. It looks like instant coverage and costs nothing up front. Alert volume past the triage ceiling in a week, and no record, score, or owner for any of them. Enable them against the alert budget, scored like anything else, in batches you can measure.
The unowned alert An alert fires into a queue that nobody is accountable for reading. The detection shipped before the response steps were written. Triage minutes are spent and no decision comes out of them. Deploy only detections whose record has response steps.
The hero detection One engineer's detection that only that engineer can interpret. The detection is clever and the record feels like overhead. It goes unread on their leave and unmaintained after they move on. 11 sections, and a reviewer who has to triage from the record alone.
Tuning that becomes narrowing Each exclusion shaves the detection until it matches only the original sample. Every individual exclusion is defensible in the moment. A detection that still reports as live coverage and can no longer catch the technique. Name the exclusion as a variable and count them. When a detection needs a new exclusion every month, propose its retirement at the monthly meeting.
The silent source A log source stops and the detections on it keep reporting as healthy. Nothing alerts on absence, and dashboards only show what arrived. Coverage is reported for a technique nobody could detect that month. Detection zero, and readiness that drops automatically when a source dies.
The redefined metric Precision means one thing this quarter and another the next. The number was inconvenient, and the definition was never written down. Every trend line tracks the definition. One written definition per metric, one owning stage, and a change to a definition treated as a release.
The god-mode emulation The technique is run from an admin session because that session was already open. It's faster, and the commands succeed the first time. The events carry an identity no attacker would have. Detections written from them fire in the lab and never in production. Start from the foothold the scenario allows. Use only the permissions that stage would have.
The remembered field name The detection is written from documentation or from memory of the schema. The engineer has read that log 100 times. A detection that is almost right, never fires, and reports as coverage until an incident proves otherwise. Read every field name off a real event from the emulation run.
The steered agent An agent reading logs follows an instruction that an attacker planted in a command line or a user name. Nothing told the agent that log content is data. The agent queries, writes, or opens pull requests for the attacker, with the program's own credentials. Read-only credentials, tool calls taken only from the task, and every change through a pull request a person approves.

11.5Miss codes

The detection review after an incident names the cause of every miss with one code. Counted over a quarter, the codes show leadership where misses come from and which owner fixes them.

Code What happened The fix Owner
no_log_source The behavior happened where no collected log source records it. A log source request to the platform owner, and the technique's candidates rescored with telemetry readiness 0. Platform or data owner
source_silent The log source is collected, but it sent nothing while the incident ran. A silence alert for the source in DET-0000, with the source's usual gap measured. Platform or data owner
field_unparsed Events arrived, but a field the detection needs was missing or unparsed. A parsing fix, and a lower telemetry readiness for the source until it lands. Platform or data owner
no_detection The telemetry was there, and no live detection covered the behavior. A candidate at intake, with the incident as its threat-relevance evidence and its events as the positive fixture. Detection lead
detection_broken A live detection covers the behavior and stayed silent, because of a wrong field, a changed format, or a query that drifted from its approved copy. Fix this detection. The missed events become a positive fixture, and the change goes back through validate and its 7-day count. Detection engineer
tuned_out An exclusion added in tuning suppressed the alert. Narrow the exclusion. The missed events become a positive fixture, so the next tuning change has to keep them. Detection engineer and SOC lead
alert_late A detection alerted, but after a person or another source had already found the incident. Shorten the detection's latency through its schedule, its lookback, or its place in the queue. Detection engineer
alert_unworked The alert fired and nobody opened it in time. Cut the load or raise the triage ceiling: retire noisy detections, or route this one to a faster queue. SOC lead
alert_closed A person or an agent opened the alert and closed it as benign. Fix the record's response section, add the case to triage calibration, and count it in the false-close rate. SOC lead

Record one code for each incident or exercise that a live detection did not catch first. When more than one applies, take the first break along the path from the log source to the analyst, because a fix further along cannot work until the earlier one lands. The repository keeps the record in incidents.csv, one row per confirmed incident or exercise. Lint checks every row against this list, and tools/metrics.py counts the codes per quarter for the reporting page. One row per confirmed incident or exercise. The found_by column says detection only when a live detection alerted first, and then miss_code stays empty. The fix column names the detection id or the log source request, and fix_validated_on is the date the fix passed validate.

11.6Quarterly OKRs

Do it in the browser Plan OKRs and a roadmap

Each quarter, the coverage and capacity review sets at most three objectives, each raising one maturity dimension by one level. Every objective carries two kinds of key result: the work that earns the next level, and a metric that moves because of that work.

  • Raise at most three dimensions in a quarter, each by one level. A level counts only when every statement at it is true, so two levels in one quarter is rare.
  • Start from the lowest dimension, because the program's level is its lowest dimension.
  • Write each metric key result as a baseline and a target. With no baseline yet, the key result is to measure it this quarter.
  • Use a KRI as a key result only when it is past its tolerance today, and set the target at the tolerance.
  • Score last quarter's objectives at the same review, before setting the next ones.

The roadmap plays the same rule forward. Each quarter, the lowest dimensions below the year's target rise one level, up to three a quarter. Re-run it every quarter, because a quarter's real results change the next one. The Plan OKRs and a roadmap tool drafts both from a maturity score. Each maturity dimension names an owner and the metrics that show it moving:

Dimension Owner Metrics that show it moving
Telemetry Platform or data owner readiness_at_hypothesis, silent_source_hours
Backlog and order Detection lead intake_to_score_days, backlog_age_days, priority_technique_gaps
The detection record Detection engineers triage_minutes_median, minutes_per_true_positive
Validation Detection lead percent_with_tests, first_pass_validation_rate, review_turnaround_hours
Deployment Detection engineering, with the platform owner deploy_lead_time_days, post_deploy_replay_failures, detection_latency_median
Upkeep and retirement Detection lead and SOC lead precision_30d, upkeep_minutes_per_detection, rule_debt, rules_retired_per_quarter
Measurement Detection lead robustness_weighted_coverage, incident_detection_rate, misses_by_cause, open_detection_fixes_age
Triage SOC or triage lead triage_minutes_median, false_close_rate
Investigation Incident response lead time_to_scope_hours, misses_by_cause
Containment Incident response lead time_to_contain_minutes
Communication Incident response lead, with legal and the CISO's office notifications_on_time

11.7Regulatory requirements

Do it in the browser Map regulatory controls

A detection and response program already keeps most of the records a security regulation or an audit asks for: the logs it collects, the detections it reviews, the incidents it records, and the notifications it sends. The crosswalk names, for each control, the records that answer it, so an audit request becomes a list of files.

Answer each control with a record the program already keeps, and add a record only when none answers. An auditor, or counsel for a regulation, decides whether a record meets the control. A notification clock starts at the event its rule names, and the program records that time with the notification.

The crosswalk maps 59 controls from 9 regulations and standards. NIST's wording is quoted; the rest is paraphrased from the source, except where the last column says otherwise:

Regulation or standard Version Controls Read in
NIST Cybersecurity Framework 2.0 CSWP 29, 26 February 2024 16 the source
ISO/IEC 27001:2022, Annex A 2022 10 control titles only
PCI DSS 4.0.1, June 2024 10 the source
SOC 2 Trust Services Criteria 2017, points of focus revised 2022 6 a secondary copy
DORA, Regulation (EU) 2022/2554 Applies from 17 January 2025, with Delegated Regulation (EU) 2025/301 for report timing 3 the source
NIS2, Directive (EU) 2022/2555 Directive of 14 December 2022, applied through each member state's law 3 the source
US SEC cybersecurity disclosure rules Form 8-K Item 1.05 and Regulation S-K Item 106 2 the source
HIPAA Security Rule and Breach Notification Rule 45 CFR Part 164 as in force; the 2025 proposed rule is not final 4 the source
NYDFS Cybersecurity Regulation, 23 NYCRR 500 As amended 1 November 2023 5 the source

Most controls ask for the same few records, so the program keeps each once:

Record Where it is Asked for by
Case records the case system NIST CSF, ISO 27001, PCI DSS, SOC 2, DORA, NIS2, SEC, HIPAA, NYDFS
Detection records detections/*/ads.md and rule.yml NIST CSF, ISO 27001, PCI DSS, SOC 2, DORA, NIS2, HIPAA, NYDFS
Notification log notifications.csv NIST CSF, ISO 27001, SOC 2, DORA, NIS2, SEC, HIPAA, NYDFS
Log source inventory inventory.csv NIST CSF, ISO 27001, PCI DSS, SOC 2, DORA, HIPAA, NYDFS
Incident log incidents.csv NIST CSF, ISO 27001, PCI DSS, SOC 2, DORA, SEC, HIPAA
Detection zero detections/DET-0000/ NIST CSF, ISO 27001, PCI DSS, DORA, HIPAA, NYDFS
Alert dispositions the case system NIST CSF, ISO 27001, PCI DSS, SOC 2, NIS2, HIPAA
Validation replays detections/*/tests/ and the CI log ISO 27001, PCI DSS, SOC 2, DORA, NIS2
Emulation runs the Technical Context section of each ads.md NIST CSF, PCI DSS, SOC 2, DORA, NYDFS
Metrics report site-data/metrics.json, from tools/metrics.py NIST CSF, SOC 2, DORA, NIS2, SEC
Precision checks the 30-day precision review, which a person runs today ISO 27001, SOC 2, NIS2
Maturity score and OKRs the maturity and OKR tools NIST CSF, NIS2, SEC
Backlog scores detections/*/score.yml NIST CSF, ISO 27001
Review approvals the pull request history ISO 27001, SOC 2
Retirement notes the Retirement record section of each ads.md PCI DSS

The reporting clocks run from an event the regulation names. Each notice goes in notifications.csv with its clock and the time the clock started. Lint computes each deadline and fails a hand-typed one that disagrees, and metrics.py reports notifications_on_time each quarter. A late notice to a regulator or a customer turns that KRI red. Business days count weekdays and skip no holidays, so the computed deadline is never later than the real one. National law sets the details of NIS2 reporting, and counsel decides which clocks apply to an incident.

Report Due Clock
DORA initial notification 4 hours after the incident is classified as major dora_initial
DORA initial notification, outer limit 24 hours after the entity becomes aware of the incident dora_initial_awareness
DORA intermediate report 72 hours after the initial notification is sent dora_intermediate
DORA final report 1 month after the latest intermediate report is sent dora_final
NIS2 early warning 24 hours after the entity becomes aware of a significant incident nis2_early_warning
NIS2 incident notification 72 hours after the entity becomes aware of a significant incident nis2_notification
NIS2 incident notification by a trust service provider 24 hours after the provider becomes aware of a significant incident nis2_notification_trust
NIS2 final report 1 month after the incident notification is sent nis2_final
Form 8-K Item 1.05 4 business days after the company determines the incident is material sec_8k
Form 8-K amendment with information missing from the first filing 4 business days after the missing information is determined or becomes available sec_8k_amendment
HIPAA notice to affected individuals 60 days after the breach is discovered hipaa_individuals
NYDFS notice to the superintendent 72 hours after the company determines a cybersecurity incident occurred nydfs_notice
NYDFS notice of an extortion payment 24 hours after the extortion payment is made nydfs_extortion
NYDFS reasons for an extortion payment 30 days after the extortion payment is made nydfs_extortion_reasons

Some clocks bend in cases the table can't show:

  • dora_initial: When a deadline falls on a weekend or bank holiday, Delegated Regulation 2025/301 moves it to noon of the next working day for most entities. The tools do not, so their deadline can only come earlier.
  • dora_initial_awareness: Log this clock beside dora_initial only when the incident was classified major within 24 hours of awareness. A later classification leaves dora_initial alone, at 4 hours.
  • nis2_notification: Trust service providers have 24 hours, on the nis2_notification_trust clock.
  • nis2_final: For an incident still being handled at the one-month mark, a progress report is due then, and the final report one month after the handling ends.
  • sec_8k: The materiality determination itself must come without unreasonable delay after discovery.

The kit's audit_pack.py reads the records the repository keeps and writes an index for the regulations named, with each record found, empty, or missing. It lists the records kept elsewhere, case records above all, for a person to export. The Map regulatory controls tool shows the same crosswalk in a browser.

11.8Response playbooks

A playbook is the automation that runs when a detection fires: it enriches the alert, decides, and acts or proposes an action. It gets the same treatment as a detection. It has a record, it moves through the eight stages with a countable definition of done at each, it runs in propose mode before it acts, and a trigger retires it. A playbook that only exists in the SOAR console is a live detection with no record.

Playbooks serve detections, so a playbook names the detection ids or the alert class it runs on, and it enters intake only when that detection is live. The agent rules of section 10 cover a playbook that calls a model; the approval points below apply either way.

The record lives at playbooks/PB-NNNN/playbook.md and carries these sections:

Section What it holds
Serves The detection ids or the alert class the playbook runs on, and the alert volume per day it will see.
Trigger The alert field values that start it. Nothing else does, so an alert the trigger does not name goes to a person.
Enrichment Each lookup, its source, and the field it fills. A lookup that fails leaves its field empty and says so, and the playbook goes on.
Decision The rule that turns the enriched alert into one outcome: close as benign, escalate, or act. Every branch is written down, and the default branch is escalate.
Action What it does on each outcome, at which tier of the ladder, and the exact call it makes.
Approval point Which actions wait for a person, who that person is, and how long the action waits before it expires unacted.
Rollback The call that undoes each action, tested once against a real object, and who may run it.
Manual baseline The steps an analyst took by hand before the playbook, timed over at least 20 alerts: median minutes, and the outcome each one got.
Fixtures One past alert per outcome, with the enrichment results as they were, and the outcome the analyst recorded.
What it gets wrong The alert the decision rule will misread, with its name. A playbook that closes alerts has at least one.

What a playbook may do comes in four tiers. Each tier up changes more outside the alert, and each needs more of a person:

Tier What the playbook does Who approves
1. Enrich Adds context to the alert: asset owner, user's role, prior alerts, reputation, the detection's record. None. Nothing changes outside the alert.
2. Route Sends the alert to a queue, a person, or a ticket, and sets its severity from the enrichment. None, once the routing rule has run in propose mode.
3. Close Closes an alert as benign with a code, and records why. No person for a detection rated impact 1 to 3 once agreement is above the floor. A person every time for impact 4 or 5.
4. Contain Changes something outside the alert: disables an account, isolates a host, blocks an address, revokes a token. A person, always, and the action expires unacted after the time the record sets. A reversible action on an asset the record names as expendable, such as a test host, may skip the approval.

A playbook moves through the same eight stages as a detection. Where a stage's definition of done differs, this table says how; the rest is Appendix A:

Stage What differs for a playbook Definition of done, counted
1. Intake The candidate names the detection or alert class it serves, the alerts per day it would see, and the ladder tier it wants. Scored on the six inputs like a detection, where build effort covers the integrations and run cost covers the actions it would take. 6 scores with an evidence line each, 1 detection id or alert class, 1 tier
2. Hypothesis One sentence: on this alert, with these lookups, this rule gives this outcome, and it will misread this case. 1 sentence, 1 named outcome, 1 named misread
3. Research An analyst works at least 20 of the alerts by hand and times each one. The steps they took become the enrichment list and the decision rule; the minutes become the manual baseline. 20 alerts timed, each with its steps and its outcome
4. Build The playbook is written as code in the repository, where it can be reviewed and replayed. Each lookup has a fixture, each outcome has a fixture, and the rollback runs once against a real object. 1 fixture per outcome, 1 fixture per lookup, 1 rollback run
5. Validate Replayed against the last 30 days of closed alerts for the alerts it serves. Its outcome agrees with the analyst's recorded outcome at or above the floor, it proposes no close on an alert later confirmed malicious, and a second person approves. 30 days of alerts replayed, agreement at or above the floor, 0 closes on a confirmed alert, 1 approval by someone other than the author
6. Deploy Runs for 14 days in propose mode: it enriches, decides, and writes what it would do, and a person does it. Acting switches on only if agreement stayed above the floor for the whole 14 days and no proposed action was refused on an alert rated impact 4 or 5. 14 days in propose mode, agreement at or above the floor on every day, 0 refused proposals on an impact 4 or 5 alert
7. Tune Every refused or reverted action is a tuning pull request that changes the decision rule and adds the alert as a fixture. The playbook stays in propose mode until it merges. 1 pull request per refused or reverted action, with the alert as a fixture
8. Retire A trigger fires, the owner decides, and the record keeps a retirement note. The playbook's actions switch off before its code is removed. 1 trigger named, 1 retirement note, actions off before removal

The agreement floor is 0.95. The share of alerts on which the playbook's outcome matched the analyst's. The default is a chosen starting point that no team has measured yet. Set it lower for tier 1 and 2 playbooks, which cost a person a minute when wrong, and never below 0.99 for a playbook that closes alerts on its own.

Four triggers propose a playbook's retirement, and the owner decides, as with a detection:

  • agreement: Agreement under the floor for two months running. Back to propose mode first; retirement if the tuning pull requests do not raise it.
  • orphaned: Every detection it serves is retired. The playbook retires with the last one.
  • idle: No run in 90 days. Either the alert stopped, which is a detection question, or the trigger no longer matches, which is a playbook bug. Both end at retire or tune.
  • reverted: A tier 4 action reverted by a person. The playbook drops to propose mode that day, and the live review decides whether it comes back.

Four metrics, defined in Appendix C with the rest. The kit does not compute them yet; the SOAR's own run log and the alert outcomes supply the counts.

Metric Unit Aggregation Definition
playbook_coverage percent per quarter Share of alerts in the quarter whose detection has a live playbook at tier 1 or higher.
playbook_minutes_saved_per_alert minutes median per quarter The manual baseline minutes on the playbook's record, minus the analyst minutes an alert takes with the playbook running, per alert class.
playbook_actions_unattended count per month, by tier Actions a playbook completed with no person in the loop, counted by ladder tier. A tier 4 count above zero names the expendable asset the record allows.
playbook_actions_reverted count per quarter Playbook actions a person refused in propose mode or undid after they ran. Each one is a tuning pull request.

11.9After an incident, and who carries the pager

Every confirmed incident changes the backlog or a detection. The detection review names what it changes, and the quarterly report counts the incidents that changed nothing.

  • Every confirmed incident gets a row in incidents.csv within 5 working days, with found_by filled in and, when no live detection caught it first, one miss code.
  • Every incident produces at least one of: an intake candidate carrying the incident's events as its positive fixture, a tuning pull request on the detection that fired late or stayed silent, or a log source request to the platform owner. The row's fix column names it.
  • An incident that produced none of these within 30 days counts in incidents_without_followup. The quarterly report lists each one with the responder who ran it.
  • A rule put live by hand during the incident enters intake the same week, with the incident as its evidence. It stays live until its candidate passes validate or the live review retires it.
  • The responder brings the timeline; the detection lead brings the alert record. Neither writes the other's part.

The SOC's rotation answers alerts. A second, lighter rotation answers for the detection pipeline itself. A silent log source or a red build on main is not an alert, so nobody is paged for it unless someone is named.

What pages Who answers Within
A DET-0000 silence alert on a log source rated readiness 3 or higher The platform or data owner, with the detection engineer on rotation in copy The source's usual gap, as DET-0000 measures it
A red build on the default branch, or a conversion that no longer matches its approved copy The detection engineer on rotation The next working day; nothing deploys until it is green
A live detection whose alert count passes its hourly limit The detection engineer on rotation, with the SOC lead One hour, and alerting switches off on its own before anyone answers
A tier 4 playbook action waiting for approval The incident response lead or the named approver The time the playbook's record sets; the action expires if nobody answers

One engineer carries the pipeline pager for a week at a time. A one-person team carries it always, which is one reason the silence alert's floor is an hour and not a minute.

Next step Templates