ICS

Quick card

The first 30 minutes of command, and what to fill as it grows.

If you have not taken command yet, start at Incident running now.

Open the forms

First 30 minutes

#ItemDone when
1Take command out loud: your name, the time, the incident name and where the command bridge is. Open your activity log (ICS 214).The announcement is in the channel and the first log entry has a time.
2If someone was in command before you, take a briefing from them, using the ICS 201 if one exists.You can say what is affected and what has been done so far.
3Open a command bridge and an out-of-band channel, and record both in the ICS 205. Treat email, chat and identity as visible to the attacker until scoping shows otherwise.Every responder has joined the out-of-band channel.
4Size up: what happened, what is affected, what is still happening and what is unknown.Each of the four has a written answer, even if the answer is unknown.
5Set up to three objectives, each with an outcome, a measure and a time. Examples are in Writing objectives.The objectives are written where every responder can read them.
6Name an Operations Lead, or an Operations Section Chief from Type 3, and hand over the technical work. Stay off the keyboard.The Operations Lead has accepted and briefed the technical responders.
7Decide the incident type, 5 to 1, with the type chooser, and fill the positions it calls for.The type is logged and each seat it calls for has a name against it.
8Confirm your authority limits, and who approves anything above them.You have the name and number of the executive above you.
9Tell counsel if personal data, regulators, law enforcement, extortion or insurance may be involved. The clocks are in notification deadlines.Counsel has acknowledged, or the log says why they were not called.
10Set the times of the first briefing and the first executive update, using the update schedule for the severity.Both times are announced and in the log.
11Write the incident briefing (ICS 201) before the first briefing.The ICS 201 is filed where the next Incident Commander will find it.
12Check hours: who has been awake since when, and who relieves them. Record hazards and rest rules in the ICS 208.Every responder has a relief time.

When to fill each seat

SeatFill itEarliest type
Incident CommanderEvery incident. At Type 5 it is often the analyst who found it. From Type 2, add a Deputy Incident Commander, or a second Incident Commander for alternate periods.5
Deputy Incident CommanderWhen the Incident Commander needs relief across operational periods or has command work to hand off. Must be able to take over command at any time.2
Operations Section ChiefEvery incident above Type 5. At Type 4 the seat is the Operations Lead, who becomes the Operations Section Chief at Type 3.4
Division/Group SupervisorEvery group or division Operations sets up. Each leads three to seven people.4
Public Information OfficerAs soon as anyone outside the response team has to be told.4, as Communications Lead
Planning Section ChiefWhen the incident runs past one shift.3
Situation, Resources and Documentation Unit LeadersWhen the Planning Section Chief can no longer do the unit's work alone. Documentation from the start when litigation, a regulator or an insurance claim is likely.3
Liaison OfficerWhen outside parties are engaged.3
Legal advisorWhen personal data, regulators, law enforcement, extortion or insurance may be involved.Any, when a trigger applies
Safety OfficerWhen the incident runs past one operational period, or when containment could touch a physical process.3
Logistics Section ChiefWhen responders need access, tools or facilities the response team cannot arrange for itself.2
Finance/Admin Section ChiefWhen outside costs, contracts or insurance claims begin.2
Intelligence/InvestigationsWhen the investigation is the main effort, law enforcement works alongside, or counsel directs the investigation for privilege.2
Technical SpecialistWhen the response needs a skill nobody on the roster has, such as a forensic analyst, a negotiator or an OT engineer.Any

Each seat has a job aid in Position checklists.

Each operational period

  1. Objectives meeting
  2. Command and General Staff meeting
  3. Tactics meeting
  4. Planning meeting
  5. IAP approved by the IC
  6. Operations briefing, and the period starts
  7. Execute and assess, with status to Planning
  8. Executive updates at the times the IAP sets

Rules at every size

  • Name one Incident Commander, out loud.
  • Give each responder one boss for the length of the incident.
  • Keep three to seven people per supervisor, and split the work before an eighth joins.
  • Write objectives before tactics.
  • Speak to executives and the public with one voice, through the Public Information Officer.
  • Make every update say what is affected, how bad it is, what to do now, and when it will be fixed or the next update is due.
  • Hand over by briefing, announce it to everyone, and log it with the time.
  • Give everyone an assignment before they join the response.
Adapted from the National Incident Management System, Third Edition (FEMA, 2017). Cyber adaptation, examples and templates by Habib Tora, licensed under CC BY 4.0. Not published by, endorsed by, or affiliated with FEMA or the Department of Homeland Security. Structure after Google's SRE Incident Management Guide. Companion to PIVTR-D.