Detection Lifecycle
Manage detection ideas from threat model through validation, deployment, monitoring, tuning, and retirement.
On this page · 4 sections
Operating context
A detection is a maintained product with an owner, data contract, hypothesis, tests, runbook, quality measures, and retirement criteria.
- Define the security decision that detection lifecycle must support.
- Assign accountable owners, escalation paths, service levels, and privacy boundaries.
- Measure signal quality, response consistency, operational cost, and improvement over time.
Operational workflow
- 01
Establish scope, dependencies, normal behavior, and a documented baseline.
- 02
Collect the minimum telemetry and context needed for detection lifecycle.
- 03
Correlate independent signals and state confidence before taking disruptive action.
- 04
Document the decision, evidence, containment or control action, and responsible owner.
- 05
Review the outcome, tune the process, and validate the improvement with a safe test.
Signals, evidence & decisions
| Signal or artifact | Decision it supports |
|---|---|
| detection backlog and risk rationale | Establish event sequence and affected scope. |
| test fixtures and deployment record | Confirm identity, asset, or control context. |
| fidelity, coverage, and health metrics | Support containment, recovery, or tuning. |
Record source, timestamp, collection method, confidence, owner, and disposition. Preserve the smallest useful evidence set and document any uncertainty.
Implementation & improvement
- Peer-review logic and response guidance.
- Canary-test telemetry dependencies.
- Retire rules whose objective is gone or duplicated.