RResponse loop
Scope
STARTS WHENVerified incident with at least one indicator.
DONE WHENSystems, accounts, and data enumerated, with visibility gaps named.
RECORDSScope findings and the attack timeline, with each pass logged in T4 Loop iteration log.
Scope finds every system, account and dataset in the incident, and its potential impact on the organization. Start from what identification and verification produced. Work out the attacker's tactics, techniques and procedures (TTPs), derive indicators from them, and use those indicators to find every system in scope.
Scope before cleaning anything. Cleaning only the systems you already know about leaves the attacker the rest, and the incident reopens when they use them.
Scope
| # | Item | Owner |
|---|---|---|
| 1 | List every indicator from detection and verification, and make each one searchable | Intelligence/Investigations |
| 2 | Hunt for the indicators across the security information and event management (SIEM) platform, endpoint detection and response (EDR) and any threat hunting platform | Operations |
| 3 | Sweep in order: critical assets, then lateral expansion, then the environmental sweep (table below) | Operations |
| 4 | Identify the initial compromise and patient zero | Intelligence/Investigations |
| 5 | Map lateral movement through authentication logs and file access patterns | Intelligence/Investigations |
| 6 | Date the deployment of each persistence mechanism | Intelligence/Investigations |
| 7 | Establish when sensitive data was accessed or exfiltrated | Intelligence/Investigations |
| 8 | Document visibility gaps: unmanaged systems, thin logging, Internet of Things (IoT) devices, industrial devices | Planning |
| 9 | For controllers and similar equipment with no central logging, use network flow data as the primary source | Intelligence/Investigations |
| 10 | Check for anti-forensics: log deletion, timestomping, obfuscation, living off the land | Intelligence/Investigations |
| 11 | For cloud and hybrid estates, cover cloud audit logs and container runtime security | Operations |
Sweep stages
| Sweep stage | Targets | Sources |
|---|---|---|
| Critical assets first | Domain controllers, file servers, databases, anything that stores sensitive data, regardless of where the first indicator appeared | SIEM, EDR, authenticated scans |
| Lateral expansion | Same segment, systems authenticated to by compromised accounts, systems sharing administrative credentials | Authentication logs, EDR, network flow |
| Environmental sweep | Everything remaining. Days or weeks at scale. | EDR, inventory tools, scripted checks, compromise assessment tooling |
Decisions and records
- Expanding scope to another business unit follows who authorizes what.
- Log each pass in T4. Scope owns the attack timeline. Eradication annotates it, and the debrief finalizes it.
- Move the compromise start key time in T1 earlier whenever scoping finds older evidence, as Metrics defines it.
- The scenario page for the incident type lists the log sources and questions that matter most. Evidence collection covers what to preserve as scope grows.
Watch out
- In operational technology (OT) the visibility gap is the normal condition. Controllers do not log centrally, agents cannot be installed, and maintenance windows can be months away. Plan on network flow as the primary evidence source, and write that into the response plan before it is needed.