ICS
2Respond and manage

Sizing the response

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

TypeIn NIMSCyber exampleWritten IAP
5One or two resources, closed within the first operational periodA phishing report with one mailbox affectedNo
4Several resources, one operational period, Command and General Staff not activatedCommodity malware on a handful of endpointsNo. A written objective list is enough
3Some or all Command and General Staff positions activated, multiple operational periodsBusiness email compromise with a fraudulent payment, ransomware on one siteYes, each period
2Needs resources beyond local capability, most positions filledEnterprise ransomware with an outside response firm and an insurerYes, each period
1The most complex, all positions filled, national-level resourcesA disruption of critical infrastructure with government coordinationYes, each period

Example

If your organization already uses severity levels, map them once, in writing, and publish the mapping.

SeverityTypeCommand
SEV 45Analyst in command
SEV 34IC and Operations lead
SEV 23Command and General Staff as needed
SEV 12 or 1Full organization, unified command likely

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.

Order of growth

Add positions in the order the workload usually arrives: an Operations lead, then a Public Information Officer, then Planning with documentation first, then Liaison, then Logistics, then Finance/Admin. Safety joins as soon as shifts run past twelve hours or containment touches a physical process.

When to shrink

Fold positions back as their workload drops, returning their duties to the person above them. The IC announces each change and updates the organization assignment list.

Start with three

For Type 4 incidents, and as the core of every larger one, fill three roles: incident commander, communications lead and operations lead. They are the core roles in Google's incident management system, IMAG, which is built on ICS, so they grow into the full organization without renaming anything. Add Planning when the incident runs past one shift. See Respond and manage.

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.