An incident response tabletop exercise tests how a team would coordinate during a simulated security incident. PCI DSS and CMMC impose testing requirements on organizations within their scope, while SOC 2 examines related controls.
None provides a complete quality standard for the exercise itself. This playbook covers how to test escalation, decision ownership, and cross-functional handoffs, and how Reflex Security captures evidence of team behavior.
Why CISOs Need to Test Incident Response, Not Just Document It
Three frameworks shape incident response testing, but they create different obligations. PCI DSS v4.0.1 Requirement 12.10.2 requires covered entities to review and test their incident response plans at least once every 12 months. SOC 2 evaluates controls related to incident response and recovery. CMMC Level 2 includes a requirement to test the organizational incident response capability.
PCI DSS goes one step further and names a possible method in its guidance: simulated incidents and responses, run as a tabletop with relevant personnel. The guidance identifies participation. It does not define how to evaluate performance.
Meeting the requirement with a tabletop produces useful exercises. An annual scripted discussion can expose plan gaps, correct stale contact lists, and introduce Legal and Communications to the security team. For many programs, it is the right starting point. Tabletop requirements by regulation explain which organizations face formal testing obligations.
The gap often appears after the first exercise. By then, the obvious plan gaps are closed and the contact list resolves. The next question is whether the team can execute.
Revised federal guidance (NIST SP 800-61 Rev. 3) now treats exercises as part of continuous improvement. The revised incident-handling guidance analysis explains that shift. Regulated banks may also face supervisory expectations beyond PCI DSS and SOC 2, which sit outside this playbook.
Framework | Provision | What it requires or assesses | What it does not define | Framework |
PCI DSS v4.0.1 | Annual review and testing of the incident response plan, including every element in 12.10.1 | One required method or a performance standard | PCI DSS v4.0.1 | |
SOC 2 | Incident response and recovery controls, including periodic recovery-plan testing | One format, cadence, or measure of team competence | SOC 2 | |
CMMC Level 2 | Testing the organization’s incident response capability | Third-party assessment requirements are suspended; Phase I self-assessments remain active. | CMMC Level 2 |
One note on CMMC: NIST withdrew SP 800-171 Rev. 2 in May 2024, but 32 CFR 170.14(c)(3) still bases CMMC Level 2 on its 110 requirements.
The Department suspended Phase II implementation on July 13, 2026. In early September, a class deviation directed contracting officers to remove third-party assessment requirements from contracts. Self-assessments and annual affirmations still apply, and DFARS 252.204-7012 still requires the 110 Rev. 2 controls. For a defense supplier completing a self-assessment, Rev. 2 therefore governs. The Department is reviewing the program, so confirm current status before planning around it.
Reflex focuses on the performance questions those frameworks leave open.
What Should an Incident Response Tabletop Exercise Actually Test?
An incident response tabletop exercise should test decisions made with incomplete information as well as recall of the document. Four areas deserve pressure: incident declaration, decision ownership, cross-functional handoffs, and the gap between stated intent and observable action.
The plan still matters. A tabletop can reveal outdated procedures, missing owners, and unclear escalation paths. Reflex extends that review by testing how participants respond as the simulated incident changes.
What an IR tabletop can test | What a discussion-based exercise cannot directly observe |
Whether the escalation path in the plan matches the one people name out loud | Whether anyone follows it at 2 a.m. on one ambiguous alert |
Whether every function knows which decision belongs to it | Who makes the call when two people each assume the other has it |
Whether the contact list resolves to people who answer | How long a handoff takes when the receiving function is mid-shift |
Whether the team can describe containment | Whether containment gets ordered before or after the business asks what it will cost |
Whether the plan covers a scenario type | Whether the team recognizes that scenario when it arrives mislabeled |
The right column lists behaviors a scripted discussion cannot verify. Strong incident response scenarios create enough pressure to surface them.
An incident response tabletop exercise template should contain four elements:
A named owner for every escalation decision
An observation sheet organized by timestamp
A meaningful failure condition
An evidence schedule mapping observations to relevant requirements
A list of discussion topics alone cannot measure performance. The Reflex observation sheet starts with each decision and maps it back to the requirement it supports. Reflex covers these artifacts in the Tabletop Exercise Template Toolkit: 6 Templates for Security Teams.
The People Problem: Testing Decisions, Escalation, and Cross-Functional Coordination
Escalation breaks in three places: the moment an alert becomes an incident, the moment a function outside security gets pulled in, and the moment somebody has to wake a person senior to them. Each is a decision with an owner on paper. Under pressure the owner is whoever moves first, and sometimes nobody moves at all.
Consider the incident response tabletop exercise example used throughout this playbook: a mid-size regional bank that accepts cards and operates a SOC 2-attested digital banking service. The bank runs a 24×7 SOC and keeps outside counsel on retainer. Its compliance function often enters incidents late. The bank passes its assessment every year.
The facilitator gives the team this inject and observes who takes ownership:
Core banking authorization is failing intermittently for card-present transactions across the branch network. The SOC has one payment-switch alert and a growing service-desk queue. Who declares an incident, and how long does that decision take?
Two people know the answer, but each waits for the other to act. The exercise exposes unclear ownership.
Escalation decision point | Who is assumed to own it | How it fails under pressure |
An alert becomes an incident | The SOC shift lead | The signal is ambiguous, so the shift lead waits for a second indicator. Every clock the team reports later starts here |
Outside counsel is engaged | The IR lead | The IR lead and the SOC manager each believe the other made the call. Nobody did |
Compliance is brought in | The IR lead's checklist | Compliance sits on a distribution list rather than in the decision, and finds out after containment is already chosen |
An executive is woken | The on-call escalation matrix | The matrix names a title, the phone reaches a person, and the person has been on leave for a week |
Each row is behavior an exercise can reveal and a plan review cannot.
Reflex gives the same team a second inject. A privileged service account has authenticated from an unfamiliar jurisdiction, and nobody has notified Compliance.
Who owns that call? The exercise tests whether a vague intention to notify Compliance becomes an assigned action.
Putting Technical, Legal, Communications, and Leadership Under Pressure
A cross-functional exercise earns the name only when the other functions can say no. Technical, legal, communications, and leadership each hold a decision the incident response team needs and cannot make alone. Attendance proves none of that. The test is whether the IR lead gets a usable answer inside the window the incident allows.
Pressure arrives as simultaneity, so Reflex runs the demands concurrently. Counsel needs facts the investigation has not produced yet and will not commit to language without them. Communications is holding a customer statement against a scope that changed twice in the last hour. The SOC has containment ready and wants authorization from someone who is on another call. An incident does not queue.
Legal and communications want different things from the same fact. The incident response tabletop exercise scenarios that expose this force the IR lead to choose which one to serve first.
Leadership introduces a different kind of pressure. An executive receives a page, and the IR lead has eleven minutes to prepare a briefing. The team does not yet know whether cardholder data is in scope, but the executive will ask.
Acknowledging that the scope is unknown is accurate, but it can still cost credibility. Rehearsing that briefing under a clock is a legitimate exercise objective that many programs overlook.
This playbook stops at that moment. The executive’s next decisions belong to a different exercise with a different cast. Those decisions include disclosure posture, customer and regulatory communications, and the choice of spokesperson. Reflex covers that wider format in its guide to crisis management simulation.
How to Measure Incident Response Team Readiness
Readiness appears in observable behavior recorded during the exercise. Four observations carry most of the value:
Time to escalation
Ownership of each decision
Completion of each handoff
Alignment between stated and completed actions
Reflex records these findings while the exercise runs.
The previous exercise should answer one plain question: what evidence shows that the team can execute?
For many programs, the available evidence is a date, participant list, scenario document, and unresolved recommendations. That package may support Requirement 12.10.2 when the exercise covers the required plan elements. It still says little about decision timing, ownership, or completed handoffs.
An assessor may verify that an exercise occurred. An incident reveals whether the team can execute under pressure. Passing an assessment therefore does not establish how the team will perform during a real incident.
Turning observations into change is its own discipline. Measuring tabletop results covers the reporting and follow-through process.
Reflex produces the timestamped behavior record as the exercise's primary output.
Why Annual, Scripted Tabletop Exercises Aren’t Enough
An annual scripted exercise is cheap, schedulable, and useful. It finds plan gaps, corrects stale contacts, and gets the cross-functional cast in one room before an incident does it for them.
The format becomes less useful once the team can pass it without exposing new gaps. That can happen as early as the second exercise.
Programs often design the exercise to produce evidence that testing occurred. The result is a predictable scenario with scheduled injects and narrated consequences. This compliance incentive can produce exercises nobody fails, regardless of the facilitator’s competence.
Annual scripted exercise | Adaptive crisis simulation with Reflex | |
Preparation | A facilitator may spend days building a credible scenario | One-Click Scenario Generation produces five customized scenarios from a domain in 10 to 15 minutes |
Adversary behavior | Usually follows a prepared sequence and facilitator schedule | Responds to participant decisions, delays, and omissions |
Failure condition | Often lacks an operational failure condition | The simulated situation can worsen when a decision is late, incorrect, or unowned |
Consequence of a poor decision | The facilitator usually narrates the outcome before continuing | The decision changes the adversary’s response and subsequent conditions |
Evidence produced | Attendance, facilitator observations, recommendations, and an after-action report | Timestamped evidence of decisions, handoffs, escalation delays, and findings |
Best fit | Initial plan review or an exercise following major organizational change | Teams ready to test coordination and decision-making under adaptive pressure |
A program that has outgrown its annual exercise has options short of replacing it. Fixing a stale program is often the cheaper first step. Adaptive simulation becomes relevant when the team needs observable consequences and performance evidence.
From Tabletop to “People Pen Test”: How Reflex Security Tests Incident Readiness
Reflex describes its crisis simulation as a people pen test. The scenario begins with the organization’s external footprint. An adaptive adversary responds to participant decisions, while AI agents represent unavailable stakeholders. The platform records actions, decisions, and handoffs as evidence.
The bank's escalation problem does not yield to a better slide deck.
Build a Specific Scenario
A scenario about "a ransomware event at a financial institution" cannot test whether this bank's SOC recognizes its own payment switch behaving strangely. One-Click Scenario Generation takes a company domain and produces five customized scenarios in 10 to 15 minutes. Reflex draws them from information publicly available about that environment. Reflex explains the mechanics in adaptive scenario generation.
Make Hesitation Change the Incident
A path only gets tested when hesitation costs something, which requires an adversary that notices. The Adaptive Adversary Engine reacts to what the team does and what it defers. Victoria, an AI facilitator, maintains pressure on the decision throughout a 60-to-120-minute exercise. When the team stalls on ownership, the scenario continues to develop.
Test Cross-Functional Handoffs
A handoff to Legal cannot be observed when nobody represents Legal. Reflex fills empty seats with agents that respond in character. These can include outside counsel, communications leaders, and regulators.
The Facilitator Guide supports the human facilitator, while the Investigation Console records what each participant did and when.
Turn Behavior Into Evidence
An assessor or program owner reviewing a finding wants the evidence behind it. The Reflex After Action Report (AAR) contains evidence-backed findings and recommendations for teams to act on. It includes:
A minute-by-minute progression of the exercise
Direct transcript evidence for each finding
MITRE ATT&CK and NIST CSF alignment
Analysis of communication, leadership, individual contributions, and skills gaps
Action items with named owners and deadlines
Documentation supporting SOC 2, ISO 27001, and cyber-insurance testing
The report provides evidence that a sign-in sheet cannot.
Reflex still depends on organizational context that public reconnaissance cannot provide. It also serves a different purpose from a red team. Reflex tests how the organization responds after detecting an incident. It does not test whether an attacker can gain access. For a team running its first exercise, an annual scripted discussion may still be the right starting point.
See how the Reflex platform is built. Run one Reflex scenario against your environment. The result will answer the readiness question faster than this playbook can.
See what your team does under real pressure.
Put your readiness to the test. Sixty minutes, your real environment, no slides.
Book A demo
Frequently Asked Questions
Does PCI DSS require an annual tabletop exercise specifically?
No. PCI DSS Requirement 12.10.2 requires annual review and testing of the incident response plan and names no required method. A tabletop with relevant personnel is a common way to comply, but PCI DSS does not define how to evaluate performance.
What does an assessor actually accept as evidence of testing?
The testing procedure for PCI DSS Requirement 12.10.2 directs assessors to interview personnel and examine documentation. Relevant evidence may include a dated scenario, participant list, session notes, and remediation items with owners. That documentation confirms testing activity. It says little about team performance.
What must an incident response tabletop exercise template contain?
At minimum, the template needs named decision owners, timestamped observations, a meaningful failure condition, and an evidence map. Discussion topics alone cannot measure performance.
Can a team run the exercise without taking the SOC off the floor?
Partly, although the coverage trade-off remains. A 60-to-120-minute exercise still needs the on-call IR lead and at least one responding analyst. Their participation reduces coverage during that window. Scheduling during a quieter period can help. Reflex agents can also represent functions that would otherwise be absent, but they cannot replace the core responders being tested.
How is this different from a red team engagement?
A red team tests whether an attacker gets in and how far they travel. An exercise like this tests what the organization does once it knows. Reflex is the second kind of test. Both are worth running, and their findings rarely overlap: a red team report names a control gap, an exercise record names a decision nobody owned.
References
American Institute of Certified Public Accountants. (2022). 2017 trust services criteria with revised points of focus (CC7.4–CC7.5). AICPA & CIMA. https://www.aicpa-cima.com/resources/download/2017-trust-services-criteria-with-revised-points-of-focus-2022
National Institute of Standards and Technology. (2006, September 21). Guide to test, training, and exercise programs for IT plans and capabilities (SP 800-84). NIST Computer Security Resource Center. https://csrc.nist.gov/pubs/sp/800/84/final
National Institute of Standards and Technology. (2021, January 28). Protecting controlled unclassified information in nonfederal systems and organizations (SP 800-171 Rev. 2, control 3.6.3). NIST Computer Security Resource Center. https://csrc.nist.gov/pubs/sp/800/171/r2/upd1/final (Withdrawn by NIST on May 14, 2024; incorporated by reference for CMMC Level 2 at 32 CFR 170.14(c)(3).)
PCI Security Standards Council. (2024, June 11). Payment card industry data security standard: Requirements and testing procedures, version 4.0.1 (Requirement 12.10.2). PCI Security Standards Council. https://docs-prv.pcisecuritystandards.org/PCI%20DSS/Standard/PCI-DSS-v4_0_1.pdf
U.S. Department of Defense, Office of the Chief Information Officer. (2024). CMMC assessment guide level 2, version 2.13 (IR.L2-3.6.3). DoD Chief Information Officer. https://dodcio.defense.gov/Portals/0/Documents/CMMC/AssessmentGuideL2v2.pdf
U.S. Department of Defense, Office of the Chief Information Officer. (2026). CMMC program status and Phase II suspension. https://dodcio.defense.gov/CMMC/About/
