How to Run a Tabletop Exercise That Actually Works (Even If It’s Your First)

A tabletop exercise should do more than spark discussion. It should prove your organization can recover when ransomware, cloud outages, or data loss strike. Discover how to plan and run an effective tabletop exercise, test real-world disaster recovery capabilities, expose critical gaps, and turn findings into measurable improvements in cyber resilience.
Share post:

Most tabletop exercises fail simply because they never touch a real system. Everyone agrees the backups exist, someone says “we’d restore from there,” and the management typically moves on without question. This is a discussion that’s built on hypothesizing, it’s certainly not a disaster simulation.

I work with enterprises every day to prepare for cloud outages, ransomware and data loss. This guide is the practical playbook I give teams, especially teams running their first tabletop.

What is a tabletop exercise?

A tabletop exercise is a structured, facilitated simulation in which an organization’s technical and business leaders walk through a realistic incident, such as a ransomware attack or a cloud region outage, to test their response plan, roles and recovery capabilities. A good tabletop ends with evidence: a restore that actually ran, a measured recovery time and a list of gaps with owners assigned.

Why tabletop exercises are now about cyber resilience, not just cybersecurity

Tabletop exercises have traditionally been a cybersecurity exercise focused on detecting and containing the intrusion. That changed over the last year. AI has made attacks faster, cheaper and more sophisticated, and stolen sessions and tokens let attackers walk past even strong defenses.

The more realistic assumption today is that a breach will happen at some point. That shifts the focus from cybersecurity to cyber resilience, which asks different questions:

  • When an attack or outage hits, can the business keep running?
  • How fast can we recover to a known-clean state?
  • Have we actually proven it, or are we assuming it?

It also moves the conversation out of the IT team and into the boardroom. Resilience is ultimately about business continuity, not just technology. A tabletop exercise is where you test whether all of that holds up under pressure.

How do you make sure a tabletop exercise is done properly?

A tabletop is done properly when it produces evidence, not just agreement. Three rules make the difference.

1. Scope it around the business, not the infrastructure. Ask leadership for the five processes that would sink the company if they stopped for a week, such as payroll, order fulfillment or customer billing. Then map the systems and dependencies behind each one, because critical resources are rarely in one place. IT teams used to decide what was “critical,” but IT doesn’t run the business. The business has to define it.

2. Define measurable outcomes before you start. Write down your target recovery time objective (RTO) and recovery point objective (RPO), or how much data loss is acceptable, for each critical process.

3. Time everything. If someone says “we can be back in four hours,” the exercise should prove or disprove it with a stopwatch.

Who should be in the room for a tabletop exercise?

The facilitator should be someone who is not a participant. Their job is to run the scenario, inject complications and control the clock.

The active participants should include:

  • Incident response lead: coordinates the response and makes the calls
  • Infrastructure and cloud engineers: carry out the recovery
  • Backup and DR owner: knows what’s protected, where and how recent it is
  • Security: handles containment and identifies clean restore points
  • Legal and communications: cover disclosure, regulators, customers and evidence preservation
  • At least one business executive with decision-making authority

That last seat matters most. Executives usually show up reluctantly and leave as the exercise’s biggest supporters, because they finally see what happens behind the scenes. They also understand what’s needed in terms of budget and can help make it happen.

6 tabletop exercise scenarios that break assumptions

The best injects are the ones that break what everyone assumes will work. Use these at the moment the team feels most confident.

InjectThe question it forcesWhat it tests
Your primary cloud account is compromised and the attacker has admin credentials.Can you recover into a separate, clean account?Cross-account recovery and backup isolation
Your most recent backups were taken after the attacker got in.Do you know which restore point is clean?Immutable backups and clean restore points
The cloud region is degraded.Can you restore cross-region?Cross-region DR
The database came back, but the app won’t connect.Were security groups, IAM roles and network configurations cloned and restored too?Metadata and configuration recovery
The person who owns this system left six months ago.Who has the runbook?Ownership and documentation
The app servers came up before the database and identity services they depend on.Was recovery order defined in advance?Dependency mapping and recovery prioritization

Don’t underestimate the fourth inject. Data without its configuration and permissions is essentially a pile of bricks, not a house.

How to turn tabletop findings into real changes

A tabletop only improves your tech stack if its findings leave the room as work. Every gap the injects expose should follow the same path:

  1. Log it as a ticket, not a bullet in a slide deck.
  2. Give it one owner and a deadline.
  3. Fix it at the source. For example, if nobody has restored a full environment end to end, the fix isn’t a policy update. It’s defining the recovery: which resources come back, in what order, into which account and region, with their configuration intact.
  4. Rerun the scenario that exposed the gap and confirm the fix holds.

The tabletop exercise playbook: 7 steps for your first one

If this is your first tabletop, start simple. The goal is a team that leaves confident and a list of real gaps, not a team that leaves overwhelmed.

  1. Pick your five critical processes. Get business sign-off and map the systems and dependencies behind each one.
  2. Set success criteria in writing. Record RTO, RPO and decision checkpoints before day one.
  3. Start with a one-hour walkthrough on a single critical system. Add injects and complexity once each step is confirmed and the team feels confident.
  4. Run a real, timed restore. Talk through the response, then actually recover the systems in scope and record how long it takes.
  5. Debrief the same day. Document what took longer than expected and who was unsure of their role.
  6. Assign owners and fix it. One owner per finding, with a date.
  7. Retest and repeat on a schedule. Run it quarterly at minimum, and after any major architecture change.

Why teams skip the restore, and how to make it affordable

Many teams skip a full disaster recovery drill because of cost and effort. Spinning up hundreds of resources in a second account just to prove a point doesn’t go over well with a management team that isn’t yet convinced.

That’s where tooling changes the math. With N2W recovery scenarios, teams can:

  • Restore a full environment, not just files. Bring back the resources behind a critical process, including network configuration and metadata.
  • Set recovery priority. Define the order resources come back so dependencies like databases and identity services are up first.
  • Run low-cost dry runs. Validate permissions, availability and dependencies without standing up the full infrastructure every time.
  • Schedule DR tests automatically. Recovery testing stops being something that happens once a year, or for the first time in the middle of a catastrophe.

Restores must happen in peacetime. In my experience, the organizations that come through cyberattacks and cloud outages are the ones that rehearsed.

Tabletop exercise FAQ

How often should you run a tabletop exercise?

Run a tabletop exercise at least quarterly, and after any major change to your architecture, cloud footprint or team. Automated, scheduled DR tests can fill the gaps between full exercises.

How long should a tabletop exercise take?

A first tabletop can be a one-hour walkthrough focused on a single critical system. More advanced exercises with multiple injects and a live restore typically take a half day or longer.

What’s the difference between a tabletop exercise and a disaster recovery test?

A tabletop exercise tests people, decisions and process by walking through a simulated incident. A disaster recovery test proves the technology can actually restore systems within your RTO and RPO. The most effective tabletops include both.

Who should facilitate a tabletop exercise?

Someone who is not a participant. The facilitator runs the scenario, introduces injects and keeps time, which is hard to do while also responding to the incident.

What should a ransomware tabletop exercise include?

A ransomware tabletop should test recovery into a clean account, identifying an uninfected restore point, restoring configuration and permissions along with data, recovering in the right dependency order, and the legal and communications decisions that run alongside recovery.

Need help with a tabletop checklist? It’s what we do everyday. Schedule a short demo.

You might also like