PIVTR-D
RResponse loop

Running the response loop

STARTS WHENVerification says continue. Any new fact that changes scope, containment, eradication or recovery starts another pass.
DONE WHENScoping produces no new indicators, and technical closure and residual risk acceptance are signed with names and times.
RECORDSOne T4 Loop iteration log per pass, then T5 Technical closure and T6 Residual risk acceptance at exit.

Put the same question to every new fact: does this change scope, containment, eradication or recovery? If it does, the team is on another pass.

Say so on the bridge, because silence reads as progress and stakeholders start planning the all-clear. Each scenario page lists what the loop adds for that incident type.

Start another pass

TriggerLooks likeNext move
New indicatorsA PowerShell script in a registry key, traffic to an unknown command and control (C2) serverBack to scoping with the new indicator
Scope expansionA known compromised service account also active in a regulated systemAnother scoping pass, with new stakeholders and new obligations
Incomplete eradicationA system that looked clean shows reinfectionHunt the missed persistence or the unidentified access vector
Analysis revelationsMemory forensics finds a second malware familyRescope, then revisit containment and eradication
Business changeA new obligation or a shift in prioritiesRe-triage and reset the plan with decision makers

Before exiting

#ItemOwner
1Scoping produces no new indicatorsIntelligence/Investigations
2Monitoring shows no attacker activityIntelligence/Investigations
3Eradication verification confirms removalOperations
4Restored systems operate normallyOperations
5Operational objectives are met and residual risk is acceptableIncident Commander
6Cost and benefit no longer favor active responseIncident Commander
7Regulatory conditions for closure are satisfiedLegal advisor
8Ongoing monitoring is decided and has an ownerIncident Commander
9Technical closure is signed and residual risk accepted, both with names and timesIncident Commander

Decisions and records

  • Name the person who authorizes the exit, from who authorizes what. An attributed written decision stands if the incident is reopened or reviewed, and people commit more carefully when their name is on it.
  • Log every pass in T4: the trigger, and the changes to scope, containment, eradication and recovery.
  • At exit, sign T5 and T6.
Watch out
  • Rotate people and schedule rest. Fatigue accumulates across iterations, so track hours worked in the incident record.
  • Documentation has to survive shift handover, or incoming analysts repeat work or skip it. Use the shift handover checklist in Incident Command.

Why it loops

A straight line through contain, eradicate and recover misses whatever becomes visible only after the evidence has been read, as Figures 67 and 68 show.

Linear flow from attacker through Contain, Eradicate and Recover, with three missed threats marked around the sequence.
Figure 67. Three threats pass through unnoticed.
Circular flow of Scope, Contain, Eradicate and Recover with three threat icons inside the loop, each caught on a successive iteration.
Figure 68. The same three threats, caught across successive passes.
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.