PIVTR-D

The lifecycle

Read it left to right. Scope, contain, eradicate and recover repeat until scoping stops turning up new evidence. Decision makers sit behind the whole sequence, because every gate needs them.

Incident response lifecycle Preparation, Identification and Verification and Triage run left to right into a four part response actions loop containing Scope, Contain, Eradicate and Recover, which exits to Debrief. Gate conditions sit above each junction. A band behind the sequence marks continuous decision maker involvement. A dashed arrow returns from Debrief to Preparation. Decision makers, throughout Preparation Identification Verification and Triage Debrief Contain Eradicate Recover Scope Response repeat until no new evidence runs continuously event of interest verified, continue exit criteria met Debrief findings set the next Preparation cycle Incident response lifecycle The same lifecycle stacked vertically, with gate conditions between each waypoint and a repeat arrow on the response actions loop. Decision makers, throughout Preparation runs continuously Identification event of interest Verification and Triage verified, continue Response actions loop Scope Contain Eradicate Recover repeat exit criteria met Debrief Debrief findings set the next Preparation cycle
Each checkpoint sits above the junction it governs. Identification is drawn as continuous because it never stops. The dashed return path carries debrief findings into the next preparation cycle.
The DAIR model: chevrons for Prepare, Detect, Verify and Triage, then a ring containing Scope, Contain, Eradicate and Recover, ending at Debrief.
Figure 22. The source model, Wright's Dynamic Approach to Incident Response (DAIR). PIVTR-D renames Detect to Identification so the letters match PICERL, gives Verify and Triage a letter each, and adds a return path from Debrief to Preparation.

Why the loop is there

Figure 23 draws four activities as steps: isolate and gather evidence under contain, analyze and remove persistence under eradicate, each running once and in order.

Timeline with four activities as single segments, split between Contain and Eradicate.
Figure 23. The stepped view.

Figure 24 draws the same four as they run in a real incident. Isolation happens three times, evidence gathering starts and stops four times, and analysis runs underneath from early on. Plan for the second picture, because status reporting built on the first contradicts itself once the activities repeat.

Timeline with the same four activities as recurring blocks across the full time axis, evidence analysis as one long bar.
Figure 24. The same work, as it runs in practice.
The model with the background band behind all activities highlighted, marking decision maker involvement throughout.
Figure 25. Coordinating with decision makers. Wright highlights verification, triage and the response loop, and PIVTR-D extends the band across every phase.

Where the model came from

PICERL is the six-step incident handling cycle from SANS: preparation, identification, containment, eradication, recovery, lessons learned. PIVTR-D keeps all six.

PICERL leaves verification, triage and scope implicit. They happen in every incident whether or not a model names them. PIVTR-D names them so each gets a gate and an owner, which makes them harder to skip under pressure.

Scope, contain, eradicate and recover share the R because they repeat. Giving each its own letter would imply they run once each, in order, and Figure 24 shows they repeat.

LetterPhaseWhat it coversIn PICERL
PPreparationReadiness, authority, tooling, exercises, huntingPreparation
IIdentificationAlerting, detection and hunting, all running continuouslyIdentification
VVerificationEstablish that the event is an incident requiring a responseNamed here. Left implicit.
TTriagePrioritize the incident against organizational objectivesNamed here. Left implicit.
RResponseScope, contain, eradicate and recover, repeating until scoping produces nothing newContainment, Eradication, Recovery, plus scope named here
DDebriefClose the incident and convert it into changesLessons Learned

Verification and triage run together because both need the same conversation with decision makers. The hyphen marks where the incident ends and the closeout begins, and it stops the letters from being read as a word.

Start, work, finish, record

ActivityStarts whenCore workDone whenRecord produced
P. PreparationNo incident running. This is the default statePolicy, authority, playbooks, backups, tooling, exercises, huntingNever closes. Every debrief reopens it with named ownersAuthority matrix, playbooks, asset and contact lists
I. IdentificationTelemetry and reports flowing. Runs continuouslyOperate detections, work alerts, hunt on a cadenceAn event of interest raised with evidence references attachedAlert or hunt finding with evidence references
V, T. Verification and triageAn event of interest with evidence referencesConfirm it requires a response, rank it against organizational objectivesContinue, stop, or defer, with a name and a time against itIncident record, triage brief
R. Response (scope)Verified incident with at least one indicatorDerive indicators, enterprise hunt, progressive sweep, attack timelineSystems, accounts, and data enumerated, with visibility gaps namedScope findings, attack timeline
R. Response (contain)Scope clear enough to act, posture chosen, authority in handStop attacker activity, preserve evidence by volatilityNetwork, process, and log channels all show attacker activity stoppedContainment decision record
R. Response (eradicate)Evidence collected and preservedShort-form investigation, remove persistence, rotate credentials, patchRerunning the enumeration that found the problem comes back cleanRoot cause, eradication log
R. Response (recover)Eradication verifiedVerification checks, validation testing, owner sign-off, restorationSystems in production under enhanced monitoring, owner sign-off on filePre-restoration sign-off, owner acceptance
D. DebriefLoop exited, technical closure and risk acceptance both signedClose temporary assets, consolidate records, metrics, after-action reviewImprovement plan issued with named owners and milestone datesIncident report, metrics, improvement register
Adapts material from Dynamic Incident Response: A Framework for Security Teams by Joshua Wright, © 2026 The Escal Institute of Advanced Technologies, Inc. d/b/a SANS Institute, licensed under CC BY 4.0. Figures reproduced under that license. Changes were made. Not published by, endorsed by, or affiliated with the SANS Institute.