,

Incident Response Tabletop Exercise: Test the Decisions, Not Just the Runbook

Line art: a runbook track that turns into decision points, each branching to the people who must decide

Most incident response tabletop exercises test whether the security team knows its runbook. It usually does. The real incident fails somewhere else: on the decisions the runbook does not make.

Who declares a crisis. Who authorizes shutting down the systems that run revenue. Who calls outside counsel, the insurer, and the regulator, and when. Whether to pay.

Those decisions belong to legal, communications, operations, finance, and your executives. If none of them are in the exercise, you have tested the part of the response most likely to work.

The short answer: an incident response tabletop exercise should test the decisions your runbook doesn’t make, with legal, communications, operations, finance, and your executives in the room. Build it around six: when it becomes a crisis, whether to shut systems down, who to call, who to notify and by when, whether to pay, and what to restore first.

The Exercise Most Teams Run, and the One They Need

Old View New View
The exercise tests the incident response plan The exercise tests the decisions around the plan
The security team plays; everyone else gets a debrief Everyone who would own the real incident plays
The scenario ends at containment The scenario runs into recovery and disclosure
Success is “we followed the runbook” Success is a list of decisions made, missed, and too slow
One exercise a year checks the box A sequence of exercises closes gaps and re-tests them

An incident response tabletop exercise is a facilitated, discussion-based walkthrough of a realistic cyber incident, usually two to four hours, in which participants talk through what they would do as the scenario unfolds. NIST’s incident response guidance (SP 800-61 Revision 3, aligned with the Cybersecurity Framework 2.0) treats exercises as part of preparation, and most cyber insurers, auditors, and large customers now ask when you last ran one.

The format is sound. The problem is what most organizations put in it.

Three Exercises, Not One

A cyber incident has three layers, and each needs its own test:

  • The technical tabletop. Your incident response and engineering teams against a realistic scenario. It tests detection, escalation triggers, containment, and technical decision-making. This is the exercise most organizations already run.
  • The handoff tabletop. The incident team and the crisis team together. It tests the moment a security incident becomes a business crisis: the severity call, the escalation, and the move from response to crisis management. This is where most real incidents break, and it is the exercise most organizations skip.
  • The executive exercise. The decisions only the top can make, with counsel in the room: pay or refuse, disclose or wait, shut down or keep running.

If you can run only one this year, run the handoff. Your security team already practices the first layer every week on real alerts. Nobody practices the seam.

Six Decisions to Build Your Incident Response Tabletop Exercise Around

Write the scenario backward. Start with the decisions you want to test, then write the injects that force them. Every one of these should land on a specific person with incomplete information and a clock running.

1. When does this become a crisis?

The security team sees a SEV1. Does that mean the crisis team convenes? If the answer depends on who is on call, your criteria are not written down. (Here is how to design crisis severity levels that trigger action.)

Inject that forces it: an alert that is ambiguous for the first hour, then is not.

2. Do we shut it down?

Isolating systems stops the spread. It can also stop shipping, billing, or patient care. The incident commander rarely has the authority to take down a revenue system alone, and the executive who does is rarely in the room.

Inject that forces it: encryption reaches a system the business cannot run without, at 2:00 AM.

3. Who do we call, and under what privilege?

Outside counsel, the forensics firm, the cyber insurer, and law enforcement all want an early call. Many cyber policies require you to notify the carrier quickly and use its approved vendors. If counsel does not engage the forensics firm, the findings may not be privileged.

Inject that forces it: the forensics firm you have used for years is not on the insurer’s panel.

4. Who must we notify, and by when?

Regulators, customers, partners, and employees all run on different clocks. A public company has four business days after it determines an incident is material to file with the Securities and Exchange Commission (SEC). Healthcare, financial services, and state breach laws add their own deadlines. The clock often starts at “determined” or “discovered,” which means someone has to decide when that moment was.

Inject that forces it: a reporter calls with details your team has not confirmed.

5. Do we pay?

Payment is a business decision with legal limits. Someone has to check sanctions exposure, weigh what the backups can actually restore, and decide what the company will say if the payment becomes public. Teams that have never discussed this in advance spend the first day of a real event arguing about it.

Inject that forces it: the ransom demand arrives with a 72-hour deadline and a sample of your stolen data.

6. What do we restore first, and from when?

Most exercises end at containment, exactly where the hardest decisions begin. Which services come back first, from which restore point, and who accepts the data loss? (We wrote about the decisions your ransomware recovery plan must make in advance.)

Inject that forces it: the most recent clean backup is nine days old.

A Sample Scenario Timeline

Here is the shape of a four-hour handoff tabletop built on a ransomware scenario. Times are scenario time, not clock time.

Scenario time Inject Decision it forces
Day 1, 9:00 AM Help desk resets an executive’s credentials after a convincing phone call None yet. Does anyone notice?
Day 1, 3:00 PM Unusual data transfers from a file server Is this an incident? Who is told?
Day 2, 2:00 AM Encryption spreads to a production system Shut it down? Who authorizes?
Day 2, 8:00 AM Ransom note and a leak-site post with sample data Declare a crisis? Call counsel and the insurer?
Day 2, 11:00 AM A reporter and your largest customer call within minutes What do we say, and who says it?
Day 3 Clean backups are nine days old; the attacker sets a deadline Pay or refuse? Restore what first?

Notice who is needed after the second row: almost everyone except the security team.

How to Run It

  • Build the scenario from real tradecraft. Use the techniques attackers are using against your sector right now, such as help desk social engineering and data theft before encryption. A generic “malware detected” scenario tests nothing.
  • Put the decision-makers in the room. If the general counsel sends a delegate, the delegate needs the authority to decide.
  • Withhold information. Real incidents arrive in fragments. Injects should, too.
  • Keep a decision log. Record every decision, who made it, and how long it took. The gaps in that log are your findings.
  • Run it into recovery. If the exercise ends when the threat is contained, schedule the second half.

Common Failure Modes

  • The exercise is a briefing. A presenter walks through slides about ransomware, and nobody has to decide anything.
  • The scenario is too easy. Every inject has a clear right answer, and the room agrees. Real incidents do not cooperate.
  • The wrong people attend. Security plays, the business watches, and the exercise confirms what the security team already knew.
  • No one owns the findings. The after-action report lists twenty gaps and assigns none of them. (Here is how to turn exercise findings into an improvement plan.)

Where to Start

  • Run it yourself. Our Ransomware Tabletop Scenario is a ready-to-run exercise package for $129.99. Add the six decisions above as injects.
  • Get a custom exercise built in a day. Exercise in a Day® builds your scenario, injects, and facilitator materials in one business day for $7,500, with optional facilitation by our team.
  • Test the handoff with senior facilitation. Our cyber crisis exercises put the incident team and the crisis team in the same fight, from a technical tabletop to a multi-day simulation. A cyber crisis tabletop starts at $25,000.

If you are hiring outside help, here is how to choose a tabletop exercise facilitator.

Your runbook tells the team what to do. Your next exercise should find out who decides.

Keep Going

A few ways to go deeper if this was useful.

Bryan Strawser Avatar

About the author

Let’s build your Resilience Roadmap

Our team has spent two decades helping the world’s leading organizations prepare for and navigate disruption. We’ll bring that experience to yours.