Performing Ransomware Tabletop Exercise
When to Use
- Testing organizational ransomware response procedures annually or after major infrastructure changes
- Validating decision-making processes for ransom payment, regulatory notification, and public disclosure
- Training executives, IT, legal, PR, and operations teams on their roles during a ransomware incident
- Meeting cyber insurance policy requirements for documented incident response testing
- Identifying gaps in recovery playbooks, communication plans, and backup procedures
Do not use as a substitute for technical controls testing. Tabletop exercises validate procedures and decision-making, not technical detection or prevention capabilities.
Prerequisites
- Documented incident response plan (IRP) that participants should have read before the exercise
- Identified exercise participants from: executive leadership, IT/security, legal, communications/PR, HR, operations, and external counsel
- Facilitator who is independent from the IR team (to provide objective evaluation)
- Ransomware scenario designed with injects that escalate over multiple rounds
- Evaluation criteria aligned to NIST CSF Respond/Recover functions
- Conference room or virtual meeting for 2-4 hours with no interruptions
Workflow
Step 1: Design the Exercise Scenario
Build a realistic scenario based on current threat actor TTPs:
Scenario Structure:
Phase 1: Initial Detection (30 min)
- SOC receives alert for suspicious process execution on file server
- EDR detects Cobalt Strike beacon on 3 workstations
- Inject: External threat intel report links C2 IP to LockBit affiliate
Phase 2: Escalation (30 min)
- Ransomware executes on 40% of servers during overnight hours
- Ransom note demands $2M in Bitcoin with 72-hour deadline
- Inject: Attackers contact media claiming data theft of customer PII
Phase 3: Decision Points (45 min)
- Backup assessment reveals immutable copies are intact but primary backups encrypted
- Legal advises on breach notification timeline (72 hours GDPR, varies by US state)
- Inject: Threat actor publishes sample of stolen data on leak site
Phase 4: Recovery and Communication (45 min)
- Recovery time estimate: 5-7 days from immutable backups
- Insurance carrier engages negotiation firm
- Inject: Major customer threatens contract termination without update within 24 hours
Scenario Variables to Customize:
- Threat actor group and known TTPs
- Percentage of infrastructure encrypted
- Whether backups are intact, partially compromised, or fully destroyed
- Type of data exfiltrated (PII, PHI, financial, trade secrets)
- Applicable regulatory frameworks (GDPR, HIPAA, PCI DSS, SEC rules)
- Ransom amount and payment deadline
Step 2: Prepare Exercise Materials
Create the following documents for participants:
- Exercise Overview Briefing - Ground rules, objectives, scope, and participants
- Situation Reports (SITREPs) - One per phase, distributed as the exercise progresses
- Inject Cards - New information introduced at specific times to force decision-making
- Decision Point Worksheets - Structured forms for documenting group decisions
- Evaluation Scorecard - Criteria for assessing response quality
Key Decision Points to Include:
- When to activate the incident response team
- Whether to shut down systems or contain selectively
- Whether to engage law enforcement (FBI IC3, CISA)
- Whether to pay the ransom and under what conditions
- When and how to notify regulators, customers, and the public
- How to prioritize system recovery order
Step 3: Facilitate the Exercise
Facilitator Responsibilities:
- Present each phase scenario and distribute SITREPs
- Introduce injects at predetermined times to increase pressure
- Ask probing questions to test decision-making reasoning
- Ensure all participant groups contribute (prevent IT from dominating)
- Document all decisions, rationales, and action items
- Track time management (many teams lose time on early phases)
Probing Questions by Phase:
Phase 1 - Detection:
- Who makes the call to declare an incident? What criteria trigger it?
- How do we determine the scope of compromise from initial alerts?
- Do we have the forensic capability to investigate or do we need external help?
Phase 2 - Escalation:
- What is our communication plan for employees? Do they know not to turn on affected machines?
- Have we isolated the network to prevent further encryption?
- Who authorizes system shutdowns that impact business operations?
Phase 3 - Decision:
- Under what conditions would we consider paying the ransom?
- What are the legal obligations for notification at this point?
- How do we handle the public leak of customer data?
Phase 4 - Recovery:
- What is the recovery priority order? Is it documented or decided ad hoc?
- How long until critical business operations resume?
- What evidence preservation is required for law enforcement and insurance?
Step 4: Evaluate and Score Responses
Score each functional area against defined criteria:
| Evaluation Area |
Score (1-5) |
Criteria |
| Detection & Escalation |
|
Timely incident declaration, proper chain of command |
| Containment |
|
Network isolation, credential reset, scope assessment |
| Communication - Internal |
|
Employee notification, executive briefing, documented decisions |
| Communication - External |
|
Regulatory notification, customer communication, media response |
| Recovery Planning |
|
Backup verification, recovery priority, RTO tracking |
| Legal & Compliance |
|
Breach notification timelines, evidence preservation, law enforcement engagement |
| Business Continuity |
|
Manual operations, customer impact mitigation, revenue loss estimation |
| Payment Decision |
|
Structured framework, legal review, OFAC sanctions check |
Step 5: Document Findings and Remediation Plan
Produce an after-action report (AAR) within 5 business days:
AAR Contents:
- Exercise overview and objectives
- Scenario summary and injects
- Key decisions made and rationale
- Strengths observed
- Gaps identified with severity rating
- Remediation actions with owners and deadlines
- Comparison to previous exercise results (if applicable)
Key Concepts
| Term |
Definition |
| Tabletop Exercise (TTX) |
Discussion-based exercise where participants walk through a simulated incident scenario to test plans and procedures |
| Inject |
New information introduced during the exercise to change the scenario and force additional decision-making |
| SITREP |
Situation Report providing current status of the simulated incident at each exercise phase |
| After-Action Report (AAR) |
Post-exercise document capturing findings, gaps, strengths, and remediation actions |
| Double Extortion |
Ransomware tactic where attackers both encrypt data and threaten to publish stolen data unless ransom is paid |
| OFAC Check |
Verification that ransom payment recipient is not on the US Treasury OFAC sanctions list, which would make payment illegal |
Tools & Systems
- CISA Tabletop Exercise Packages (CTEPs): Free scenario packages from CISA designed for critical infrastructure sectors
- FEMA Homeland Security Exercise and Evaluation Program (HSEEP): Methodology for designing, conducting, and evaluating exercises
- Immersive Labs: Platform providing interactive cyber crisis simulations with real-time scoring
- Tabletop Scenarios (from NCSC UK): Exercise in a Box tool providing free guided tabletop exercises
- Ransomware Readiness Assessment (CISA): Self-assessment tool for evaluating ransomware preparedness
Common Scenarios
Scenario: Healthcare System Double Extortion Exercise
Context: A 5-hospital healthcare system conducts an annual ransomware tabletop. Previous exercise revealed gaps in HIPAA breach notification and clinical system recovery priority. This year's scenario simulates a double extortion attack targeting the EMR system.
Approach:
- Design scenario based on Cl0p MOO (Managed Operations Operator) TTPs: exploitation of MOVEit vulnerability for initial access, data exfiltration of 500,000 patient records, followed by encryption of EMR database servers
- Participants: CISO, CIO, CMO (Chief Medical Officer), General Counsel, VP Communications, Director of Clinical Operations, Privacy Officer, External IR firm representative
- Phase 1 inject: EMR system down, emergency department diverting patients to neighboring hospital
- Phase 2 inject: HHS OCR (Office for Civil Rights) contacts organization about reports of patient data on dark web
- Phase 3 inject: Attacker provides decryption key sample for $3.5M, 48-hour deadline
- Key finding: Organization lacks documented criteria for ransom payment decision and had not pre-identified an OFAC-compliant payment mechanism
- Remediation: Establish payment decision framework, pre-engage ransomware negotiation firm, update HIPAA breach notification procedures with specific timelines
Pitfalls:
- Designing unrealistic scenarios that do not reflect actual ransomware TTPs, reducing exercise credibility
- Allowing technical teams to dominate the exercise while business and legal participants remain passive
- Not testing the communication plan (many organizations discover their notification list is outdated during the actual incident)
- Failing to follow up on remediation actions identified in the AAR, negating the exercise value
Output Format
## Ransomware Tabletop Exercise - After Action Report
**Exercise Date**: [Date]
**Facilitator**: [Name]
**Scenario**: [Brief description]
**Duration**: [Hours]
**Participants**: [Count by department]
### Exercise Objectives
1. [Objective] - Met / Partially Met / Not Met
2. [Objective] - Met / Partially Met / Not Met
### Key Decisions Log
| Time | Decision Point | Decision Made | Rationale | Assessment |
|------|---------------|--------------|-----------|------------|
### Strengths Observed
1. [Strength]
### Gaps Identified
| Gap | Severity | Affected Area | Current State | Desired State |
|-----|----------|--------------|---------------|---------------|
### Remediation Actions
| Action | Owner | Deadline | Priority | Status |
|--------|-------|----------|----------|--------|
### Comparison to Previous Exercise
| Area | Previous Score | Current Score | Trend |
|------|---------------|--------------|-------|
1---
2name: performing-ransomware-tabletop-exercise
3description: 'Plans and facilitates tabletop exercises simulating ransomware incidents
4 to test organizational readiness, decision-making, and communication procedures.
5 Designs realistic scenarios based on current ransomware threat actors (LockBit,
6 ALPHV/BlackCat, Cl0p), injects covering double extortion, backup destruction, and
7 regulatory notification requirements. Evaluates participant responses against NIST
8 CSF and CISA guidelines. Activates for requests involving ransomware tabletop, incident
9 response exercise, or ransomware readiness drill.
10
11 '
12domain: cybersecurity
13subdomain: ransomware-defense
14tags:
15- ransomware
16- incident-response
17- tabletop-exercise
18- defense
19- preparedness
20version: 1.0.0
21author: mahipal
22license: Apache-2.0
23nist_csf:
24- PR.DS-11
25- RS.MA-01
26- RC.RP-01
27- PR.IR-01
28mitre_attack:
29- T1078
30- T1190
31- T1059
32- T1486
33- T1490
34source: https://github.com/mukul975/Anthropic-Cybersecurity-Skills
35source_commit: 04450304b12645cb2b974ab96d28c0664758a88d
36metadata:
37 source: https://skillmd.com/skills/yanacuti1121/performing-ransomware-tabletop-exercise
38---
39
40# Performing Ransomware Tabletop Exercise
41
42## When to Use
43
44- Testing organizational ransomware response procedures annually or after major infrastructure changes
45- Validating decision-making processes for ransom payment, regulatory notification, and public disclosure
46- Training executives, IT, legal, PR, and operations teams on their roles during a ransomware incident
47- Meeting cyber insurance policy requirements for documented incident response testing
48- Identifying gaps in recovery playbooks, communication plans, and backup procedures
49
50**Do not use** as a substitute for technical controls testing. Tabletop exercises validate procedures and decision-making, not technical detection or prevention capabilities.
51
52## Prerequisites
53
54- Documented incident response plan (IRP) that participants should have read before the exercise
55- Identified exercise participants from: executive leadership, IT/security, legal, communications/PR, HR, operations, and external counsel
56- Facilitator who is independent from the IR team (to provide objective evaluation)
57- Ransomware scenario designed with injects that escalate over multiple rounds
58- Evaluation criteria aligned to NIST CSF Respond/Recover functions
59- Conference room or virtual meeting for 2-4 hours with no interruptions
60
61## Workflow
62
63### Step 1: Design the Exercise Scenario
64
65Build a realistic scenario based on current threat actor TTPs:
66
67**Scenario Structure:**
68```
69Phase 1: Initial Detection (30 min)
70 - SOC receives alert for suspicious process execution on file server
71 - EDR detects Cobalt Strike beacon on 3 workstations
72 - Inject: External threat intel report links C2 IP to LockBit affiliate
73
74Phase 2: Escalation (30 min)
75 - Ransomware executes on 40% of servers during overnight hours
76 - Ransom note demands $2M in Bitcoin with 72-hour deadline
77 - Inject: Attackers contact media claiming data theft of customer PII
78
79Phase 3: Decision Points (45 min)
80 - Backup assessment reveals immutable copies are intact but primary backups encrypted
81 - Legal advises on breach notification timeline (72 hours GDPR, varies by US state)
82 - Inject: Threat actor publishes sample of stolen data on leak site
83
84Phase 4: Recovery and Communication (45 min)
85 - Recovery time estimate: 5-7 days from immutable backups
86 - Insurance carrier engages negotiation firm
87 - Inject: Major customer threatens contract termination without update within 24 hours
88```
89
90**Scenario Variables to Customize:**
91- Threat actor group and known TTPs
92- Percentage of infrastructure encrypted
93- Whether backups are intact, partially compromised, or fully destroyed
94- Type of data exfiltrated (PII, PHI, financial, trade secrets)
95- Applicable regulatory frameworks (GDPR, HIPAA, PCI DSS, SEC rules)
96- Ransom amount and payment deadline
97
98### Step 2: Prepare Exercise Materials
99
100Create the following documents for participants:
101
1021. **Exercise Overview Briefing** - Ground rules, objectives, scope, and participants
1032. **Situation Reports (SITREPs)** - One per phase, distributed as the exercise progresses
1043. **Inject Cards** - New information introduced at specific times to force decision-making
1054. **Decision Point Worksheets** - Structured forms for documenting group decisions
1065. **Evaluation Scorecard** - Criteria for assessing response quality
107
108**Key Decision Points to Include:**
109- When to activate the incident response team
110- Whether to shut down systems or contain selectively
111- Whether to engage law enforcement (FBI IC3, CISA)
112- Whether to pay the ransom and under what conditions
113- When and how to notify regulators, customers, and the public
114- How to prioritize system recovery order
115
116### Step 3: Facilitate the Exercise
117
118**Facilitator Responsibilities:**
119- Present each phase scenario and distribute SITREPs
120- Introduce injects at predetermined times to increase pressure
121- Ask probing questions to test decision-making reasoning
122- Ensure all participant groups contribute (prevent IT from dominating)
123- Document all decisions, rationales, and action items
124- Track time management (many teams lose time on early phases)
125
126**Probing Questions by Phase:**
127
128Phase 1 - Detection:
129- Who makes the call to declare an incident? What criteria trigger it?
130- How do we determine the scope of compromise from initial alerts?
131- Do we have the forensic capability to investigate or do we need external help?
132
133Phase 2 - Escalation:
134- What is our communication plan for employees? Do they know not to turn on affected machines?
135- Have we isolated the network to prevent further encryption?
136- Who authorizes system shutdowns that impact business operations?
137
138Phase 3 - Decision:
139- Under what conditions would we consider paying the ransom?
140- What are the legal obligations for notification at this point?
141- How do we handle the public leak of customer data?
142
143Phase 4 - Recovery:
144- What is the recovery priority order? Is it documented or decided ad hoc?
145- How long until critical business operations resume?
146- What evidence preservation is required for law enforcement and insurance?
147
148### Step 4: Evaluate and Score Responses
149
150Score each functional area against defined criteria:
151
152| Evaluation Area | Score (1-5) | Criteria |
153|----------------|-------------|----------|
154| Detection & Escalation | | Timely incident declaration, proper chain of command |
155| Containment | | Network isolation, credential reset, scope assessment |
156| Communication - Internal | | Employee notification, executive briefing, documented decisions |
157| Communication - External | | Regulatory notification, customer communication, media response |
158| Recovery Planning | | Backup verification, recovery priority, RTO tracking |
159| Legal & Compliance | | Breach notification timelines, evidence preservation, law enforcement engagement |
160| Business Continuity | | Manual operations, customer impact mitigation, revenue loss estimation |
161| Payment Decision | | Structured framework, legal review, OFAC sanctions check |
162
163### Step 5: Document Findings and Remediation Plan
164
165Produce an after-action report (AAR) within 5 business days:
166
167**AAR Contents:**
1681. Exercise overview and objectives
1692. Scenario summary and injects
1703. Key decisions made and rationale
1714. Strengths observed
1725. Gaps identified with severity rating
1736. Remediation actions with owners and deadlines
1747. Comparison to previous exercise results (if applicable)
175
176## Key Concepts
177
178| Term | Definition |
179|------|------------|
180| **Tabletop Exercise (TTX)** | Discussion-based exercise where participants walk through a simulated incident scenario to test plans and procedures |
181| **Inject** | New information introduced during the exercise to change the scenario and force additional decision-making |
182| **SITREP** | Situation Report providing current status of the simulated incident at each exercise phase |
183| **After-Action Report (AAR)** | Post-exercise document capturing findings, gaps, strengths, and remediation actions |
184| **Double Extortion** | Ransomware tactic where attackers both encrypt data and threaten to publish stolen data unless ransom is paid |
185| **OFAC Check** | Verification that ransom payment recipient is not on the US Treasury OFAC sanctions list, which would make payment illegal |
186
187## Tools & Systems
188
189- **CISA Tabletop Exercise Packages (CTEPs)**: Free scenario packages from CISA designed for critical infrastructure sectors
190- **FEMA Homeland Security Exercise and Evaluation Program (HSEEP)**: Methodology for designing, conducting, and evaluating exercises
191- **Immersive Labs**: Platform providing interactive cyber crisis simulations with real-time scoring
192- **Tabletop Scenarios (from NCSC UK)**: Exercise in a Box tool providing free guided tabletop exercises
193- **Ransomware Readiness Assessment (CISA)**: Self-assessment tool for evaluating ransomware preparedness
194
195## Common Scenarios
196
197### Scenario: Healthcare System Double Extortion Exercise
198
199**Context**: A 5-hospital healthcare system conducts an annual ransomware tabletop. Previous exercise revealed gaps in HIPAA breach notification and clinical system recovery priority. This year's scenario simulates a double extortion attack targeting the EMR system.
200
201**Approach**:
2021. Design scenario based on Cl0p MOO (Managed Operations Operator) TTPs: exploitation of MOVEit vulnerability for initial access, data exfiltration of 500,000 patient records, followed by encryption of EMR database servers
2032. Participants: CISO, CIO, CMO (Chief Medical Officer), General Counsel, VP Communications, Director of Clinical Operations, Privacy Officer, External IR firm representative
2043. Phase 1 inject: EMR system down, emergency department diverting patients to neighboring hospital
2054. Phase 2 inject: HHS OCR (Office for Civil Rights) contacts organization about reports of patient data on dark web
2065. Phase 3 inject: Attacker provides decryption key sample for $3.5M, 48-hour deadline
2076. Key finding: Organization lacks documented criteria for ransom payment decision and had not pre-identified an OFAC-compliant payment mechanism
2087. Remediation: Establish payment decision framework, pre-engage ransomware negotiation firm, update HIPAA breach notification procedures with specific timelines
209
210**Pitfalls**:
211- Designing unrealistic scenarios that do not reflect actual ransomware TTPs, reducing exercise credibility
212- Allowing technical teams to dominate the exercise while business and legal participants remain passive
213- Not testing the communication plan (many organizations discover their notification list is outdated during the actual incident)
214- Failing to follow up on remediation actions identified in the AAR, negating the exercise value
215
216## Output Format
217
218```
219## Ransomware Tabletop Exercise - After Action Report
220
221**Exercise Date**: [Date]
222**Facilitator**: [Name]
223**Scenario**: [Brief description]
224**Duration**: [Hours]
225**Participants**: [Count by department]
226
227### Exercise Objectives
2281. [Objective] - Met / Partially Met / Not Met
2292. [Objective] - Met / Partially Met / Not Met
230
231### Key Decisions Log
232| Time | Decision Point | Decision Made | Rationale | Assessment |
233|------|---------------|--------------|-----------|------------|
234
235### Strengths Observed
2361. [Strength]
237
238### Gaps Identified
239| Gap | Severity | Affected Area | Current State | Desired State |
240|-----|----------|--------------|---------------|---------------|
241
242### Remediation Actions
243| Action | Owner | Deadline | Priority | Status |
244|--------|-------|----------|----------|--------|
245
246### Comparison to Previous Exercise
247| Area | Previous Score | Current Score | Trend |
248|------|---------------|--------------|-------|
249```