Many ransomware tabletop exercises spend their four hours on the technical story: the phishing email, the encrypted file shares, the ransom note. A federal system has a second story: who reports what, to whom, by when, and who is allowed to decide that a system can come back online. A ransomware tabletop exercise can test both if it starts from a CISA package, adds injects tied to your reporting clauses and ends with an improvement plan that has owners and dates.
What a ransomware tabletop exercise is, and what it isn't
A tabletop exercise (TTX) is, in the words of CISA's planner handbook, "a facilitated discussion of a scripted scenario in an informal, stress-free environment." The people who would respond to a real attack talk through what they would do as a facilitator releases new information. NIST SP 800-84 adds the limit that matters: a tabletop "is discussion-based only and does not involve deploying equipment or other resources."
A tabletop finds gaps in decisions, authority and communication cheaply. It does not prove that backups restore or that a network can be segmented in an hour. Those need a functional exercise, which 800-84 describes as people performing their duties "in a simulated operational environment."
Why federal programs run them
NIST SP 800-53 gives federal systems a written basis for testing incident response. Control IR-3 asks organizations to "test the effectiveness of the incident response capability" at a frequency and with tests the organization defines, and IR-3(2) asks that testing be coordinated with related plans. CP-4 does the same for the contingency plan and adds two steps: review the results and "initiate corrective actions, if needed." IR-8(c) then asks for the incident response plan to be updated for problems found during testing.
Contractors whose contracts include DFARS 252.204-7012 implement NIST SP 800-171, and requirement 3.6.3 in Rev. 2 says the same thing: "Test the organizational incident response capability." Its discussion names "walk-through or tabletop exercises" among the ways to do it. DoD's continuous ATO criteria also list periodic tabletop exercises with after-action reports as team evidence, which we covered in what DoD checks before granting a continuous ATO.
Ransomware is a sensible scenario because it touches every part of the plan at once. NIST IR 8374r1, the June 2026 ransomware profile for the Cybersecurity Framework 2.0, says ransomware response and recovery plans "should be tested periodically to ensure that risk and response assumptions and processes are current with respect to evolving ransomware threats."
How much planning a ransomware tabletop exercise needs
CISA's Tabletop Exercise Packages (CTEPs) do most of the scenario writing. CISA describes them as customizable packages with "template exercise objectives, scenarios, discussion questions, and resources," and ransomware is one of the cyber topics. Each package includes a situation manual, a facilitator and evaluator handbook, a slide deck template, feedback forms and an After Action Report and Improvement Plan (AAR/IP) template, and CISA builds them on FEMA's Homeland Security Exercise and Evaluation Program (HSEEP) method.
The package still needs to be fitted to your system, and the handbook's timeline is long:
| When | Step in CISA's planner handbook |
|---|---|
| 3 months before | Concept and objectives meeting |
| 2.5 months before | Initial planning meeting |
| 6 to 8 weeks before | Midterm planning meeting |
| 5 to 7 weeks before | Send invitations |
| 2 weeks before | Final planning meeting |
| Exercise day | About four hours of play, then a hot wash |
| 3 to 4 weeks after | Draft the AAR/IP |
| 5 to 6 weeks after | After-action meeting |
| Within 2 weeks of that meeting | Finalize and distribute the AAR/IP |
The four hours come from the templates; the handbook says the length "is ultimately at your discretion." Most of the three months goes to getting the right people on the calendar and agreeing on objectives.
Who needs to be in the room
The handbook defines the roles: facilitators "provide situation updates and moderate discussions," evaluators document player discussions, including whether they conform to plans, policies and procedures, players describe their response, and observers generally don't take part directly. The handbook adds that players should have authority to speak for their organization. Add a dedicated note taker so the facilitator can run the room.
Players should be the people who would decide things for real: the incident response lead, the system owner, the Information System Security Officer (ISSO), network and backup administrators, legal counsel, public affairs, and the official who would accept the risk of restoring service. For a contractor-operated system, add the contract's program manager and whoever would file the DoD report. If the person who holds the reporting credential isn't there, the exercise can't test the report.
Injects that test federal requirements
An inject is a piece of new information the facilitator releases to force a decision. The CISA scenario supplies the attack. These injects, each tied to a written requirement, supply the federal second story:
| Inject | What it tests | Where the requirement comes from |
|---|---|---|
| Email and chat are down | Out-of-band communications and current contact lists, including law enforcement and counsel | NIST IR 8374r1 |
| Backups exist, but were they touched? | Who verifies backup integrity before restoration | NIST IR 8374r1, RC.RP-03 |
| Encryption reaches a system that holds covered defense information | Whether the team recognizes a reportable cyber incident and files with DoD within 72 hours of discovery at dibnet.dod.mil, with a DoD-approved medium assurance certificate | DFARS 252.204-7012(c) |
| A malware sample is isolated | Submitting it to the DoD Cyber Crime Center (DC3), not to the contracting officer | DFARS 252.204-7012(d) |
| The team wants to rebuild the servers | Preserving images and packet capture for at least 90 days from the report | DFARS 252.204-7012(e) |
| The system owner wants it back online | Who has authority to approve restoration, and whether the plans say so | The IR plan's designated responsibility (IR-8(a)(10)) and the contingency plan, tested under CP-4 |
Agencies should replace the DFARS rows with their own reporting procedures, and contractors should check which clauses are actually in the contract. Whether a given clause applies is for the contracting officer to determine. For agencies, our post on the CISA incident reporting form covers who must report to CISA within one hour and what the form asks, which makes a good worksheet for the reporting inject.
From our delivery teams: Give the evaluators a short list of the decisions you expect to see before the exercise starts, such as "isolates the hypervisor" or "names who files the report." Without it, the after-action report records what people said instead of what they missed.
After the exercise: the improvement plan
The hot wash, the facilitated debrief right after play, captures what people noticed while it's fresh. NIST SP 800-84 says the after-action report should be based on evaluation criteria "developed before the exercise," so data collectors know what to capture.
The improvement plan is where the exercise earns its cost. CISA's handbook says it "will provide timelines for improvement recommendation implementation and assignment to responsible parties." In practice, track each finding the way you would track a security finding: a named owner, a due date and a status. Fixes to the plan itself go into the next revision, which IR-8(c) asks for, and CP-4(c) asks for corrective actions after a contingency plan test. Other findings may belong in the system's Plan of Action and Milestones (POA&M).
Next steps
Before you book the room, settle these:
- Get the current CISA ransomware package, and contact [email protected] with questions.
- Pull the incident response plan, contingency plan and contract reporting clauses, and write two or three objectives from them.
- Name the players by role, including whoever holds the reporting credential, and get them on the calendar three months out.
- Write the federal injects and the expected-decisions list for the evaluators.
- Schedule the after-action meeting before exercise day, so the improvement plan has a date.
For related work on FISMA and NIST compliance, see our cybersecurity services.
The Bottom Line
A ransomware tabletop is worth the afternoon only if its objectives come from your own plan and reporting duties and its findings end up in an improvement plan someone owns. Start with a CISA package, write injects for the rules that apply to your system, and schedule the after-action meeting before the exercise.
FAQ
How often should a federal agency run a ransomware tabletop exercise?
NIST SP 800-53 IR-3 leaves the frequency to the organization, so the answer is whatever the agency defined in its policy or the system security plan. NIST IR 8374r1 says ransomware response and recovery plans should be tested periodically so their assumptions stay current with evolving threats.
Where do I get a CISA ransomware tabletop exercise package?
CISA's Tabletop Exercise Packages (CTEPs) are a library of customizable packages with template objectives, scenarios and discussion questions, and ransomware is one of the cyber topics. They are listed on cisa.gov under CISA Tabletop Exercise Packages, and CISA's exercises page gives [email protected] as the contact for more information.
What is the difference between a tabletop exercise and a functional exercise?
NIST SP 800-84 describes a tabletop as discussion-based only, with no equipment or resources deployed. A functional exercise has people perform their duties in a simulated operational environment, such as actually restoring a system from backup. Many teams run the tabletop first and use its findings to scope a functional test.
Does a tabletop exercise satisfy NIST SP 800-171 requirement 3.6.3?
Requirement 3.6.3 in Rev. 2 says to "test the organizational incident response capability," and its discussion says testing "includes the use of checklists, walk-through or tabletop exercises, simulations" and comprehensive exercises. Whether a given exercise and its records are enough is for the assessor, or the contracting officer for contract terms, to decide, so keep the scenario, attendance, notes and after-action report.
Who should play in a ransomware tabletop exercise?
The people who would make real decisions: the incident response lead, system owner, ISSO, network and backup administrators, legal counsel, communications and the official who would accept recovery risk. Contractors should include whoever files DoD reports and holds the medium assurance certificate.
Sources
- CISA, CTEP Exercise Planner Handbook
- CISA, CISA Exercises
- NIST IR 8374r1, Ransomware Risk Management, A CSF 2.0 Community Profile (June 2026)
- NIST SP 800-84, Guide to Test, Training, and Exercise Programs for IT Plans and Capabilities (September 2006)
- NIST SP 800-53 Rev. 5, Security and Privacy Controls (IR-3, IR-8, CP-4)
- DFARS 252.204-7012, Safeguarding Covered Defense Information and Cyber Incident Reporting (MAY 2024)
How we researched this. Every number, date and requirement here is checked against the sources listed above, primary documents first, and the post is fact-checked again before publication. When a rule, date or status changes, we update the post and log the change below. Read our editorial standards or send a correction.





