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
| Trigger | Looks like | Next move |
|---|---|---|
| New indicators | A PowerShell script in a registry key, traffic to an unknown command and control (C2) server | Back to scoping with the new indicator |
| Scope expansion | A known compromised service account also active in a regulated system | Another scoping pass, with new stakeholders and new obligations |
| Incomplete eradication | A system that looked clean shows reinfection | Hunt the missed persistence or the unidentified access vector |
| Analysis revelations | Memory forensics finds a second malware family | Rescope, then revisit containment and eradication |
| Business change | A new obligation or a shift in priorities | Re-triage and reset the plan with decision makers |
Before exiting
| # | Item | Owner |
|---|---|---|
| 1 | Scoping produces no new indicators | Intelligence/Investigations |
| 2 | Monitoring shows no attacker activity | Intelligence/Investigations |
| 3 | Eradication verification confirms removal | Operations |
| 4 | Restored systems operate normally | Operations |
| 5 | Operational objectives are met and residual risk is acceptable | Incident Commander |
| 6 | Cost and benefit no longer favor active response | Incident Commander |
| 7 | Regulatory conditions for closure are satisfied | Legal advisor |
| 8 | Ongoing monitoring is decided and has an owner | Incident Commander |
| 9 | Technical closure is signed and residual risk accepted, both with names and times | Incident 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.