Containment, Eradication & Recovery
Choose proportionate containment, remove root causes, and restore services with verified security controls.
On this page · 4 sections
Operating context
Containment limits harm; eradication removes persistence and vulnerabilities; recovery restores trustworthy operation. Each phase needs explicit exit criteria and rollback planning.
- Define the security decision that containment, eradication & recovery 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 containment, eradication & recovery.
- 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 |
|---|---|
| containment decision and business impact | Establish event sequence and affected scope. |
| eradication checklist and credential actions | Confirm identity, asset, or control context. |
| recovery tests and monitoring results | 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
- Prefer reversible containment when risk permits.
- Rebuild high-risk systems from trusted baselines.
- Increase monitoring during staged restoration.