ICS
2Respond and manage

Above the incident

Incident command runs the incident. When the incident reaches the whole organization, NIMS adds three structures above and around it. Each has its own job, and keeping the jobs separate leaves the Incident Commander free to run the response.

Emergency operations center: the crisis team

An EOC supports incident command and manages consequences away from the incident. In a cyber incident that is the crisis management team: business continuity, operations, finance, HR, facilities and customer operations, led by an executive other than the Incident Commander. It runs manual workarounds while systems are down, keeps customers served, finds extra staff and money, and tells the Incident Commander what the business needs.

Activate it when business operations are disrupted beyond the technology estate, when the incident will run past a day, or when the response needs resources beyond the Incident Commander's authority.

Activation levels

NIMS names three EOC activation levels. The crisis lead sets the level, and the Incident Commander may ask for a higher one.

LevelNIMS nameCrisis teamWhen
3Normal operations/steady stateThe crisis lead on call reads each ICS 209SEV 2 to 4 with no business disruption
2Enhanced steady state/partial activationThe crisis lead and affected functions meet at set timesAny SEV 1, an incident that will run past a day, or a need for resources beyond the Incident Commander's authority
1Full activationThe whole team, in session through the working dayBusiness operations disrupted beyond the technology estate

First crisis team meeting

The crisis lead runs it in 30 minutes.

#ItemWho
1Situation from the latest ICS 209Incident Commander
2Impact by function: what stopped, what has a workaround, what fails next and whenEach business function
3Workarounds to start, each with an ownerEach business function
4Deadlines to customers, regulators, contract partners and the insurerLegal advisor
5Resource requests beyond command authority, and decisions for the executive groupCrisis lead
6Messages to staff and customersPublic Information Officer
7Next meeting, set to the executive update scheduleCrisis lead

Multiagency coordination group: the executive decision group

A MAC group is a small set of executives who set policy and priorities when demands exceed resources or several incidents compete. In cyber: the chief executive, general counsel, finance, operations, security and technology leadership, with the board kept informed.

They decide what only they can decide: taking a line of business offline, which business unit restores first, and public disclosure. They also decide any engagement with an extortionist, with counsel advising on legal and sanctions exposure, and spending beyond set limits. They leave tactics to the Incident Commander.

Ranking competing incidents

NIMS gives MAC groups the job of supporting resource prioritization and allocation. When two incidents want the same people, the executive group ranks them on these criteria, in order.

  1. Life safety: any risk to people, or to a physical process that keeps people safe.
  2. Legal deadlines: a notification clock that has started, then one about to start, then contract and regulator deadlines.
  3. Business impact: services, customers and revenue affected now.
  4. Spread: an incident still spreading, or with the attacker still inside, ranks above a contained one of equal impact.

Each Incident Commander presents from a current ICS 209. Break a tie with each incident's cost of delay. The executive group records the ranking in the decision register, tells each Incident Commander which people and tools they keep, and ranks again when either severity changes.

Briefing executives

Brief at the times in the communications standards. For a SEV 1: first within 1 hour, then every 30 minutes until mitigated, then every 2 hours. For a SEV 2: first within 2 hours, then hourly until mitigated, then every 4 hours.

10-minute executive briefing

MinutesItemWho
0 to 1Purpose, and the decisions needed today with their deadlinesIncident Commander
1 to 4Situation from the current ICS 209: what is affected, how bad, whether it is growingIncident Commander
4 to 6Progress on each objective, and what changes by the next briefingIncident Commander
6 to 7Notices made and dueLegal advisor
7 to 9Each decision request. Executives decide or set a time to decideIncident Commander
9 to 10Messages cleared, and the time of the next briefingPublic Information Officer

Script for opening the executive briefing

This is the [time] executive briefing for [incident name]. I am
[name], Incident Commander. We have 10 minutes and [number]
decisions for you, the first needed by [time]. The situation comes
from the status summary issued at [time], and each fact is marked
confirmed, probable or unknown. Save questions until the end of
each part. The next briefing is at [time].

Executive decision request

EXECUTIVE DECISION REQUEST
Incident name and number:          Request number:
From (Incident Commander):         To (executive group):
Decision needed:
Needed by (date, time, time zone), and why then:
Options
  A.                  Cost:          Risk:          Effect on objectives:
  B.                  Cost:          Risk:          Effect on objectives:
Recommendation, and the reason:
Cost of delay (what each hour or day without a decision costs):
Legal advisor's view:
Decided: option          by (name, title)          at (date, time)
Conditions attached:
Logged in the decision register by:

Board updates

Board updates start from the ICS 209, so the board reads the facts the executives read. Board and government reporting sets the rules and cadence.

  1. Planning issues the ICS 209 as of a stated time, and the Incident Commander approves it.
  2. The executive sponsor writes the board update from it, adding context and keeping each fact as the ICS 209 states it.
  3. The Legal advisor reviews it, and the approval is recorded.
  4. Documentation files the version sent and its recipients.

Joint information system: one set of public facts

A JIS coordinates public information across every organization involved. A supplier breach that reaches your customers, or an incident with law enforcement, an insurer and a managed provider involved, puts several communications teams in front of the same audience. The JIS keeps their statements consistent: shared facts, agreed timing, each party speaking for its own part.

A joint information center is where those communicators work together, in a room or on a bridge.

How they connect

FromToWhat flows
Incident commandCrisis team (EOC)Status summaries, and resource requests beyond command authority
Crisis team (EOC)Incident commandResources, business priorities, decisions within the crisis team's authority
Crisis team (EOC)Executive group (MAC)Decisions that need executive authority, with options and business impact
Executive group (MAC)Crisis team and incident commandPriorities, policy decisions, allocation of scarce resources
Every levelJoint information systemVerified facts cleared for release
Joint information systemEvery levelApproved statements and their timing
Keep the jobs apart

Watch for executives directing tactics from the crisis room. Give them the decisions only they can make, on a written list, and route everything else to the incident through the Incident Commander.

Built from NIMS, third edition (October 2017), on the MAC group's role, and the NIMS EOC activation levels as taught in FEMA's E/L/G 2300 Intermediate EOC Functions course. The triggers, agendas, script, decision request, ranking criteria and board steps are additions to this guide.

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.