PIVTR-D

Quick reference

Every phase on one page.

Open the templates

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

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.