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.
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.
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.
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.
| Letter | Phase | What it covers | In PICERL |
|---|---|---|---|
| P | Preparation | Readiness, authority, tooling, exercises, hunting | Preparation |
| I | Identification | Alerting, detection and hunting, all running continuously | Identification |
| V | Verification | Establish that the event is an incident requiring a response | Named here. Left implicit. |
| T | Triage | Prioritize the incident against organizational objectives | Named here. Left implicit. |
| R | Response | Scope, contain, eradicate and recover, repeating until scoping produces nothing new | Containment, Eradication, Recovery, plus scope named here |
| D | Debrief | Close the incident and convert it into changes | Lessons 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
| Activity | Starts when | Core work | Done when | Record produced |
|---|---|---|---|---|
| P. Preparation | No incident running. This is the default state | Policy, authority, playbooks, backups, tooling, exercises, hunting | Never closes. Every debrief reopens it with named owners | Authority matrix, playbooks, asset and contact lists |
| I. Identification | Telemetry and reports flowing. Runs continuously | Operate detections, work alerts, hunt on a cadence | An event of interest raised with evidence references attached | Alert or hunt finding with evidence references |
| V, T. Verification and triage | An event of interest with evidence references | Confirm it requires a response, rank it against organizational objectives | Continue, stop, or defer, with a name and a time against it | Incident record, triage brief |
| R. Response (scope) | Verified incident with at least one indicator | Derive indicators, enterprise hunt, progressive sweep, attack timeline | Systems, accounts, and data enumerated, with visibility gaps named | Scope findings, attack timeline |
| R. Response (contain) | Scope clear enough to act, posture chosen, authority in hand | Stop attacker activity, preserve evidence by volatility | Network, process, and log channels all show attacker activity stopped | Containment decision record |
| R. Response (eradicate) | Evidence collected and preserved | Short-form investigation, remove persistence, rotate credentials, patch | Rerunning the enumeration that found the problem comes back clean | Root cause, eradication log |
| R. Response (recover) | Eradication verified | Verification checks, validation testing, owner sign-off, restoration | Systems in production under enhanced monitoring, owner sign-off on file | Pre-restoration sign-off, owner acceptance |
| D. Debrief | Loop exited, technical closure and risk acceptance both signed | Close temporary assets, consolidate records, metrics, after-action review | Improvement plan issued with named owners and milestone dates | Incident report, metrics, improvement register |