ICS
2Respond and manage

Position checklists

Each ICS seat has a job aid, grouped by when you use it: on taking the seat, every operational period, and before handing over. Print the page for the war room, or copy any list into the incident channel as a Markdown checklist. The seats are described in The organization, and the forms in Forms.

Incident Commander

Reports to
The executive who delegated authority for the incident, the Agency Administrator in NIMS terms
Fill the seat
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.
Forms
Prepares the ICS 201. Approves the ICS 202, the Incident Action Plan and the ICS 209.

On taking the seat

#Item
1Take command out loud: your name, the time, the incident name and where the command bridge is. Open your activity log (ICS 214).
2If someone was in command before you, take a briefing from them, using the ICS 201 if one exists.
3Open a command bridge and an out-of-band channel, and record both in the ICS 205. Treat email, chat and identity as visible to the attacker until scoping shows otherwise.
4Size up: what happened, what is affected, what is still happening and what is unknown.
5Set up to three objectives, each with an outcome, a measure and a time. Examples are in Writing objectives.
6Name an Operations Lead, or an Operations Section Chief from Type 3, and hand over the technical work. Stay off the keyboard.
7Decide the incident type, 5 to 1, with the type chooser, and fill the positions it calls for.
8Confirm your authority limits, and who approves anything above them.
9Tell counsel if personal data, regulators, law enforcement, extortion or insurance may be involved. The clocks are in notification deadlines.
10Set the times of the first briefing and the first executive update, using the update schedule for the severity.
11Write the incident briefing (ICS 201) before the first briefing.
12Check hours: who has been awake since when, and who relieves them. Record hazards and rest rules in the ICS 208.

Every operational period

#Item
1Run the objectives meeting and approve the ICS 202.
2Approve the Incident Action Plan before the operations briefing.
3Approve the ICS 209 before it goes to executives.
4Approve resource orders beyond the sections' authority.
5Check span of control, and add or fold positions as the workload changes.
6Review hours worked with the Safety Officer and roster relief.

Before handing over

#Item
1Brief the incoming IC by voice from the ICS 201 or the current IAP.
2Walk every open decision and every commitment made to outside parties.
3Agree the effective time, announce the change, and log it with both names.

Deputy Incident Commander

Reports to
The Incident Commander
Fill the seat
From Type 2, or sooner when the Incident Commander needs relief across operational periods or has command work to hand off. The deputy must be able to take over as Incident Commander at any time. A second Incident Commander who commands alternate periods, as in the worked example, covers the relief use.
Forms
Keeps an ICS 214. Reads each ICS 201, 202 and 209 when it is issued, and uses the Incident Commander's forms while in command.

Owns. The command tasks the Incident Commander delegates, and command itself while relieving the Incident Commander. ICS gives a deputy three uses.

One is specific tasks the Incident Commander assigns. Another is relief in command, for example for the next operational period. The third is representing a party that has, or may later have, authority over part of the incident.

On taking the seat

#Item
1Take a briefing from the Incident Commander, using the ICS 201 or the current IAP. Open your activity log (ICS 214).
2Agree which tasks you own and which decisions stay with the Incident Commander, and record the split in both activity logs.
3Read the delegation of authority, so you know the limits that apply when you take command.
4If you are the relief in command, agree which operational periods you command and the time of each transfer.
5If you represent another party, agree with the Incident Commander which of its decisions you can make on the spot and which go back to it.
6Ask Planning to add you to the ICS 203, and announce your role on the command bridge.

Every operational period

#Item
1Run the tasks the Incident Commander delegated, such as coordinating unified command members, and report on each at the objectives meeting.
2Attend the objectives meeting and the planning meeting, so you can explain every decision in the IAP when you take command.
3Keep a list of open decisions, with who is waiting on each and by when.
4Before you relieve the Incident Commander, take the handover briefing and follow Transferring command. While in command, work from the Incident Commander job aid.
5Track your hours and the Incident Commander's, and tell the Safety Officer before either of you reaches the shift limit.

Before handing over

#Item
1Hand each delegated task back to the Incident Commander or to a named person, with its status.
2If you are in command, transfer it on the transfer of command record, announce it, and log it with both names.
3Brief the incoming deputy by voice on the delegated tasks and the open decisions.

Built from FEMA's ICS 300 review document (March 2018), which gives a deputy these three uses and requires a deputy to be able to take over the primary role.

Public Information Officer

Reports to
The Incident Commander
Fill the seat
As soon as anyone outside the response team has to be told.
Forms
Drafts from the ICS 209 and logs on an ICS 214.

On taking the seat

#Item
1Get the current status summary and the list of who already knows about the incident.
2List every audience: executives, staff, customers, partners, media, and regulators through counsel.
3Agree with the IC who approves each kind of message, and with counsel which ones need legal review.
4Take the update cadence from the update schedule for the severity, and put the times in the IAP.
5Prepare an interim statement before anyone asks for one, on PIVTR-D T18.
6Tell staff where to send questions from outside the organization.

Every operational period

#Item
1Draft every update from the current ICS 209 so every audience gets the same facts.
2Make each update say what is affected, how bad it is, what people should do, and when it will be fixed or the next update is due.
3Send attacker contact, extortion notes and leak-site posts to the IC and counsel, unanswered.
4Agree wording and timing with the other parties' communicators through the joint information system.
5Log every message sent, with the time, the audience and who approved it.

Before handing over

#Item
1Hand over the message log and every promised update time.
2List open media and customer questions, with who is waiting on each.

Safety Officer

Reports to
The Incident Commander
Fill the seat
When the incident runs past one operational period, or when containment could touch a physical process.
Forms
Writes the safety message (ICS 208) and the IAP safety analysis (ICS 215A).

On taking the seat

#Item
1Confirm your authority to stop any action that puts people at risk, and tell Operations you have it.
2Get the roster with the hours worked by everyone on the response.
3List every containment action that could affect a physical process or a safety system, and require engineering sign-off before it runs.
4Ask HR and physical security to support any staff named in extortion or doxxing.

Every operational period

#Item
1Enforce the maximum shift length and the relief roster.
2Review the tactics at the tactics meeting for risk to people and to physical processes.
3Write the safety and wellbeing message for the IAP.
4Record every action you stopped, and why.

Before handing over

#Item
1Name everyone at or near the hours limit.
2Hand over every open safety concern and every pending engineering sign-off.

Liaison Officer

Reports to
The Incident Commander
Fill the seat
When outside parties are engaged.
Forms
Logs on an ICS 214 and records requests on ICS 213 general messages.

On taking the seat

#Item
1List every outside party and one named contact at each: the response firm, the insurer and breach coach, law enforcement, managed providers, suppliers, the ISAC, and regulators through counsel.
2Tell the IC which of them have authority over part of the response and belong in unified command.
3Give each party a single contact point on the incident, which is you.
4Agree with counsel what may be shared with each party.

Every operational period

#Item
1Brief outside parties at the times the IAP sets.
2Bring their requests and constraints to the Command and General Staff meeting.
3Log every commitment made to them, with a date and an owner.
4Carry evidence and preservation requests to suppliers on PIVTR-D T19, and log each with its due date.

Before handing over

#Item
1Hand over the commitment log and every pending request.
Reports to
The Incident Commander
Fill the seat
When personal data, regulators, law enforcement, extortion or insurance may be involved.
Forms
Records privilege routing in the IAP.

On taking the seat

#Item
1Decide whether counsel will direct the investigation to preserve privilege, and have it recorded in the IAP.
2List every notification obligation, with its deadline and what starts its clock, starting from Notification deadlines and the PIVTR-D sector pages. Work each regulator's notice on T17.
3Confirm engagement terms for outside responders.
4Issue preservation instructions for evidence and records.

Every operational period

#Item
1Review every message leaving the incident that could create legal exposure.
2Track notification deadlines and advise the IC before each one falls due.
3Advise on law enforcement engagement and on any contact from the attacker.

Before handing over

#Item
1Hand over the deadline list, the privilege routing and any open advice.

Operations Section Chief

Reports to
The Incident Commander
Fill the seat
Every incident above Type 5. At Type 4 the seat is the Operations Lead, who becomes the Operations Section Chief at Type 3.
Forms
Builds the ICS 215 at the tactics meeting, and guides the ICS 204 assignment lists, which the resources unit in Planning prepares.

On taking the seat

#Item
1Get the objectives and the current scope from the IC.
2Organize the work into groups, each with a named supervisor and three to seven people.
3Agree with the IC which containment actions need approval before they run.
4Set the cadence for status reports to Planning.
5Request people, tools and access through Logistics, on the resource request.

Every operational period

#Item
1Bring tactics and resource needs to the tactics meeting.
2Deliver assignments at the operations briefing, one ICS 204 per group.
3Run the PIVTR-D response loop and report each pass to Planning.
4Tell the IC at once about any change that affects the objectives.

Before handing over

#Item
1Hand over the status of every group, the actions in progress and any evidence in hand.

Division/Group Supervisor

Reports to
The Operations Section Chief, or a Branch Director once Operations has branches. At Type 4, the Operations Lead.
Fill the seat
Every group or division Operations sets up, usually from Type 4. Each supervisor leads three to seven people.
Forms
Receives one ICS 204 at the operations briefing and works from it. Keeps an ICS 214.

Owns. One part of the IAP, as written on one ICS 204: the work, the people doing it, their safety, and reports on progress. A group splits the work by function, such as the Containment, Rebuild and Investigation groups in the worked example.

A division splits it by place, such as a data center or a cloud tenant. Division and group supervisors have the same level of authority.

On taking the seat

#Item
1Take a briefing from the Operations Section Chief or Branch Director. Read your ICS 204 and the objectives on the ICS 202 that it serves.
2Attend the operations briefing, and raise anything on the ICS 204 your group cannot deliver in the period.
3Confirm every member has checked in with the Resources unit and has the access and tools the work needs.
4Brief the members on each task, the objective it serves, the special instructions and the channels.
5Confirm which actions need approval before they run, and who gives it.
6Agree hand-offs with the supervisors of the groups your work depends on, for example when the Investigation group dates the backups the Rebuild group may restore.

Every operational period

#Item
1Assign each task on the ICS 204 to named members, and move people between tasks as the work changes.
2Keep members to the special instructions: systems not to touch, change windows and evidence handling.
3Report progress and the status of your people at the times on the ICS 204, through the channel it names.
4Coordinate with the supervisors of adjacent groups and divisions before anyone touches a system you share.
5Request more people or tools through the Operations Section Chief or Branch Director.
6Report at once anything that changes the plan: new hosts or accounts in scope, a containment action that failed, or a responder too tired or unwell to continue.
7Solve the group's own access, license and workstation problems, and pass the rest to Logistics.
8Send anyone at the shift limit to rest, and tell the Safety Officer.

Before handing over

#Item
1Debrief the Operations Section Chief or Branch Director before you leave the shift.
2Brief the incoming supervisor face to face or by voice: each task's status, actions in progress, evidence in hand, and hazards.
3Hand your ICS 214 to Documentation.

Built from FEMA's Division/Group Supervisor position checklist (February 10, 2012) and position task book (July 2019), the NWCG incident position description, and NIMS (2008) Appendix B. Appendix B gives division and group supervisors the same level of authority.

Planning Section Chief

Reports to
The Incident Commander
Fill the seat
When the incident runs past one shift.
Forms
Prepares the ICS 202, 209 and the IAP. Its units prepare the ICS 203, 204, 211 and 221, and keep the open action tracker.

On taking the seat

#Item
1Start the incident record and the attack timeline, or take them over from whoever started them.
2Stand up the situation, resources and documentation units as the workload needs.
3Publish the meeting schedule for the operational period.
4Check in everyone working the incident on the ICS 211, with an assignment and a relief time.

Every operational period

#Item
1Prepare the ICS 202 after the Command and General Staff meeting, for the IC to approve.
2Assemble the IAP: the ICS 202, 203 and 204s, the communications plan and the safety message.
3Prepare the ICS 209 on the cadence the IAP sets.
4Keep the common operating picture current, timestamped and in one place.
5Collect the activity logs from every position.
6Start the demobilization plan as soon as the end is in sight.

Before handing over

#Item
1Hand over the situation, the planning products in progress and the meeting schedule.

Situation Unit Leader

Reports to
The Planning Section Chief
Fill the seat
When the Planning Section Chief stands up the unit, as the workload needs. Until then the Planning Section Chief does this work.
Forms
Drafts the ICS 209 for the Planning Section Chief. Keeps the attack timeline, the scope list and an ICS 214.

Owns. The common operating picture: the status summary, the attack timeline and the scope list, in one place and timestamped. Also the analysis and predictions that command and Operations ask for, and any Technical Specialists assigned to the unit.

On taking the seat

#Item
1Take a briefing from the Planning Section Chief. Get the ICS 201, the current IAP and the incident record, PIVTR-D T1.
2Take over the attack timeline and the scope list, and publish them where everyone on the response can read them, outside the affected identity provider.
3List your sources and when each reports: every group's status reports, findings from Intelligence/Investigations, the activity logs, and outside parties through Liaison.
4Agree the ICS 209 times with the Planning Section Chief, from the IAP and the executive update schedule.
5Brief any Technical Specialists assigned to the unit on the questions they are answering, and when each answer is due.

Every operational period

#Item
1Update the timeline and the scope list as reports arrive. Record each entry with its time, time zone and source.
2Count a host or account as confirmed only with evidence, and list the rest as suspected.
3Interview supervisors coming off shift about what they found and how well their tactics worked.
4Draft the ICS 209 from the timeline and the scope list before each executive update, and give it to the Planning Section Chief.
5Give the situation briefing at the planning meeting and the operations briefing.
6Give command and Operations a prediction at set times or on request, for example which hosts are likely to be hit next, or when restores will finish.

Before handing over

#Item
1Brief your relief on the current situation and anything unusual.
2Hand over the timeline, the scope list, the next ICS 209 time, and every open question with who is answering it.
3Hand your ICS 214 to Documentation.

Built from FEMA's Situation Unit Leader position checklist (February 10, 2012), the NWCG incident position description, and the FEMA ICS forms booklet. The booklet names the Situation Unit Leader as the usual preparer of the ICS 209.

Resources Unit Leader

Reports to
The Planning Section Chief
Fill the seat
When the Planning Section Chief stands up the unit, as the workload needs, and at the latest before an outside response firm arrives. Until then the Planning Section Chief does this work.
Forms
Runs check-in on the ICS 211. Prepares the ICS 203 and, with the Operations Section Chief, the ICS 204s. Keeps an ICS 214.

Owns. Check-in, the master roster, and the status of every person and resource on the incident: assigned, available, resting or released.

On taking the seat

#Item
1Take a briefing from the Planning Section Chief. Get the resource list on the ICS 201 and the current ICS 203.
2Open check-in on the ICS 211 at every place responders join: the command bridge, the war room and the out-of-band channel.
3Check in everyone already working, with assignment, supervisor, relief time, when they last slept, and any access granted, with its end date.
4Start the master roster and a status board showing who is assigned, available, resting or released.
5Get status from the people who have it: the Operations Section Chief, each supervisor, the first Incident Commander, and Logistics for people and tools on order.

Every operational period

#Item
1Record every arrival, reassignment, rest period and release as it happens.
2Bring the roster to the tactics meeting: who is available for the next period, who needs relief, and which skills are missing.
3Prepare the ICS 203 and, with the Operations Section Chief, one ICS 204 per group or division for the IAP.
4Tell the Safety Officer about anyone near the shift limit and any seat without a named relief.
5Give Logistics and Finance/Admin every arrival and departure, so access and recorded hours match the roster.
6Tell the Planning Section Chief whose work is closing, for the demobilization plan.

Before handing over

#Item
1Brief your relief on the roster, pending arrivals and releases, and anything unusual.
2Hand over the master roster, the status board and the check-in lists.
3Hand your ICS 214 to Documentation.

Built from FEMA's Resources Unit Leader position checklist (February 10, 2012), the NWCG incident position description, and the FEMA ICS forms booklet. The booklet names the Resources Unit Leader as the usual preparer of the ICS 203 and, with the Operations Section Chief, the ICS 204.

Documentation Unit Leader

Reports to
The Planning Section Chief
Fill the seat
When the Planning Section Chief stands up the unit, as the workload needs, and at the start of any incident that may lead to litigation, a regulator's inquiry or an insurance claim. Until then the Planning Section Chief does this work.
Forms
Files every ICS form and PIVTR-D record, and collects every position's ICS 214.

Owns. The incident files: every plan, form, log, decision record and report, checked and filed, and the index of the evidence register.

On taking the seat

#Item
1Take a briefing from the Planning Section Chief. Ask the Legal advisor whether counsel directs the investigation, and how privileged material is labeled and routed.
2Set up the incident files where the attacker cannot read them, with access limited to the response and counsel.
3Lay out the files: one folder per operational period for the IAP and its forms, and one each for the incident record, decisions, general messages, activity logs and the evidence register index.
4Collect what exists: the ICS 201, any transfer of command records, and the activity logs and notes kept so far.
5Apply the Legal advisor's preservation instructions to the incident files.

Every operational period

#Item
1Send the approved IAP to everyone on its distribution list, and file the signed copy.
2Accept and file every form, log and report on the day it arrives.
3Check each record for names, times with time zones, and approvals, and return errors to the author.
4Keep the decision register: one numbered entry per decision, and each reversed entry marked with the number that replaced it.
5Collect the ICS 214 from every position at the end of the period.
6Keep the evidence register index in step with the register Intelligence/Investigations keeps.
7Answer requests for records along counsel's routing, and log what went to whom.

Before handing over

#Item
1Brief your relief on the file layout, missing records and open requests.
2At the end of the incident, index the files and give the complete set to the Planning Section Chief.
3File your own ICS 214.

Built from FEMA's Documentation Unit Leader position checklist (February 10, 2012) and the NWCG incident position description.

Logistics Section Chief

Reports to
The Incident Commander
Fill the seat
When responders need access, tools or facilities the response team cannot arrange for itself.
Forms
Prepares the ICS 205 through the communications unit.

On taking the seat

#Item
1Stand up the out-of-band channel and the command bridge, with accounts outside the affected identity provider.
2Provide clean administrative workstations and break-glass access.
3Arrange access for outside responders, with an end date on every account.
4Set up the war room, physical or virtual.

Every operational period

#Item
1Fill the resource requests from the tactics meeting.
2Have the communications unit prepare the ICS 205 and give it to Planning for the IAP.
3Track forensic licenses, evidence storage and rebuild hardware.
4Arrange food, transport and places to rest.

Before handing over

#Item
1Hand over open orders, every temporary account and all hardware on loan.

Finance/Admin Section Chief

Reports to
The Incident Commander
Fill the seat
When outside costs, contracts or insurance claims begin.
Forms
Keeps the time and cost records.

On taking the seat

#Item
1Open a cost code for the incident and record responder hours from the first hour.
2Read the cyber insurance policy's notice deadline and panel-vendor terms, and tell the IC and Liaison.
3Confirm who can approve emergency purchases, and up to what amount.
4Activate the retainers the IC has approved, with the retainer script.

Every operational period

#Item
1Record hours for everyone on the roster.
2Approve emergency purchases within your authority, and route the rest to the IC.
3Update the cost summary and the insurer's claim file.

Before handing over

#Item
1Hand over costs to date, open purchases and invoices, and the claim status.

Intelligence/Investigations

Reports to
The Incident Commander
Fill the seat
When the investigation is the main effort, law enforcement works alongside, or counsel directs the investigation for privilege.
Forms
Keeps the evidence register. Findings follow counsel's routing when privilege applies.

On taking the seat

#Item
1Agree with counsel how findings are routed and recorded.
2Take over the evidence register, and confirm chain of custody for everything collected so far. Collection steps are in PIVTR-D evidence collection.
3Set priorities for forensic analysis with the IC.

Every operational period

#Item
1Feed findings into Planning's situation picture on the cadence the IAP sets.
2Share threat intelligence with Operations for scoping.
3Keep the evidence register current.

Before handing over

#Item
1Hand over open analysis, and log every custody transfer.

Technical Specialist

Reports to
Whoever needs the skill, most often the Planning Section Chief. In the Situation unit, the Situation Unit Leader.
Fill the seat
When the response needs a skill nobody on the roster has. Order outside specialists through Logistics. The Incident Commander approves orders beyond the sections' authority.
Forms
Checks in on the ICS 211 and keeps an ICS 214. Puts advice that a decision depends on in writing, on an ICS 213.

Owns. Advice and work in one specialty. ICS places Technical Specialists in the Planning Section or wherever their skills are needed, with no fixed position in the structure.

Cyber specialists

SpecialistReports toRules
Forensic analyst from a response firmIntelligence/Investigations, or the Investigation group supervisor while the investigation sits in OperationsWorks to the analysis priorities Intelligence/Investigations sets with the Incident Commander. Hashes every image and enters it in the evidence register. Findings follow counsel's routing when privilege applies.
Ransomware negotiatorIntelligence/Investigations, or Planning while the investigation sits in Operations. See Command by incident typeContacts the attacker only after the executive decision group approves engagement, with counsel advising on legal and sanctions exposure. Sends each message only after the Incident Commander approves it and the Legal advisor reviews it. Logs every message sent and received. Passes the attacker's claims to Intelligence/Investigations to verify.
Cloud provider engineerThe group working the affected tenant, or Planning when the incident is on the provider's sideWorks through the open support case. Gives the case number, the provider's findings and its next update time at each status report. Requests to the provider's account team go through Liaison.
OT engineerThe OT group or OT branch in Operations, advising the Safety OfficerReviews every containment action on plant systems before it runs, and gives or withholds engineering sign-off. Tells the Safety Officer about any action that could stop a process or disable a safety system.

On taking the seat

#Item
1Check in with the Resources unit on the ICS 211, and get access with an end date through Logistics.
2Take a briefing from the person you report to: the question to answer, the deadline, and who acts on your answer.
3Agree with the Legal advisor what you may record and share, and where your findings go.
4Confirm what you may do in the environment on your own, and what needs approval from the Operations Section Chief first.
5Use only the channels in the communications plan (ICS 205).

Every operational period

#Item
1Report findings or advice at the times your supervisor sets, marking what is confirmed, what is suspected, and how sure you are.
2Attend the tactics or planning meeting when your specialty shapes the plan.
3Log every action you take in the environment, with the time, on your ICS 214.
4Enter every item of evidence you collect in the evidence register, with custody recorded.

Before handing over

#Item
1Hand findings, open questions and work in progress to a named person, in writing.
2Hand evidence and notes to Intelligence/Investigations, with custody recorded.
3Check out on the ICS 221: access revoked, hardware returned, hours to Finance/Admin.
4Hand your ICS 214 to Documentation.

Built from FEMA's ICS 300 review document (March 2018), which places Technical Specialists in the Planning Section or wherever their services are needed. The cyber specialists and their rules are this guide's practice.

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.