ICS
1Prepare

Tabletop: ransomware

A 90-minute exercise that walks a ransomware incident from one alert to a Type 2 response with an outside firm, an insurer and a leak site. It tests taking command, sizing, the planning cycle, communications, outside parties and handover. The organization and every detail below are fictional.

Position checklistsFormsFlood tabletop

Set up the room

Seat one person in each position: Incident Commander, Operations, Planning, Logistics, Public Information, Liaison, Legal advisor, Finance/Admin and Safety, plus one executive to speak for the executive decision group. Give each player the Incident running now page, the quick card and the job aid for their seat.

The technical responders also work from the PIVTR-D first hour. A facilitator reads the injects, and a separate note-taker records the time of every decision.

The injects compress 55 hours of incident into 75 minutes, one about every eight minutes, followed by a 15-minute hot wash. Read each inject at its time, then let the players work.

Move on when they have produced what the inject calls for, or when the next inject is due. Keep the "Look for" column away from the players.

The scenario

Northgate Supply is a regional distributor with 1,200 staff, two data centers and one plant whose packing lines run on programmable controllers. Corporate email, chat and single sign-on share one identity provider. The security team has an incident response retainer and a cyber insurance policy, and nobody has read either since they were signed.

Injects

ClockInjectLook forSeats tested
0:00Friday 02:10. EDR flags mass file renames on two file servers. The on-call analyst sees the alert.The analyst takes command out loud and opens an activity log. Verification completes, and the two servers are isolated within the analyst's standing authority. The ICS 201 is started.Incident Commander
0:0802:40. Ransom notes appear on 30 more servers across both data centers. A domain administrator account is signing in from an unmanaged host.The incident is re-sized to Type 3. Command transfers to the on-call Incident Commander by briefing from the ICS 201. An Operations Section Chief and a Planning Section Chief are named. Up to three objectives are written, each with a measure and a time. The response moves to the out-of-band channel because identity is compromised.Incident Commander, Operations, Logistics
0:1604:00. The plant manager reports that the operator screens on the packing lines show the ransom note. The lines are still running.A Safety Officer is named. Nobody touches plant systems without engineering sign-off. Stopping the lines is a business decision, so it goes to the executive decision group with options and impact.Safety Officer, Incident Commander, executive group
0:2406:30. Executives are waking up. Shipping has stopped, and three different estimates of the damage are circulating.A Public Information Officer is named. Planning drafts the first ICS 209, and every update comes from it. The update cadence is set. The crisis team stands up to run manual workarounds for shipping.Public Information Officer, Planning, crisis team
0:3208:00. The insurer's hotline says the policy requires notice within 72 hours and names its panel firms. Your retainer firm is not on the panel.Liaison opens a line to the insurer. Finance/Admin reads the notice and panel terms. Counsel decides whether to direct the investigation for privilege. The IC decides which response firm to engage, with counsel and the insurer. An outside firm and an insurer make this a Type 2 incident.Liaison, Finance/Admin, Legal advisor
0:4010:30. A leak site posts sample files that include employee HR records. The attacker emails the chief executive directly.The attacker's email goes to the IC and counsel, unanswered. Counsel lists notification obligations and their clocks. Any engagement with the attacker goes to the executive decision group, with counsel advising on legal and sanctions exposure. The Public Information Officer prepares an interim statement and a staff notice.Legal advisor, Public Information Officer, executive group
0:4813:00. The first night shift starts at 19:00 and needs a plan.Planning runs the cycle: objectives meeting, tactics meeting, planning meeting. The IC approves an IAP with the ICS 202, 203 and 204s, the ICS 205 from Logistics, and the safety message.Planning, Operations, Incident Commander
0:5618:30. The Incident Commander and the Operations Section Chief have been on the incident since 02:40, almost 16 hours.The Safety Officer should have flagged both at the 13-hour duty limit, about 15:40. Command transfers by briefing, the change is announced and logged, and Operations hands over with the shift handover checklist.Safety Officer, Incident Commander, Operations
1:04Sunday 09:00. A scoping pass finds a second persistence mechanism on systems that were already restored.Operations starts another pass of the response loop. Planning updates the objectives and the timeline. The next executive update carries a revised recovery estimate.Operations, Planning, Public Information Officer

Hot wash

Start the hot wash at 1:15. Ask each question, record the answers, and let the note-taker's decision times settle disagreements.

#Item
1How long did it take from the first alert to someone taking command out loud?
2When was the incident re-sized, and who made that call?
3Were objectives written before tactics, each with a measure and a time?
4Did every executive update carry the same facts?
5Was attacker contact routed to the Incident Commander and counsel without a reply?
6Did anyone act on plant systems without engineering sign-off?
7Was each transfer of command briefed, announced and logged?
8Who worked past the shift limit, and who noticed?
9Which decisions waited on someone who could not be reached?

Write the findings into the after-action report and improvement plan within a week, with an owner and a date on every action, the same as for a real incident. Run the exercise again after the actions close, rotating players through different seats.

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.