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.
| Type | In NIMS | Cyber example | Other example | Written IAP |
|---|---|---|---|---|
| 5 | One or two resources, closed within the first operational period | A phishing report with one mailbox affected | A failed disk in one server, replaced the same day | No |
| 4 | Several resources, usually one operational period, Command and General Staff functions activated only if needed | Commodity malware on a handful of endpoints | A cooling failure in one data center hall, fixed within the shift | No. The ICS 201 is the plan and the briefing for incoming resources |
| 3 | Some or all Command and General Staff positions activated, multiple operational periods | Business email compromise with a fraudulent payment, ransomware on one site | A data center flood that runs for a day or more | May be required each period |
| 2 | Needs resources beyond local capability, most positions filled | Enterprise ransomware with an outside response firm and an insurer | A regional power outage that closes a site for several days, with outside contractors | Yes, each period |
| 1 | The most complex, all positions filled, national-level resources | A disruption of critical infrastructure with government coordination | A hurricane that closes several sites and needs government coordination | Yes, 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 level | Severity | First report | Full report | Usual starting type |
|---|---|---|---|---|
| Low | SEV 4 | Within 2 days | Within 5 business days | 5 |
| Medium | SEV 3 | Within 4 hours | Within 72 hours | 5 or 4 |
| High | SEV 2 | Within 2 hours | Within 48 hours | 4 or 3 |
| Critical | SEV 1 | Within 1 hour | Within 24 hours | 3, 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 true | The type is at least |
|---|---|
| One or two people can close it within the first operational period | 5 |
| It needs several people or teams, but should close within one operational period | 4 |
| It will run past one operational period | 3 |
| A supervisor would have more than seven people reporting | 3 |
| It needs people or tools beyond what the organization has, such as an outside response firm | 2 |
| It disrupts critical infrastructure or needs coordination with government at a national level | 1 |
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.
| Seat | Fill it | Earliest type |
|---|---|---|
| Incident Commander | Every 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 Commander | When 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 Chief | Every 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 Supervisor | Every group or division Operations sets up. Each leads three to seven people. | 4 |
| Public Information Officer | As soon as anyone outside the response team has to be told. | 4, as Communications Lead |
| Planning Section Chief | When the incident runs past one shift. | 3 |
| Situation, Resources and Documentation Unit Leaders | When 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 Officer | When outside parties are engaged. | 3 |
| Legal advisor | When personal data, regulators, law enforcement, extortion or insurance may be involved. | Any, when a trigger applies |
| Safety Officer | When the incident runs past one operational period, or when containment could touch a physical process. | 3 |
| Logistics Section Chief | When responders need access, tools or facilities the response team cannot arrange for itself. | 2 |
| Finance/Admin Section Chief | When outside costs, contracts or insurance claims begin. | 2 |
| Intelligence/Investigations | When the investigation is the main effort, law enforcement works alongside, or counsel directs the investigation for privilege. | 2 |
| Technical Specialist | When 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.