ICS
2Respond and manage

Sizing the response

NIMS sorts incidents into five complexity types, from Type 5, the smallest, to Type 1, the most complex. The type tells you which positions to fill and whether the plan must be written down.

TypeIn NIMSCyber exampleOther exampleWritten IAP
5One or two resources, closed within the first operational periodA phishing report with one mailbox affectedA failed disk in one server, replaced the same dayNo
4Several resources, usually one operational period, Command and General Staff functions activated only if neededCommodity malware on a handful of endpointsA cooling failure in one data center hall, fixed within the shiftNo. The ICS 201 is the plan and the briefing for incoming resources
3Some or all Command and General Staff positions activated, multiple operational periodsBusiness email compromise with a fraudulent payment, ransomware on one siteA data center flood that runs for a day or moreMay be required each period
2Needs resources beyond local capability, most positions filledEnterprise ransomware with an outside response firm and an insurerA regional power outage that closes a site for several days, with outside contractorsYes, each period
1The most complex, all positions filled, national-level resourcesA disruption of critical infrastructure with government coordinationA hurricane that closes several sites and needs government coordinationYes, each period

Severity and type

PIVTR-D, the companion response manual, rates risk from Low to Critical, and many organizations already use SEV levels. The table maps them onto each other and onto the type.

Every incident gets two ratings. Severity measures impact, and sets how fast and how high the incident is reported. Complexity type measures how hard the incident is to manage, and sets how large the organization is. A single stolen laptop full of patient records can be high severity and Type 5, and a noisy but harmless worm across three data centers can be low severity and Type 3.

PIVTR-D risk levelSeverityFirst reportFull reportUsual starting type
LowSEV 4Within 2 daysWithin 5 business days5
MediumSEV 3Within 4 hoursWithin 72 hours5 or 4
HighSEV 2Within 2 hoursWithin 48 hours4 or 3
CriticalSEV 1Within 1 hourWithin 24 hours3, 2 or 1

The reporting deadlines are Wright's sample SLA, Table 5, p. 84. The severity labels and starting types are placeholders. Replace them with your own and publish the result once, in writing.

Choosing the type

Start at Type 5 and move up to the highest row that is true. Re-check at every operational period, because the type can go down as well as up.

If this is trueThe type is at least
One or two people can close it within the first operational period5
It needs several people or teams, but should close within one operational period4
It will run past one operational period3
A supervisor would have more than seven people reporting3
It needs people or tools beyond what the organization has, such as an outside response firm2
It disrupts critical infrastructure or needs coordination with government at a national level1

Rows follow the NIMS complexity type descriptions in FEMA's IS-200 course.

When to grow

  • A supervisor has more than seven people reporting.
  • The incident will run past the current operational period.
  • An outside response firm, insurer, regulator or law enforcement agency is engaged.
  • Customers, the public or the media will hear about it.
  • Containment could affect a physical process or anyone's safety.
  • Two parts of the organization claim authority over the same systems.
  • Business operations are disrupted beyond the technology estate: activate the crisis team as well. See Above the incident.

Adding and removing positions

Add each seat when its trigger is met. The earliest type is where the seat usually appears, and any incident can need one sooner.

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

Fold positions back as their workload drops, returning their duties to the person above them. The Incident Commander announces each change, and Planning's Resources unit updates the organization assignment list.

Every larger organization grows from the three core roles in Start with three roles.

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.