ICS
2Respond and manage

The organization

One commander at the top, a Command Staff beside them for the things only command should own, and a General Staff below who run the work. Positions are filled only when the incident needs them. An empty box on the chart is a job the Incident Commander still carries.

Incident Commanderor Unified CommandDeputy ICCOMMAND STAFFPublic Information OfficerCommunications LeadSafety Officerfatigue, OT, personal safetyLiaison Officeroutside partiesLegal advisorprivilege, notification clocksGENERAL STAFFOperationsthe response workInvestigation groupContainment groupEradication groupRecovery groupOT groupPlanningsituation, plan, recordSituation unitResources unitDocumentation unitDemob unitLogisticsaccess, tools, peopleAccess and accountsTools and hardwareFacilities and commsResponder supportFinance/Admintime, cost, claimsTime unitProcurement unitCost unitClaims unitIntel / Investigationsoptional sectionForensicsThreat intelligenceEvidence custody
The incident organization with cyber units. Dashed boxes are optional. Colors mark the sections: red for Operations, blue for Planning, amber for Logistics, green for Finance/Admin.

Command

Incident Commander

Owns. Objectives and priorities, approval of the Incident Action Plan, and orders for resources beyond the sections' authority. Also what goes to executives and the public, transfer of command, and the call to demobilize.

First hour. Takes command out loud, sizes up, writes objectives, names an Operations Lead, opens communications and sets the first briefing.

Rule. The Incident Commander stays off the keyboard, because an Incident Commander doing technical work leaves nobody watching the whole incident.

In cyber. The Incident Commander needs authority agreed in advance to isolate systems, suspend accounts, activate retainers and spend money. Write it into policy with business-impact and spending limits.

Deputy. A Deputy Incident Commander has the same qualification. The deputy runs command while the Incident Commander rests, takes delegated work such as coordinating unified command members, and, when assigned, is the default relief at shift change.

Public Information Officer

Owns. Every message leaving the incident organization: executive updates, staff notices, customer and partner statements, media, status pages.

In cyber. Drafts from the incident status summary so every audience gets the same numbers. Clears wording with Legal. Routes attacker contact, extortion notes and leak-site posts to the Incident Commander and the Legal advisor, unanswered.

Safety Officer

Owns. Authority to stop any action that puts people at risk, and the plan that keeps responders fit to work.

In cyber. Watches three risks. Responder fatigue: shift lengths, rest, handover. Physical processes: where containment touches operational technology, isolating a controller or a segment can stop a process or disable a safety system. Engineering signs off first. Personal safety: staff named in extortion or doxxing get support and, where needed, protection.

Liaison Officer

Owns. The single point of contact for outside parties that are not in command.

In cyber. The outside response firm's engagement lead, the insurer and breach coach, law enforcement, regulators, the ISAC, managed service providers, suppliers, and major customers' security teams. Keeps a log of every commitment made to them.

Owns. NIMS lets command add technical specialists as advisors. This guide adds counsel at any type when personal data, regulators, law enforcement, extortion or insurance may be involved. Counsel covers privilege, notification obligations and their clocks, law enforcement engagement, contracts with responders, and review of anything said outside the organization.

General Staff

Operations Section Chief

Owns. The response work, organized to meet the IAP's objectives. Builds groups, names their supervisors, keeps span of control inside three to seven.

In cyber. This is where the PIVTR-D response loop runs: investigation and scope, containment, eradication and recovery, with an OT group where plant systems are involved. Reports status to Planning on the cadence the IAP sets.

Planning Section Chief

Owns. The situation picture, the Incident Action Plan and the planning cycle, resource status, documentation, and the demobilization plan.

Units. Situation: scope, attack timeline, status summary. Resources: who is assigned, resting, and relieving whom. Documentation: activity logs, decision records, the evidence register index. Demobilization: release plan and check-out.

In cyber. Owns the attack timeline and the incident record, the two documents every later review depends on.

Logistics Section Chief

Owns. Everything responders need to do the work.

In cyber. Clean administrative workstations, break-glass accounts, access for outside responders, forensic licenses and storage, spare hardware for rebuilds, the out-of-band channel, the war room, food, and places to rest.

Finance/Admin Section Chief

Owns. Time, cost, procurement, contracts and claims.

In cyber. Tracks every responder hour and outside invoice from the first hour, approves emergency purchases, activates retainers, and keeps the insurer's claim file. Read the cyber policy's notice deadline and panel-vendor terms before the incident, then track them during it.

Intelligence/Investigations

Where it sits. NIMS lets the intelligence and investigations function sit inside Planning, inside Operations, as its own General Staff section, or with the Command Staff.

In cyber. Forensic analysis, threat intelligence and evidence custody. Consider giving it its own section when the investigation is the main effort, when law enforcement works alongside, or when counsel directs the investigation for privilege. Otherwise it stays as the investigation group in Operations.

Branches, groups and task forces

ICS gives the pieces under a section fixed names, so a request for a task force means the same thing to everyone.

TermIn ICSCyber example
BranchAdded when a section outgrows its span of control. Functional or geographicA technical branch and an OT branch under Operations
DivisionA geographic or physical areaA data center, a site, a cloud tenant, a subsidiary
GroupA functional areaContainment group, identity group
Task forceMixed resources under one leader with shared communicationsIdentity task force: directory engineer, IAM administrator, detection analyst
Strike teamResources of the same kind and type under one leaderFive endpoint analysts working the rebuild queue
Single resourceOne person or item with an assignmentThe malware reverse engineer

Growing the organization

One incident, three sizes. Each chart shows the Operations Section only. Split any unit before it passes seven people, and add a layer before a supervisor has more than seven reporting.

About 8 responders, Type 4

Operations LeadContainment group3 peopleInvestigation group3 people
The Operations Lead supervises two groups directly. Command is the Incident Commander and a Communications Lead, who becomes the Public Information Officer as the incident grows.

About 25 responders, Type 3

Operations Section ChiefContainment group5 peopleIdentity task force4 peopleInvestigation group5 peopleRebuild group5 people
Three groups and a task force report to the Operations Section Chief, inside the span of control.

About 60 responders, Type 2

Operations Section ChiefTechnical branchChicago DCdivision, 6Dallas DCdivision, 6Cloud tenantdivision, 6Identitytask force, 5Investigationoutside firm, 6Recovery branchRebuildstrike team, 6OT branchPlantdivision, 6
Three branches keep the Operations Section Chief inside the span of control. Divisions split the technical work by place, recovery gets its own branch, and the plant branch has engineering in it.

The org chart builder draws the organization for an incident type, a sector and a size, with a name in each seat.

Who usually fills each seat

PositionDraw from
Incident CommanderSecurity operations leadership or a senior incident handler trained in ICS
OperationsThe incident response lead
PlanningA senior analyst or program manager who writes well under pressure
LogisticsIT operations or service desk leadership
Finance/AdminA finance partner with procurement authority
Public InformationCorporate communications, paired with a security writer
LiaisonVendor management or third-party risk
SafetyHealth and safety or HR, with OT engineering where plants are involved
Legal advisorIn-house counsel, with outside counsel as needed

Train two people for every seat you expect to fill, so each seat can be relieved.

Each seat has a job aid in Position checklists.

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.