ICS
2Respond and manage

Unified command

Unified command is how several parties with authority over the incident run one response. They agree one set of objectives and one plan. Each keeps authority over its own people and budget, and none acts outside the plan without telling the others.

Who sits in it

A party joins unified command when it has authority or accountability for part of the response.

PartyJoins whenOtherwise
Technology leadershipSystems will be isolated, rebuilt or restoredSupports through Operations
Security leadershipEvery incident, for investigation and containmentTakes command, or leads Operations
OT or engineeringPlant or physical systems are affected or at riskAdvises the Safety Officer
The affected businessOperations, customers or revenue are affectedReceives updates
CounselLegal exposure is driving decisionsLegal advisor to command
Managed security providerIt takes containment actions under its contractWorks through Operations
Law enforcementIt has authority over part of the response, as in some public-sector incidentsThrough Liaison

Rules

  • One set of objectives and one IAP, approved by every member.
  • One Operations Section Chief, whatever the number of members.
  • One voice outside the incident, through the Public Information Officer.
  • Members sit together, or on one bridge, during planning.
  • A member who must act outside the plan says so first and the others hear it before it happens.

The initial unified command meeting

Run it once, after the incident briefing (ICS 201) and before the first objectives meeting, as the Planning P shows. FEMA's ICS 300 course limits it to the members, who arrive having read the agenda.

Planning records the outcomes in the first IAP. The members agree:

  1. Each member's priorities, objectives and authority.
  2. Each member's limits: systems it may not touch, change freezes, notice duties, contract terms.
  3. One set of objectives, each with an outcome, a measure and a time.
  4. The order of priorities and the overall strategy.
  5. The organization, and whose people staff each section.
  6. One Operations Section Chief, the best qualified and acceptable to all.
  7. Planning, logistics and finance arrangements, such as whose accounts responders use.
  8. How resources are ordered, on one resource request.
  9. Who pays for what.
  10. How information is released: one Public Information Officer, or a joint information system.
  11. One spokesperson for unified command.
  12. For cyber: the out-of-band channel, how members verify each other, and what each may do alone.

Settling disagreements

In FEMA's ICS 300 course, each member presents its limitations, concerns and restrictions at the initial meeting. When members disagree after that, work through these steps.

  1. State the disagreement as two or three options, each with its effect on the objectives.
  2. Each member names the authority, obligation or risk behind its position.
  3. Look for an objective every member can sign: sequence the actions, split the work by division, or try one option for a set time.
  4. Set a deadline: the end of the meeting, or one hour during active containment.
  5. Past the deadline, send it to the executive group on an executive decision request that gives each member's position in its own words.
  6. Until the answer comes back, the current IAP stands, and each member keeps authority over its own people and systems.

Some questions go to the executive group even when the members agree: anything beyond a member's delegated authority or spending limit, and taking a line of business or shared service offline. Public disclosure, contact with an extortionist, and conflicts between members' legal obligations also go to the executive group. When the members come from two organizations, each names its escalation executive in advance, and those executives form the executive group.

Objectives and signatures

Unified command writes one ICS 202. Write each objective once, in words every member accepts, and name in each ICS 204 whose people carry the assignment.

FEMA's ICS 202 instructions let one Incident Commander approve for a unified command, with further signatures on an attached page. This guide asks every member to sign the IAP cover sheet, because each commits its own people and budget. Treat a missing signature as a disagreement and settle it before the operations briefing.

Members may name one of themselves to speak for unified command in meetings and briefings. The members together fill the Incident Commander's role.

Two cyber pairings

Your organization and a managed service provider

The provider runs your detection and response platform, has administrative rights, and takes containment actions under its contract. You own business decisions, notifications and counsel. The provider owns actions inside its platform.

Example

Joint objectiveCarried by
Every finance-segment host isolated, or confirmed clean in EDR telemetry, by 18:00 TuesdayProvider analysts, under the IAP's standing list
Provider access limited to the engineers on the IAP roster, with MFA confirmed and older sessions revoked, by 16:00Provider, checked by your identity team
Alert and action logs for the incident window in your evidence store, hashed and registered, by 09:00 WednesdayProvider, received by Intelligence/Investigations

A subsidiary and its parent

The parent runs shared identity, network and security tools. The subsidiary runs its own systems and answers to its own customers and regulators.

Example

Joint objectiveCarried by
Every subsidiary account in the shared directory reset, with tokens revoked, by 20:00, from a list the subsidiary confirmsParent identity team
Connections between the two networks limited to the services named in the IAP by 17:00, each business impact accepted by the subsidiaryParent network team
Subsidiary customer data exposure scoped, each affected data set listed with evidence, by 12:00 Thursday, in time for the subsidiary's notice decisionSubsidiary investigation group, using the parent's logs

Advisors to unified command

Seats go to parties with authority or functional responsibility for part of the response. The insurer, outside counsel and the outside response firm work under contract to a member, so they advise.

Outside counsel advises through the Legal advisor, the response firm's lead works inside Operations or Intelligence/Investigations, and the insurer works through Liaison and Finance/Admin. Record each advisor's advice by name. The members decide and sign.

Counsel, managed providers and insurers

If counsel directs the investigation to preserve privilege, record that in the IAP. Documentation, the forensic report and outside responders' deliverables then follow counsel's routing, and Planning keeps the record index to match.

A provider that can isolate hosts or disable accounts in your environment acts inside the plan. Agree in advance which actions it takes on its own authority and which need the Operations Section Chief, then write that list into the IAP so the night shift knows it too.

An insurer may require notice within a set time and may direct which response firms and counsel you use. It works through Liaison and Finance/Admin, and its requirements go into the IAP as constraints.

Built from NIMS, third edition (October 2017), on membership and assisting agencies; FEMA's ICS Training Reference Guide (March 2023) on the spokesperson; FEMA's ICS 300 course, Lesson 4, for the meeting agenda and each member's limitations; and the ICS 202 instructions on approval. The disagreement steps, escalation list and pairings 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.