# Tabletop Exercises

Tabletop exercises are facilitated, discussion-based simulations that test how people would use an incident response plan without deliberately disrupting live systems.

Cloud concept. Updated 2026-10-29. Page: https://blowstack.com/tools/cloud-concepts-hub/tabletop-exercises

> Participants work through a realistic incident scenario, explain their decisions, and identify gaps in responsibilities, communications, access, and response procedures. These exercises validate organizational readiness at relatively low operational risk, but they must be complemented by technical tests to establish whether controls and recovery mechanisms actually work.

Practice exams covering Tabletop Exercises: [SCS-C03 AWS Certified Security - Specialty](https://blowstack.com/practice-exams/aws-certified-security-specialty), [SAP-C03 AWS Certified Solutions Architect - Professional](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional).

## 6 key aspects of Tabletop Exercises

Effective tabletop exercises combine realistic scenarios, explicit objectives, cross-functional decisions, and tracked improvements while keeping discussion-based validation distinct from technical proof.

1. **Realistic, objective-driven scenarios**: Choose scenarios that reflect the organization's workloads, threats, and dependencies. Define observable objectives, such as locating evidence, selecting a containment procedure, or identifying the authority to declare an incident.
2. **Facilitated discussion and scenario injects**: A facilitator presents information progressively and asks participants to explain decisions using existing plans. New facts introduce uncertainty and test whether escalation and response procedures remain usable.
3. **Cross-functional roles and authority**: Validate responsibilities across security, operations, application teams, management, and relevant legal or communications functions. Confirm who can authorize disruptive containment, emergency access, recovery, and external notifications.
4. **Low-risk process validation**: Keep the tabletop discussion-based, using simulated findings and evidence rather than deliberately changing production resources. This reduces operational risk but does not demonstrate that technical controls function correctly.
5. **Complementary technical testing**: Use controlled simulations, automation tests, restore tests, or fault-injection experiments to verify assumptions uncovered during discussion. Establish authorization, scope, monitoring, stop conditions, and recovery procedures before executing changes.
6. **Documented improvement and retesting**: Capture decisions, gaps, and unsupported assumptions in an after-action report. Assign remediation owners and deadlines, then retest to establish whether the changes resolved the weaknesses.

## Cloud services for Tabletop Exercises

GuardDuty findings can supply the initial scenario, while CloudTrail records provide investigation context and expose questions about evidence availability. Participants explain how they would use documented procedures, including response automations implemented with Systems Manager. Resilience Hub assessments can identify recovery assumptions worth challenging during the discussion. Where technical validation is needed, Fault Injection Service can introduce supported faults in an explicitly authorized, bounded experiment. These services support different parts of readiness testing; none substitutes for a facilitated tabletop. Keep simulated decisions separate from executed actions, and convert exercise findings into tracked changes followed by appropriate technical tests and repeat discussions.

- **[AWS Resilience Hub](https://blowstack.com/tools/cloud-services-hub/aws-resilience-hub)**: Assesses supported application resources against resilience policies, including recovery time and recovery point objectives, and provides recommendations that can inform exercise scenarios. Its assessments support resilience planning but do not validate incident-command decisions or prove that security response procedures work.
- **[Amazon GuardDuty](https://blowstack.com/tools/cloud-services-hub/amazon-guardduty)**: Provides threat findings that can form realistic starting points for cloud security exercises. Sample findings can support scenario preparation, but generating a sample finding does not demonstrate that a real attack would be detected.
- **[AWS CloudTrail](https://blowstack.com/tools/cloud-services-hub/aws-cloudtrail)**: Provides records of supported account and API activity that responders can use during investigation. Exercises should validate whether the required events are being recorded, retained, protected, and made accessible to responders, rather than assuming every relevant activity is logged by default.
- **[AWS Systems Manager](https://blowstack.com/tools/cloud-services-hub/aws-systems-manager)**: Systems Manager Automation can implement response procedures that participants reference during a tabletop and validate separately through controlled execution. Technical tests should check permissions, approval steps, target selection, failure handling, and recovery actions before production use.

## Tabletop Exercises exam questions

Real practice exam questions on Tabletop Exercises, with the correct answer and its explanation.

### Question 1 (SAP-C03)

**Question:**

A payments company maintains a warm standby environment in a second AWS Region. Recent technical recovery tests met the recovery time objective (RTO) and recovery point objective (RPO). Since those tests, the company has outsourced overnight operations and changed who can authorize recovery when replication lag exceeds the RPO.

Before the next live recovery test, the company must evaluate whether the new operations provider, application owners, and business leaders can coordinate a Regional recovery. The evaluation must address incomplete monitoring information, an unavailable primary approver, and customer notification obligations. No recovery actions or resource changes are authorized during this evaluation.

Which approach best meets these requirements?

**Correct answer:** Have a facilitator present an evolving Regional outage scenario to the participating teams. Introduce uncertain replication status and an unavailable approver, and require participants to explain authorization, escalation, and notification decisions using current procedures. Record gaps, assign remediation owners, and revisit findings before the live recovery test.

**Explanation:** This discussion-based exercise directly evaluates organizational readiness without changing resources. Progressive scenario updates expose gaps in decision authority, cross-team handoffs, communications, and procedures. Tracking remediation makes the findings actionable. The exercise complements the technical recovery tests rather than replacing or revalidating their RTO and RPO evidence.

### Question 2 (SCS-C03)

**Question:**

A company's security operations center hands incident investigations between teams in different time zones. During a recent AWS security incident, the incoming team repeated completed investigative work and overlooked an unresolved hypothesis about activity in a second AWS Region. The incident record was complete, but the response plan did not specify how to communicate investigative uncertainty during a handoff.

The company has revised its handoff procedures. Before conducting technical simulations, it wants to evaluate whether outgoing and incoming responders can maintain a consistent understanding of incident scope, distinguish confirmed facts from assumptions, and prioritize unfinished investigative work as new information becomes available. The evaluation must not send operational alerts or execute actions in AWS accounts.

Which procedure BEST meets these requirements?

**Correct answer:** Have a facilitator present a fictional AWS incident to the outgoing team and require a handoff to the incoming team using the revised procedures. Introduce additional evidence that challenges an earlier scope assumption. Observe how both teams communicate facts, uncertainty, and unfinished work; record gaps against predefined objectives and assign corrective actions for reevaluation.

**Explanation:** This tabletop exercise directly evaluates the revised handoff process through structured discussion without operational alerts or AWS resource changes. The evolving evidence tests whether responders preserve investigative context and revise priorities. Observed outcomes and tracked corrective actions provide evidence of procedural effectiveness, although separate technical tests are still needed to validate tools and controls.

## Practice Tabletop Exercises in a full exam

Questions on Tabletop Exercises in each practice exam, with every answer option and an explanation for each:

- [SCS-C03](https://blowstack.com/practice-exams/aws-certified-security-specialty): 3 questions
- [SAP-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional): 1 question

## What is Tabletop Exercises

A tabletop exercise tests an incident response plan through structured discussion rather than live incident execution. A facilitator presents a scenario, such as compromised cloud credentials or suspected data exfiltration, and asks participants to explain what they would do using the current plan. The objective is to expose unclear decisions, missing procedures, and coordination failures before a real incident occurs. An exercise should evaluate the plan and supporting processes, not assign blame to individuals.

Start by defining the scope and measurable objectives. For example, determine whether the team can identify the incident commander, locate the credential-compromise runbook, select an appropriate containment action, and identify who authorizes customer communications. Include security responders, application owners, cloud operations, and business stakeholders. Legal, privacy, and communications representatives should participate when the scenario involves notification obligations or external messaging. Assign a facilitator and someone to record decisions, assumptions, and gaps.

In a cloud scenario, the facilitator might begin with a simulated threat-detection finding involving an application role. Participants explain how they would establish which account and workload are affected, inspect audit records, preserve evidence, and assess the permissions available to the suspected attacker. Subsequent scenario updates, often called injects, could reveal unexpected object downloads, disabled logging, or an unavailable account administrator. These updates test whether the plan remains usable when information is incomplete and normal access paths fail.

Discuss containment precisely rather than accepting statements such as “disable access.” Responders should identify the relevant identity type, the mechanism for restricting access, the implications for existing sessions, and the expected application impact. They should also explain how they would preserve volatile evidence and record investigative actions. The exercise should cover escalation, eradication, recovery validation, and the conditions for declaring the incident resolved. Cloud-specific considerations include cross-account permissions, regional dependencies, centralized logs, emergency access, and the division of responsibility between the customer and provider.

Tabletops are inexpensive relative to disruptive tests and are especially useful for validating authority, communications, and decision-making. However, discussion cannot prove that an alert reaches the on-call engineer, an automation has sufficient permissions, or a backup restores successfully. Record a participant's proposed action separately from evidence that the action has been technically tested. A tabletop is not a penetration test, a failover test, or a live chaos experiment.

Use technical exercises to address these limits. AWS Fault Injection Service can introduce supported faults in a controlled environment to test operational behavior, while AWS Resilience Hub can assess supported application resources against resilience policies and help identify recovery-readiness gaps. Neither service replaces a facilitated security incident discussion. Technical experiments require explicit authorization, bounded targets, monitoring, stop conditions, and recovery procedures; stopping an experiment does not necessarily reverse every effect.

Finish with an after-action review and an improvement plan. Assign each gap an owner, priority, completion date, and validation method. Update runbooks, access arrangements, contact information, and training, then repeat relevant scenarios after remediation or significant architectural changes. Measure decision quality and objective completion; timings from a discussion should not be treated as measured production detection or recovery times.

## Learn Tabletop Exercises in lessons

3 short lessons on Tabletop Exercises in 2 certification courses.

- SAP-C03: Tabletop Exercises: disaster recovery readiness rehearsals (Premium), https://app.blowstack.com/lessons/tabletop-exercises-disaster-recovery-readiness-rehearsals-sap-c03
- SCS-C03: Tabletop Exercises: scenario-driven plan validation (Premium), https://app.blowstack.com/lessons/tabletop-exercises-scenario-driven-plan-validation-scs-c03
- SCS-C03: Tabletop Exercises vs Chaos Engineering (Premium), https://app.blowstack.com/lessons/tabletop-exercises-vs-chaos-engineering-scs-c03
