What is a cybersecurity tabletop exercise?
A tabletop exercise is a guided discussion, not a technical test. A facilitator presents an incident scenario in stages, called injects, and the people who would handle a real incident explain how they would respond: who gets called, what gets shut down, who talks to customers, when regulators are told.
Nothing is attacked and no systems go offline. The goal is to find the gaps in your plan, your contact lists and your decision-making while the stakes are low.
Why auditors care about tabletop exercises
Most compliance frameworks expect you to have an incident response plan and to show that it works. A tabletop exercise is usually the most practical way to produce that evidence.
| Framework | What it expects | How a tabletop exercise helps |
|---|---|---|
| SOC 2 | Incident response and recovery activities are defined and carried out (Common Criteria CC7.3 to CC7.5) | Auditors often ask for proof that the incident response plan was tested during the period |
| ISO 27001:2022 | Incident management planning, response and learning (Annex A 5.24 to 5.27) and ICT readiness for business continuity (5.30) | Shows the plan is understood and that lessons learned feed back into the ISMS |
| HIPAA | Security incident procedures (45 CFR 164.308(a)(6)) and a contingency plan, including testing and revision procedures (164.308(a)(7)) | Gives documented evidence that incident and contingency procedures were exercised |
| HITRUST | Incident management and business continuity requirements in the HITRUST CSF | Assessors look for evidence that plans are tested on a regular schedule, typically at least once a year |
| India DPDP Act and CERT-In | Breach notification to the Data Protection Board and affected people; CERT-In reporting of specified incidents within 6 hours | Lets you rehearse the notification decisions and timelines before a real incident |
A tabletop exercise doesn't replace technical testing such as backup restores or penetration tests. It complements them by testing the people and decisions around an incident.
Who should take part
Keep the group small enough to talk, usually 6 to 12 people:
- Incident response lead or security owner
- IT or engineering lead for the affected systems
- A senior decision-maker (CEO, COO or CTO)
- Legal or compliance, for notification decisions
- Customer success or communications
- HR, if the scenario involves an employee
- Key vendors, such as your managed IT provider, if they play a role in your plan
Add a facilitator who runs the scenario and a note-taker who records decisions, gaps and action items.
Five tabletop exercise scenarios that map to audit requirements
- Ransomware on a file server or laptop fleet. Tests isolation, backup restore decisions, ransom policy, and when to involve law enforcement and insurers.
- Customer data exposed through a misconfigured cloud storage bucket. Tests detection, scoping which records were exposed, customer notification and regulatory reporting.
- Compromised admin account through phishing. Tests account lockdown, log review, privileged access controls and how quickly access can be revoked.
- Vendor breach. A key SaaS provider or business associate reports a breach involving your data. Tests vendor contracts, BAAs, and how you assess your own exposure.
- Lost or stolen laptop with patient or customer data. Tests encryption evidence, device management and whether the incident is a reportable breach under HIPAA or DPDP.
Pick the one or two scenarios most relevant to your business and audit scope. A health-tech company should almost always include a patient data scenario.
How to run a tabletop exercise: step by step
- Set the objective. For example: "Confirm we can decide within 4 hours whether a data exposure is reportable."
- Choose the scenario and write 4 to 6 injects that reveal new information over time.
- Invite participants and share the incident response plan in advance.
- Run the session (60 to 120 minutes). The facilitator presents each inject and asks: what do you do now, who does it, and how do you know?
- Record decisions, gaps, unclear responsibilities and missing information as you go.
- Hold a short debrief straight after: what worked, what didn't, what surprised people.
- Write an after-action report with clear actions, owners and due dates.
- Update the incident response plan, contact lists and runbooks, then track the actions to closure.
Tabletop exercise checklist
Before the exercise
- Objective agreed with leadership
- Scenario and injects written
- Incident response plan and contact list shared with participants
- Facilitator and note-taker assigned
- Date, time and attendance confirmed
During the exercise
- Attendance recorded (names and roles)
- Decisions and timings noted for each inject
- Gaps and open questions captured
After the exercise
- After-action report written within one week
- Actions assigned with owners and due dates
- Incident response plan updated and version recorded
- Evidence filed for your next audit
What evidence to keep for your audit
Auditors usually ask for:
- The scenario and injects used
- The attendance list with names, roles and date
- Notes or minutes from the session
- The after-action report with findings and actions
- Proof that actions were tracked and the plan was updated (version history or change log)
Keep these together in your evidence folder or compliance platform (Vanta, Drata, Sprinto and similar tools all have a place for them).
How often should you run one?
At least once a year, and after any major change: a new product, a move to a new cloud provider, a merger, or a real incident. SOC 2 Type 2 and HITRUST assessments look at whether testing happens on a regular schedule, so an annual exercise in the same quarter each year is a simple habit that keeps you audit-ready.
Common mistakes to avoid
- Using a scenario so generic that nobody learns anything
- Inviting only IT, so legal, leadership and communications decisions never get tested
- Not writing anything down, which leaves no evidence for auditors
- Writing an after-action report but never closing the actions
- Treating the exercise as a box-ticking event instead of a real rehearsal


