Quick reference
Every phase on one page.
Each card shows when a phase starts, the work it covers, when it is done, and the record it leaves behind. Scope, contain, eradicate and recover repeat until scoping produces nothing new. Tap a card to open its playbook.
PPreparation
- Starts when
- No incident running. This is the default state
- Core work
- Policy, authority, playbooks, backups, tooling, exercises, hunting
- Done when
- Never closes. Every debrief reopens it with named owners
- Leaves behind
- Authority matrix, playbooks, asset and contact lists
IIdentification
- Starts when
- Telemetry and reports flowing. Runs continuously
- Core work
- Operate detections, work alerts, hunt on a cadence
- Done when
- An event of interest raised with evidence references attached
- Leaves behind
- Alert or hunt finding with evidence references
VTVerification and triage
- Starts when
- An event of interest with evidence references
- Core work
- Confirm it requires a response, rank it against organizational objectives
- Done when
- Continue, stop, or defer, with a name and a time against it
- Leaves behind
- Incident record, triage brief
RScope
- Starts when
- Verified incident with at least one indicator
- Core work
- Derive indicators, enterprise hunt, progressive sweep, attack timeline
- Done when
- Systems, accounts, and data enumerated, with visibility gaps named
- Leaves behind
- Scope findings, attack timeline
RContain
- Starts when
- Scope clear enough to act, posture chosen, authority in hand
- Core work
- Stop attacker activity, preserve evidence by volatility
- Done when
- Network, process, and log channels all show attacker activity stopped
- Leaves behind
- Containment decision record
REradicate
- Starts when
- Evidence collected and preserved
- Core work
- Short-form investigation, remove persistence, rotate credentials, patch
- Done when
- Rerunning the enumeration that found the problem comes back clean
- Leaves behind
- Root cause, eradication log
RRecover
- Starts when
- Eradication verified
- Core work
- Verification checks, validation testing, owner sign-off, restoration
- Done when
- Systems in production under enhanced monitoring, owner sign-off on file
- Leaves behind
- Pre-restoration sign-off, owner acceptance
DDebrief
- Starts when
- Loop exited, technical closure and risk acceptance both signed
- Core work
- Close temporary assets, consolidate records, metrics, after-action review
- Done when
- Improvement plan issued with named owners and milestone dates
- Leaves behind
- Incident report, metrics, improvement register
Templates to have open
- T1. Incident record, opened at verification
- T2. Triage brief to decision makers
- T3. Containment decision record
- T4. Loop iteration log
- T5. Technical closure
- T6. Residual risk acceptance
- T7. Pre-restoration sign-off
- T8. System owner acceptance
- T9. After-action review agenda, 90 minutes
- T10. Executive debrief, one page
- T11. Stakeholder status update
- T12. Internal notice to staff
- T13. Law enforcement and insurer contact
- T14. Improvement register
- T15. Incident report
- T16. Notice to affected individuals or customers
- T17. Regulator notification worksheet
- T18. Interim statement and media inquiry log
- T19. Vendor evidence and preservation request
Settle authority to isolate, acceptance of residual risk, notification clocks and evidence handling in advance, using Decide these before the incident. Command, roles, the planning cycle and shift handover are in the companion Incident Command guide.