Ransomware Tabletop Exercise: A Healthcare Crisis Scenario

One hospital, one day, one clock. A ransomware exercise walked hour by hour, from the overnight alert to the published sample, and the four decisions the room discovers it has no owner for.

A fractured barrier interrupting a geometric network with alternate recovery paths, illustrating ransomware crisis response.

Key Takeaways

  • A ransomware tabletop should test encryption scope, possible exfiltration, payment authority, and operational continuity.

  • The payment question tests whether counsel, insurers, executives, and board members can make an authorized decision within the available time.

  • HIPAA makes contingency-plan testing addressable but does not prescribe a testing frequency.

  • One continuous exercise clock reveals how delays and dependencies affect later decisions.

  • Programs can rotate encrypt-only, exfiltration, managed-service-provider, and post-payment scenarios across the year.

At 02:14, endpoint monitoring flags mass file writes on a health system's imaging archive. By 02:40 the on-call analyst is reading a ransom note on a shared drive. By 06:40 the night shift is charting on paper, and nobody has yet asked who is allowed to answer the attacker. A ransomware tabletop exercise rehearses that night.

A ransomware tabletop exercise is a discussion-based rehearsal of a simulated ransomware incident. It tests encryption scope, possible exfiltration, communication with the actor, payment authority, and operational continuity.

This article follows one hospital through one day, stopping at each decision as the adversary’s clock continues to run.

What Is a Ransomware Tabletop Exercise?

The instrument is the same as any other tabletop: a facilitator, a scenario, a room of people who own something, and a clock. The decision set is not.

Ransomware can force an organization to communicate with an adversary while operations remain disrupted. That pressure changes the exercise. A data-breach tabletop tests detection, escalation, and disclosure. A ransomware tabletop adds an actor who may understand the organization’s operations, estimate its downtime costs, and set a deadline.

Four decision families carry the weight, and this article walks all four: encryption scope and blast radius, exfiltration and extortion, the payment decision and its authority chain, and operational continuity, which in a hospital means clinical continuity.

Healthcare makes the gap between planning and execution unusually visible. A delayed decision can affect clinical care before the organization understands the incident’s full scope.

The HIPAA Security Rule places contingency planning within its administrative safeguards. Data backup, disaster recovery, and emergency-mode operation plans are required implementation specifications. Periodic testing and revision procedures are addressable.

Addressable does not mean optional. Under 45 CFR 164.306(d)(3), regulated entities must assess whether the specification is reasonable and appropriate. An entity that chooses another approach must document its reasoning and implement an equivalent alternative when reasonable.

HIPAA does not prescribe a testing frequency. That flexibility makes exercise cadence an organizational risk decision.

What a Ransomware Tabletop Exercise Should Actually Test

Build the exercise as a decision inventory. Each question needs a deadline and a named decision owner.

Encryption Scope and Blast Radius

What is encrypted, unreachable, or still trustworthy? Those states require different responses. The exercise should identify who can declare a system clean.

Backup Confidence

Someone may propose restoring from backup within the first hour. The exercise should ask when the last restore test occurred and who verified it. Restore sequencing and dependency order belong in Disaster Recovery Tabletop Exercise: A Practical Guide for 2026.

Exfiltration and Extortion

Did data leave, and what evidence supports that conclusion? A published sample should change the legal and communications response.

Payment Authority

Who owns the payment decision, and who must be consulted? That group may include external counsel, the insurer, executives, and the board. The exercise should also test who performs sanctions screening and how long that process takes.

Clinical Continuity

Which services continue, operate in degraded mode, or stop? Clinical leaders should own these decisions rather than the security team.

Notification Obligations

HHS ransomware guidance states that ransomware affecting ePHI can create a presumed breach. The entity must demonstrate a low probability of compromise to rebut that presumption.

The exercise should identify who conducts the four-factor assessment and what evidence is available. The exercise does not need to settle every decision. It needs to reveal who has the authority to make each one.

How to Build a Ransomware Tabletop Exercise Scenario

Fix five parameters before the exercise. Other conditions may change, but these boundaries should remain stable.

1. Define the Encryption Footprint

Name the affected and unaffected systems. A generic statement that the network is encrypted gives the team nothing specific to evaluate.

For a hospital, the list may include electronic health records, imaging, pharmacy dispensing, laboratory systems, badge access, and surgical scheduling. The scenario should state which systems the actor reached.

2. Set the Actor’s Posture

Encrypt-only, double-extortion, and exfiltration-only incidents create different decisions. Exfiltration without encryption can be especially difficult because operations appear normal while legal pressure grows.

3. Set the Deadline and Inject Cadence

The actor’s deadline should expire inside the exercise window. A later deadline allows the team to discuss options without making a decision.

Reflex scenarios place the countdown inside the session so delays affect what happens next. The mechanics of injects and escalation are worth reviewing before drafting the exercise timeline.

4. Cast Internal and External Roles

Internal roles may include security, legal, communications, executives, and board representatives. External roles may include counsel, insurers, regulators, journalists, customers, the threat actor, and a negotiating counterpart.

5. Define the Stopping Rules

The exercise should continue after participants propose restoring from backup. That decision should introduce questions about restore integrity, dependencies, and operational priorities.

For branching logic and adversary modeling, use Cybersecurity Tabletop Exercises: Scenarios & Examples for 2026.

Healthcare Scenario: Ransomware Takes a Hospital’s Critical Systems Offline

This walkthrough follows a regional health system with 412 licensed beds across three campuses. All three share one electronic health record instance. Its dependent systems are the imaging archive, pharmacy dispensing, the lab information system, badge access, and surgical scheduling. Every number below is a stated exercise parameter, chosen to force a decision. None of it is a finding about real incidents.

02:14. Endpoint monitoring flags mass file writes on the imaging archive. 200 studies scheduled before noon now sit behind encrypted volumes. Who is authorized to take the imaging network offline at 2 a.m., and can that person be reached in under 15 minutes?

The room decides to isolate. It defers the question of who had the authority to decide that, and the facilitator writes the deferral down.

04:30. Pharmacy dispensing is unreachable and the security team believes clean snapshots exist. The last verified restore test has no date attached to it. Dispensing moves to manual override at 06:00 if nothing changes. Who signs off that the backups are clean, and on what evidence?

Nobody signs. The room proceeds as though someone had.

06:40. The EHR goes offline. The emergency department has 12 patients requiring medication reconciliation within the hour. Which fallback procedure begins, and who authorizes it?

This is the beat where the incident stops belonging to security. The night charge nurse has been running paper for 4 hours and the day shift arrives without a briefing.

08:15. The lab information system is offline and results move between floors on paper. Turnaround on a stat troponin has gone from 45 minutes to unmeasured. Who tells the emergency attending that the result will not arrive, and who decides whether the patient transfers?

10:20. A contact note arrives at the general counsel's published address, with a sample directory listing and a 72-hour deadline. The address is public, so 4 people have already read it. Who is permitted to reply, and does anyone in the room know that answer without looking it up?

At this point, the clinical questions have found owners. The question of who may contact the actor remains unresolved.

14:05. The actor posts a countdown page naming the health system and one patient's chart. A local reporter calls the main switchboard within 40 minutes. Who speaks first, and has anyone told that patient's care team before the story runs?

Six beats, one clock, and the pattern is already visible: the room knows what to do and cannot say who does it.

Testing Clinical, Security, Legal & Executive Decisions Under Pressure

Same hospital, same day, later hours. This section cuts the timeline by role.

15:40. Two campuses are on ambulance diversion and the third is holding. Regional EMS wants a duration estimate before the next shift change. Who owns that estimate, and what happens when it turns out to be wrong by 6 hours?

Diversion is a clinical decision with an operational trigger. The sector’s Health Industry Cybersecurity Practices treats ransomware as a patient-safety threat rather than only a data event. Its ransomware guidance encourages organizations to develop recovery playbooks and test their readiness through tabletop exercises.

17:15. Legal wants the insurer notified before any reply goes to the actor. The insurer's after-hours line routes to a broker who is not on the policy. The board chair is on a flight. Who authorizes contact with the actor when the two people who must be consulted cannot be reached?

This is the exercise's sharpest moment, and it is entirely about sequence. A no-payment policy establishes the destination. It does not establish who has authority to act when clinical consequences turn that rule into a difficult choice.

19:30. The privacy officer is drafting a regulator notification while communications drafts a holding statement for the reporter. Neither function has read the other's draft. Who confirms that the organization is saying one thing, and by when?

The following matrix is illustrative. Actual ownership should follow the hospital’s governance model, policies, and applicable law.

Decision

Who owns it

Consulted first

The clock

Take a clinical system offline

Incident commander, with CMO concurrence

Nursing leadership on the affected unit

Minutes

Ambulance diversion

Chief medical officer or on-call medical director

Regional EMS, receiving facilities

Under 1 hour

Authorize ward downtime procedures

Nursing leadership, per campus

Pharmacy, lab, medical staff office

Immediate, then each shift

Open a channel with the actor

General counsel

External counsel, cyber insurer

Before any reply leaves

Discuss payment

CEO, with board notified

External counsel, insurer, sanctions screening

Hours, not minutes

Speak to the regulator

Privacy officer

General counsel

Per the notification rule

Speak to the press

Communications lead

General counsel, CEO

Before the first call is returned

Completing the matrix can expose gaps before the exercise begins. Most teams can name the required actions but struggle to assign final authority.

An adaptive exercise then tests whether those assignments hold under pressure. An exercise with no failure condition may never force the team to resolve an unowned decision.

Ransomware Tabletop Exercise Template & Lessons Learned

A ransomware tabletop exercise template is a capture format, not a script. A well-designed tabletop ransomware exercise should capture six things:

  1. Scenario brief. The organization, its dependent systems, and the state of the world at hour zero. Two paragraphs, no more.

  2. Encryption and exfiltration parameters. What the actor reached, what the actor took, and what the organization can prove either way.

  3. Inject timeline with the actor's clock. Each inject timestamped, each one ending on a question that names an owner.

  4. Decision log. Timestamp, decision, named owner, and a column for what was deferred. The deferral column is the one that matters.

  5. Decision-rights matrix. The table above, filled in before the exercise and corrected during it.

  6. After-action findings format. Behaviors observed, mapped to the decision families, with owners and dates attached.

The fillable artifacts will appear in the Tabletop Exercise Template Toolkit: 6 Templates for Security Teams. The findings below describe observed behavior rather than general advice.

The clinical actions happened fast and the authority questions never closed. The room isolated the imaging network at 02:14 and deferred who was entitled to order it. Who could reply to the actor was still open at 14:05.

The room asserted backup confidence at 04:30 and never evidenced it. Nobody asked for the date of the last verified restore until the facilitator did, and by then two hours of planning rested on it.

Counsel arrived late and immediately became a bottleneck. Nobody reached external counsel until 10:20, after which every decision routed through one person on one phone. Two functions spoke for the organization without a shared draft. The privacy officer and the communications lead drafted in parallel and never compared language.

The following ransomware tabletop exercise examples preserve the decision set while changing the pressure:

  • Encrypt-only with verified backups: Removes the recovery question and isolates the extortion decision.

  • Exfiltration without encryption: Leaves operations intact while legal and communications pressure grows.

  • Compromised managed service provider: Places a contract between the organization and crucial evidence.

  • Second demand after payment: Tests whether the original payment position can withstand further pressure.

Programs can rotate these four ransomware tabletop exercise scenarios across the year instead of choosing only one.

From Scripted Ransomware Exercises to Live Crisis Simulation With Reflex Security

The 10:20 inject shows the limit of a scripted exercise. The room discusses who might reply before the facilitator presents the next card. The actor never receives that response, so the scenario cannot reveal the consequences of the team’s decision.

Reflex Security runs a crisis simulation that places adaptive pressure on the other side of the conversation.

Make the Actor Respond

The Adaptive Adversary Engine reacts to participant decisions. When the room delays opening a channel, the actor can escalate. When participants commit to a position, the actor can test it.

One-Click Scenario Generation produces five customized scenarios from a company domain in 10 to 15 minutes. The scenarios draw on public information that an attacker could use during reconnaissance. Each exercise runs for 60 to 120 minutes.

Keep Pressure on Deferred Decisions

An AI facilitator named Victoria joins the video call and challenges unresolved decisions. Victoria can lead the session, or a human facilitator can use the generated Facilitator Guide.

The guide includes company background, discussion questions, and gaps to watch during the exercise.

Replace Assumptions With Evidence

The Investigation Console gives participants simulated artifacts to investigate. This evidence allows the team to evaluate encryption scope instead of relying only on assumptions.

The After Action Report reconstructs the exercise minute by minute and uses participant quotes as evidence. Reflex reports typically exceed 54 pages. Reflex explains the underlying mechanics in adaptive scenario generation.

The simulation does not replace decision-rights planning. Teams should complete the matrix and identify missing owners before testing those decisions against an adaptive adversary.

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

How long should a ransomware tabletop exercise run?

The actor’s deadline should expire inside the session. A full walkthrough may take two to three hours, while a platform exercise typically runs 60 to 120 minutes. A 45-minute session may reach encryption scope but leave later decisions untested.

Should the exercise include a simulated negotiation with the threat actor?

The exercise should include the communication channel, not a detailed commercial negotiation. It should test who may reply, who must be consulted, and how long that consultation takes. Most organizations retain specialists to conduct the negotiation rather than practicing it internally.

Can the exercise run before the organization has a payment position?

Yes, and the absence is worth surfacing. An exercise that discovers nobody can say who states the position has produced its most useful finding. What it should not do is let the room invent a policy under pressure and then file the invention as though it were governance.

Should the board take part in a ransomware tabletop exercise?

The board chair or audit committee can join a 30-minute escalation segment instead of the full session. The exercise should test whether they are reachable and can resolve questions of authority. Requiring the board to attend hours of operational discussion may discourage future participation.

Does cyber insurance require a ransomware tabletop exercise?

Policies and applications vary. Some carriers ask about incident response testing at renewal, while others do not. Organizations should confirm the requirement with their broker. A dated record with named participants and assigned actions provides stronger evidence than a description of intent.

Are free ransomware exercise packages good enough?

For a first run, frequently yes. CISA publishes free tabletop packages, and the HHS 405(d) material gives healthcare a ransomware threat profile to build from. Both are credible and cost nothing. Where they stop is the adversary: a package cannot answer a reply, which is why the payment beat reads as a discussion.

References

U.S. Department of Health and Human Services 405(d) Program, & Healthcare and Public Health Sector Coordinating Council. (2023). Health industry cybersecurity practices: Managing threats and protecting patients (2023 ed.). 405(d) Aligning Health Care Industry Security Approaches. https://405d.hhs.gov/Documents/HICP-Main-508.pdf

U.S. Department of Health and Human Services, Office for Civil Rights. (2016, July). Fact sheet: Ransomware and HIPAA. HHS.gov. https://www.hhs.gov/hipaa/for-professionals/security/guidance/cybersecurity/ransomware-fact-sheet/index.html (Content last reviewed September 20, 2021.)

U.S. Office of the Federal Register. (n.d.). Administrative safeguards (45 CFR § 164.308). Electronic Code of Federal Regulations. Retrieved September 10, 2026, from https://www.ecfr.gov/current/title-45/section-164.308

U.S. Office of the Federal Register. (n.d.). Security standards: General rules (45 CFR § 164.306). Electronic Code of Federal Regulations. Retrieved September 10, 2026, from https://www.ecfr.gov/current/title-45/section-164.306

Cite this article

Marlow Bryant.

Ransomware Tabletop Exercise: A Healthcare Crisis Scenario.

Reflex Security.

https://reflexsecurity.com/guides/ransomware-tabletop-exercise

Incident closed // after-action ready

Incident closed

See what your team does

under real pressure.

True cyber crisis readiness isn't built in a slide deck—it's forged in the trenches. Every team believes it’s ready. The simulation is where you find out. Sixty minutes, your real environment, no slides.

Book A demo

ReflexSecurity

AI-powered incident-response simulation platform.

AI-powered incident-response simulation platform.

© 2026 Reflex Security. All rights reserved.