← Back to blog

Ransomware Tabletop Exercise: A Small Business Guide

November 15, 2026
Ransomware Tabletop Exercise: A Small Business Guide

A ransomware tabletop exercise is a facilitated discussion in which your owner, office manager and IT contact talk through a scripted ransomware attack, step by step, using your real plans. Nothing is shut down and no software is touched. You find out in a conference room, not during an actual attack, who decides what, where the backups are and whether anyone knows who to call. For a small business, a first session fits in an afternoon and needs a scenario, six or so people, a note taker and a written follow-up list.

This guide walks you through the whole process for an Oklahoma small business: law firm, dental or medical practice, accounting office, manufacturer or nonprofit. It uses free government material wherever it exists, and it shows where the exercise usually breaks down, which is the part that matters.

Greatplainsnetworking
Prepare Your Business for IT Disruptions
Great Plains Networking helps small businesses protect operations with proactive IT support, cybersecurity, and rapid data recovery.
Visit

Key Takeaways

  • A tabletop exercise is a discussion, not a simulation: CISA describes it as a facilitated talk-through of a scripted scenario in an informal, stress-free setting.
  • Small businesses can finish a complete exercise in two to three hours, and CISA says even a 10-minute discussion at the start of a staff meeting counts.
  • Include the people who make business decisions (shutdown, client notification, payment questions), not only IT.
  • Test your backups on paper first: where they live, whether ransomware could reach them, how long a restore takes and which systems come back first.
  • The exercise is only worth the time if every gap leaves the room with an owner and a deadline.

Table of Contents

What a ransomware tabletop exercise is (and is not)

CISA, the U.S. Cybersecurity and Infrastructure Security Agency, defines a tabletop exercise as a facilitated discussion of a scripted scenario, based on your current policies, plans and procedures. It focuses on the roles people play rather than on simulating the attack, and no equipment or resources are deployed.

In practice, someone reads out a development: "At 7:40 a.m. the front desk reports that files on the shared drive will not open and a text file on the desktop demands payment." Then the group answers, in order: Who do we tell? What do we unplug? Can we still see patients, bill clients or run the production line? Who talks to customers?

Four decisions in a ransomware tabletop exercise

It is not a penetration test, which probes your systems for weaknesses, and it is not a technical drill where IT restores servers. It tests people, decisions and paperwork. That is why it suits a business with a small team: the failures in a real ransomware incident are rarely exotic. They are usually that nobody knew who was in charge, the phone list was on the encrypted server, or the backup could not be restored as quickly as everyone assumed.

CISA's tabletop tips say players usually take their own roles (CEO, IT lead, communications) and that the goal is not flawless performance. The goal is to work as a team and find problem areas in peacetime, because there is no chance to align the team in the middle of a crisis.

Who needs to be in the room

Ransomware is a business crisis before it is an IT problem. The people who decide on shutting down operations, notifying clients or patients, speaking to the press and handling a payment demand must be present. CISA's handbook says players should be chosen to represent their discipline and, ideally, have the authority to speak for the people they represent.

For a business with 10 to 50 employees, a workable group looks like this:

RoleWho usually fills itWhat they practice
FacilitatorSomeone who knows the plan but will not play a part (an office manager, or an outside colleague)Reads each update, keeps discussion moving, asks follow-up questions
Decision makerOwner, managing partner, practice owner or executive directorShutdown, client notification, spending, payment questions
IT leadYour internal IT person or the provider who supports youContainment options, what evidence to preserve, restore times
Operations leadOffice or practice managerWhich work can continue manually, how to tell staff
Compliance or privacy contactPractice compliance officer, attorney, bookkeeperNotification duties for client, patient or financial data
Note takerAnyone organizedRecords every decision, who made it and what it was based on

In a very small office one person may hold several roles. The point, as CISA's handbook makes clear for facilitators and evaluators, is that each responsibility has a named owner and someone keeps an accurate written record of actions and decisions.

CISA's tips also recommend that everyone gets a chance to participate, with no spectators. The facilitator can call on people for an assessment even if the scenario does not formally include them. A receptionist who first sees the ransom note has a view you want to hear.

Set one clear goal before you pick a scenario

A tabletop with no stated purpose turns into a general chat about security. Pick one business service that would hurt to lose (client billing, patient scheduling, case management, order processing) and decide what the group should demonstrate. A sensible list for a first session:

  1. Recognize that an incident is happening and report it to the right person.
  2. Find the right contacts quickly, including after-hours numbers for your IT provider, insurer and attorney.
  3. Decide who can authorize containment, such as disconnecting machines or disabling accounts.
  4. Coordinate communications to staff, clients and regulators.
  5. Set recovery priorities: which systems come back first and why.

If your IT or disaster recovery plan is more than a page in a drawer, ask the group to bring it and use it. The exercise is meant to test those documents. If you have no written plan yet, the exercise will show you exactly what the plan must contain, and our guide to incident response plan steps gives you a structure to start from.

Choose a realistic scenario

You do not have to write one from scratch. CISA's Tabletop Exercise Packages are free, customizable and include template objectives, scenarios and discussion questions. Ransomware is among the scenarios, alongside insider threats, natural disasters and others. The package materials include planner, facilitator and participant templates, an invitation letter, a slide deck, a feedback form and an after-action report template, according to CISA's CTEP fact sheet.

If you want a ready kit written for smaller firms, Nacha's ransomware tabletop kit is designed for small to medium-sized U.S. businesses to complete in two to three hours. It includes a leader's guide, an evolving scenario, a participant workbook and a discussion guide. For a technology-focused walk-through of scenario design, this ransomware tabletop exercise guide is also worth reading before you plan.

Whatever template you use, adapt it to your business. A dental practice should include patient records and an imaging system. A law firm should include client files and privileged email. A manufacturer should include the machines and scheduling software that depend on the network. A nonprofit should include donor data and grant deadlines.

Build in data theft, not just locked files

Many attacks no longer stop at encrypting files. Attackers often steal data first and then threaten to publish it. A scenario that only says "files are encrypted, restore from backup" lets everyone off too easily. Add a later update: the attacker emails a sample of your client or patient data and sets a deadline. Now the group must consider notification duties, which are different for HIPAA-covered practices than for a manufacturer, and whether restoring from backup solves the whole problem. It does not, because stolen data stays stolen.

Use evolving updates (injects)

An inject is a fictional update that arrives mid-exercise and forces a decision. Write five or six before the session, each requiring a choice. For example:

  1. 7:40 a.m.: Two staff cannot open files. A text file on a desktop demands payment.
  2. 8:15 a.m.: The note says all data will be published in 72 hours unless contacted.
  3. 9:00 a.m.: A client calls asking why they cannot reach their documents.
  4. 10:30 a.m.: Your IT contact reports the most recent backup on the main server is also encrypted. An older copy exists but has not been restored in more than a year.
  5. 1:00 p.m.: A local reporter asks whether the business has been hacked.
  6. Next morning: Your insurer asks for a timeline and a list of affected systems.

Keep a facilitator's version that explains what discussion each update should provoke and what facts the players may ask for, such as which systems are affected or when the last good backup ran. CISA's tips add that facilitators can present facts that look harmless but later signal something serious, and can offer contradictory information or distractions, as real incidents do.

Questions that test the decisions that matter

The NMFTA's facilitator handbook structures a ransomware exercise in three sessions: early warning signs and preventive measures, a fast-escalating incident that affects operational servers, continuity and communications, and finally remediation and rebuilding customer confidence. That arc works for any small business. Here are the questions to put under each stage.

Detection and containment

  • Who is the first person staff should call, and is that number written down somewhere not stored on the affected systems?
  • Who has the authority to pull machines off the network or shut down a server at 2 a.m.?
  • Do we know which accounts to disable, and does anyone have the access to do it?
  • What do we keep untouched so the incident can be investigated?

Backups and recovery

This is where small businesses most often discover a gap. Ask the group:

  • Where are the backups, and could an attacker with an administrator account reach them?
  • When was the last full restore tested, not just a backup job reported as successful?
  • How long would restoring the main systems really take, in hours or days?
  • Which systems come back first, and does everyone agree on that order?

If the answers are guesses, you have found your first improvement item. Our guides on backup restore testing and immutable backups explain what verified recovery looks like, and the ransomware recovery plan playbook covers what happens after the exercise reveals a weak spot.

Business continuity

  • Can we still serve clients, patients or customers on paper, by phone or with a temporary setup, and for how long?
  • If email is down, how do we reach staff and clients? Is there an out-of-band option such as personal phones or a messaging tool that does not run on your network?
  • Who covers payroll and invoicing if the accounting system is offline?

Communications and reporting

  • Who speaks to staff, clients, the insurer, an attorney and, where it applies, regulators?
  • Which regulations apply to the data we hold? Healthcare practices, law firms handling sensitive records and defense suppliers all have different obligations.
  • Who decides how to respond to a payment demand, and what information do they need first?

The last question deserves care. Payment decisions involve legal, insurance and law enforcement considerations, so your exercise should confirm who you would call and in what order, not settle the answer on the spot.

How to run the session

  1. Do a trial run. Walk through the scenario with a small core group first, as ransomware.org's exercise guide advises, then expand to the full group.
  2. Send materials ahead. Ask participants to read your incident response plan and bring it. A real-world example published in 2022 required every participant to be familiar with the company's plan beforehand.
  3. Set ground rules. It is not a test and nobody is graded. The point is to find gaps.
  4. Read the first update and ask what happens next. Let people think out loud and ask clarifying questions of each other, as CISA's tips encourage.
  5. Call on quiet participants. The facilitator guides players toward sound decisions and decides who receives each problem statement.
  6. Record everything. Use a shared document that everyone can edit so notes build in real time, which CISA also recommends. Capture each decision, who made it, what it was based on and what nobody could answer.
  7. Finish with a short debrief. Ask what worked, what surprised people and which phrase came up most often. "No one is really in charge of that here" is a finding, not an embarrassment.

TechTarget's sample ransomware scenario assumes a firm with a documented breach response plan and notes that people outside IT can serve as observers who comment for the after-action report. That is a useful way to include a part-time staff member or board member without overloading the table.

Keep it as small as it needs to be

CISA says tabletop exercises do not have to be large productions. A scaled-down 10-minute discussion at the start of a staff meeting works: "It is Monday and the shared drive is encrypted. Who do you call first?" Run those between full sessions and your team will build the habit.

Turn findings into an after-action report

An exercise without written follow-up is a pleasant meeting. The after-action report (AAR) records what you set out to test, what happened, strengths, and gaps. The improvement plan (IP) turns each gap into a task. CISA's handbook sets a timeline that scales down well: a draft AAR and IP within three to four weeks, a meeting about five to six weeks afterward to agree strengths, improvements, corrective actions, deadlines and owners, and final distribution within two weeks of that meeting. A small business can compress it, but keep the order: report, agree, assign, finish.

For each gap, write three things: the fix, the person responsible and the date. Typical small-business findings include:

  • Logging or threat-detection features that were paid for but never switched on.
  • A communications plan that assumes email and the main chat tool will still work.
  • Critical knowledge held by one or two people and written down nowhere.
  • A backup that has never been restored in full.
  • No current list of after-hours contacts for the insurer, attorney and IT support.

Breach Craft's published case study of an insurance carrier's exercise found those first three gaps, each with a documented remediation, owner and timeline. The lesson applies to any size of business. The gaps that hurt are mundane.

The weak point of most exercise programs is follow-through. As LegalClarity's guide puts it, organizations that never act on the improvement plan simply document the same gaps year after year. Put a review of open items on the agenda of a monthly or quarterly management meeting, and update the incident response plan before the next exercise.

How often to repeat it

A yearly full session is a sensible rhythm for most small businesses, with short discussion drills in between. Repeat sooner after a major change: a new line-of-business application, a move to cloud email, a new office, staff turnover in the owner or IT roles, or a change of IT provider. Each time, change the scenario so you are not rehearsing the same answers: vary the entry point (a phishing email, a stolen password, a compromised vendor), the systems hit and the pressure points.

Where we fit in

A tabletop exercise exposes what must be fixed; the fixes themselves are technical and ongoing. Great Plains Networking provides managed IT support for small businesses in Norman, Moore and Oklahoma City, including 24/7 monitoring, cybersecurity, and backup and recovery, with same-day response and no long-term contracts. We explain it in plain language, so the gaps your exercise uncovers come with clear next steps instead of jargon.

Greatplainsnetworking

If your exercise raised questions about backups, access or monitoring, start with the 10-minute readiness audit or the free network assessment. Both are free. Our managed IT support covers the day-to-day work of closing the gaps and keeping them closed.

FAQ

How long does a ransomware tabletop exercise take?

A complete exercise for a small business typically takes two to three hours; Nacha designed its kit for that window. A short version at the start of a staff meeting can take 10 minutes, which CISA describes as an acceptable scaled-down option.

Do we need an outside expert to run one?

No. CISA's free exercise packages include planner, facilitator and participant templates, so your team can build and run its own. What matters is that the facilitator is not also a key player, so they can focus on guiding discussion and keeping time.

Who should attend from a small business?

Include the owner or managing partner, whoever handles IT, your office or operations manager, and anyone responsible for compliance or client data. Add a note taker. One person can fill more than one role, as long as every responsibility has a named owner.

What should we do with the results?

Write an after-action report and an improvement plan with a fix, an owner and a deadline for every gap. CISA's handbook suggests a draft within three to four weeks and a review meeting about five to six weeks after the exercise. Update your incident response plan before you run the next one.

Sources