A tabletop exercise is a facilitated discussion where your team talks through how they'd respond to a simulated security or business continuity scenario. It's not a live drill. No systems are touched. It's people in a room — or on a call — working through what they'd do.
Done well, it's one of the highest-value security activities an organization can run. Done poorly, it's a meeting where people read from the incident response plan and leave feeling good about a document that won't help them in a real incident.
The difference is in how the exercise is structured.
What Tabletops Surface That Drills Don't
Technical testing — penetration tests, red team exercises, backup restoration drills — validates whether your controls work. Tabletops validate whether your people and processes work. They're testing different things.
The gaps that tabletops routinely surface:
Decision authority is unclear. When the scenario escalates and someone needs to decide whether to take systems offline, pay a ransom, or notify customers, nobody's sure who has that authority. Everyone looks at everyone else. This is fixable before an incident; during one, it costs hours.
Communications break down. Your incident response plan says to notify legal counsel early. In the tabletop, it takes 45 minutes to agree on what to tell them, because nobody has thought through what legal needs to know versus what they should not be told during an active investigation.
Dependencies aren't documented. The scenario involves your primary cloud provider being unavailable. Someone in the room realizes nobody knows who owns that relationship or what the support escalation path is.
The plan assumes things that aren't true. The IRP says to restore from backup. In the tabletop, someone points out that the backup is on a network share that would have been encrypted in a ransomware scenario. Nobody had worked through that scenario before.
Third parties aren't in the loop. Your cyber insurance carrier wants to be called within 24 hours of a suspected incident. Nobody in the room knew that. The carrier's panel of approved forensics firms wasn't on anyone's contact list.
None of these findings require a live incident to discover. A tabletop surfaces them in a context where they're fixable.
What Makes Tabletops Fail
Testing the plan instead of testing decision-making. When participants respond to scenario questions by reading from the IRP — "well, according to our plan, we'd notify IT within one hour" — the exercise is validating document familiarity, not response capability. The question isn't what the plan says. The question is what the people in this room would actually do.
Only technical people in the room. The most consequential decisions during a serious incident aren't technical. They're about communications, legal obligations, customer notification, regulatory reporting, and whether to pay a ransom. These decisions involve legal, communications, leadership, and finance. An IR tabletop with only the technical team misses the half of the incident where things go wrong.
One static scenario with no progression. Real incidents don't stay the same. They escalate. New information emerges. New pressures arrive. A scenario that presents one problem and waits for participants to solve it doesn't simulate the reality of an incident where the situation changes every few hours.
No time pressure. "What would you do?" in a calm discussion produces different answers than "you have 20 minutes to decide and a client is on the phone." Exercises without any time constraint tend toward thoughtful, well-reasoned responses that bear no resemblance to actual incident conditions.
No action items. The most common failure mode: the exercise ends, the findings are interesting, and two months later nothing has changed. A tabletop that doesn't produce a documented list of specific actions — with owners and deadlines — is entertainment, not improvement.
How to Run a Useful Tabletop
Step 1: Pick a Realistic Scenario
Choose a scenario that could actually happen to your organization, not a generic example. The more specific the scenario, the more specific and useful the discussion.
Good scenarios for SMBs and professional services firms:
Ransomware over a long weekend: Employees arrive Monday morning to find file servers, shared drives, and the accounting system encrypted. A ransom note is on the screen. You don't know yet whether backups are also encrypted. Two enterprise clients are waiting on deliverables due this week.
Credential compromise: A staff member's email and Microsoft 365 account was compromised for an unknown period. The account had access to client files, financial records, and HR data. You're not sure what was accessed or exfiltrated. You know this because a client just emailed asking about a phishing email they received that appeared to come from your domain.
Third-party breach: Your payroll processor notifies you that they experienced a breach and your employee data — names, Social Security numbers, bank account numbers — may have been exposed. What are your obligations? What do you tell employees?
Insider threat: An employee who gave notice two weeks ago is suspected of exfiltrating client data before leaving. Your IT team found anomalous download activity in the employee's last week. The employee is now working for a competitor.
Step 2: Build Injects
An inject is a new piece of information introduced at a designated point during the exercise that escalates the scenario or adds a new complication. Injects force participants to adapt and make new decisions — they simulate the way real incidents evolve.
Example injects for a ransomware scenario:
- Inject 1 (30 minutes in): Your backup provider confirms that the network-connected backups were also encrypted. Offline backups exist but are two weeks old.
- Inject 2 (45 minutes in): A reporter from a local business publication has called asking about reports of a security incident at your company.
- Inject 3 (60 minutes in): The forensics firm your cyber insurance carrier provides has a 72-hour queue. You can pay out-of-pocket for faster engagement.
- Inject 4 (75 minutes in): You discover that the encrypted systems included a folder containing personally identifiable information for Maine residents. You now have a potential notification obligation under 10 M.R.S. § 1347.
Each inject forces a new decision with new information — more like a real incident, less like a controlled test.
Step 3: Get the Right People in the Room
Minimum participants for a meaningful tabletop:
- The person who would serve as Incident Commander
- The technical lead (IT director, MSP contact, security staff)
- Legal counsel or whoever would engage them
- The person responsible for external communications
- A senior business leader who can make authorization decisions
For regulated organizations: someone who understands notification obligations (HIPAA, state breach notification law, GLBA, etc.).
You don't need everyone. You need the people whose decisions and handoffs are most likely to break down.
Step 4: Run the Exercise, Then Stop
A useful tabletop runs 90 minutes to 3 hours depending on complexity. Have a facilitator who isn't one of the participants — someone whose job is to keep the scenario moving, introduce injects, ask follow-up questions, and note where the discussion gets stuck.
The facilitator's most important question is "what happens next?" — not to the participant who just answered, but to the next person in the handoff chain. "You've decided to engage forensics — what does that call look like, and who makes it?"
Step 5: Hot Wash and Action Items
Immediately after the exercise (not a week later), hold a 30-minute debrief covering:
- What went well
- Where the discussion broke down or produced uncertainty
- What assumptions in the plan turned out to be wrong
- What information participants didn't have that they needed
Then document action items: what changes as a result of this exercise? Who owns each change? By when?
If the exercise didn't produce at least three actionable findings, either the scenario wasn't realistic enough or the participants weren't engaged enough to surface real gaps.
How Often to Run Them
Annual tabletops are the minimum for most organizations. Regulated industries (healthcare, finance) benefit from twice a year. Tabletops should also be triggered by significant organizational changes: new executive leadership, major IT changes, a near-miss security event, or after a real incident as part of the lessons-learned process.
The goal isn't a perfect response. It's a team that's thought through the decisions they'll need to make before they have to make them under pressure.
SOURCES
- NIST SP 800-84, Guide to Test, Training, and Exercise Programs for IT Plans and Capabilities: csrc.nist.gov/publications/detail/sp/800-84/final
- CISA, Tabletop Exercise Packages (free downloadable scenarios): cisa.gov/resources-tools/services/cisa-tabletop-exercise-packages
- SANS Institute, "How to Plan a Successful Security Tabletop Exercise": sans.org/reading-room
Need to run a tabletop for your organization and not sure where to start? Schedule a consultation to talk through a scenario that fits your environment.
