Incident running now
Pick the line that describes you.
I found somethingWork the first hour below, in order.
I am leading the responseThe Incident Commander's first 30 minutes, in Incident Command.
I am scoping or containingGo to the response loop and the playbook for your step.
I know what happened and who we areBuild one sheet with the scenario, sector and cloud first moves.
I am joining halfway throughRead the lifecycle, then ask the Incident Commander for the current T4 entry.
The first hour
Items 1 to 4 fall to whoever found the incident. From item 5 the Incident Commander owns the list, which may still be the same person. Log every action with the time in Coordinated Universal Time (UTC) from item 1 onward.
| # | Item | Owner | Done when |
|---|---|---|---|
| 1 | Record what you saw, where and when, in your activity log. | Finder | The observation and its time are written down. |
| 2 | Decide whether this is an incident, using Verification and triage, and open the T1 incident record with an identifier. | Finder | The decision is in T1 with the evidence references, a name and a time. |
| 3 | If it is an incident, open the matching scenario page. Where one applies, open the sector page for your organization, which lists the reporting clocks. | Finder | CLASSIFICATION and SECTOR RULES are filled in T1. |
| 4 | Name an Incident Commander. Until someone else takes over by briefing, it is you. | Finder | The Incident Commander's name is in T1 and announced to the responders. |
| 5 | Move the response to an out-of-band channel if email, chat or identity could be in the attacker's hands. | Incident Commander | Every responder has joined the out-of-band channel. |
| 6 | Check the four triggers in When containment cannot wait: active destruction, exfiltration, safety or critical systems, and a regulatory clock. If one applies, take its approved action now. | Incident Commander | Each trigger is marked yes or no in T1. |
| 7 | Preserve volatile evidence in order: memory, then running processes and network connections, then logs that could rotate or be deleted. The Incident Commander decides for each host whether to collect before or after isolating, as set out in Evidence collection. | Operations | Each item is in the evidence register with a hash and a custodian. |
| 8 | Delay changes the attacker would notice, such as reimaging, bulk password resets and blocking their infrastructure, until a containment posture is chosen. A containment trigger that applies now overrides this. | Incident Commander | The posture is recorded in T3. |
| 9 | Rate the risk level and look up what it triggers in Risk levels. | Incident Commander | The level and the rationale are in T1. |
| 10 | Tell counsel if personal data, regulators, law enforcement, extortion or insurance may be involved. Counsel decides when the insurer and any regulator are told, using the notification deadlines, T13 for the insurer and law enforcement, and T17 for each regulator. | Incident Commander | Counsel has acknowledged, or T1 says why they were not called. |
| 11 | Send the T2 triage brief to the decision makers within the reporting deadline for the risk level, with the time of the next update. | Incident Commander | T2 is sent and the next update time is in the log. |
| 12 | If staff will notice the incident, send the T12 staff notice, and set when each audience gets a T11 status update. | Incident Commander | T12 is sent or the log says why not, and the next T11 time for each audience is in the log. |
With the first hour done, start the scope step of the response loop. If the incident will run past one shift, the Incident Commander grows the organization using Sizing the response.