Home/Refreshers/Incident command: roles and rhythm: refresher
Incident command: roles and rhythm
Five roles adapted from the Incident Command System, the rhythm they work to, and how they pass from one person to a team.
Remember
- A role nobody has taken stays with the commander.
- The commander stays off the consoles once a second person joins.
- Each operational period starts with a briefing: objectives, situation, assignments, decisions, next times.
- Objectives are checkable. Every key the attacker made is disabled, for example.
- Command changes hands only with a briefing and a line in the channel naming the new commander.
| Role | Does |
|---|---|
| Incident commander | Objectives, priorities, containment that breaks production, the timeline |
| Operations | Preserve, scope, contain, and eradicate on the consoles |
| Planning, or scribe | Timeline, decision log, evidence register |
| Communications | Updates to leadership, staff, and customers; notices drafted with Legal |
| Liaison | Cloud provider support, outside firms, insurers, law enforcement |
The rhythm
- 1. Declare Name the commander in the channel. Open the decision log and record when the alert arrived.
- 2. First hour Preserve, scope, contain with the agreed actions, and send the first update.
- 3. Call Legal When personal data, an SEC filer's material systems, an insider, or law enforcement may be involved.
- 4. Each period Brief, assign by name, record decisions: time, decision, who, evidence, options set aside, owner, revisit by.
- 5. Hand over Objectives, what is open, decisions waiting, roles, next times, where the log is.
Watch out
- A lone responder drops the log and the updates first. Keep both, one line at a time.
- Disclosure clocks run from awareness or a materiality decision. Record both moments. This is not legal advice.
Check it worked
Every decision in the log has a time, an owner, and the evidence it rested on, and each review finding has a change and an owner.