CyberDrill scenario attack phases with MITRE ATT&CK tags

Cybersecurity tabletop exercises: who decides, and what record is left.

A cybersecurity tabletop exercise has two jobs that are easy to mix up. The first is to test who owns each decision as a scenario unfolds. The second is to leave a record of what the room actually did. A security leader can design the first. A recorded exercise shows the second. The two are complementary. One does not replace the other.

This split is the same for a small firm, an MSP, and a fractional CISO. Someone has to decide who escalates, who speaks, and who may isolate a system or stop a payment. Someone also has to show, later, what was said and chosen. A plan can name the owners. Only a recorded exercise can show whether those owners acted.

What a cybersecurity tabletop exercise is.

CISA describes a tabletop exercise, or TTX, as a role-playing activity. Players respond to a scenario presented by one or more facilitators, usually in their real jobs, such as chief executive, IT lead, or communications lead. The aim is to work as a team and to find problem areas before a real incident forces the same questions.

Observers may ask questions, but they do not play. Facilitators give updates and moderate the discussion. Note-takers document what the players said and did, including whether that discussion followed the organisation's plans, policies, and procedures. Those roles are set out in CISA's Cybersecurity Tabletop Exercise Tips.

Some people call this a cyber drill. CISA's small-business guidance even speaks of "tabletop exercise drills" when it asks the chief executive to take part. The usual name in public guidance is still a cybersecurity tabletop exercise, and that is the term this article uses. The session tests people and plans, not live systems. It does not prove that backups restore, or that detection works. Those questions need a technical test, run as a separate exercise.

CISA's cyber guidance for small businesses, updated in April 2024, asks the security programme manager to host quarterly tabletop exercises. It also asks the chief executive to review and approve the incident response plan, and to attend the exercises.

An incident response tabletop exercise is the same kind of session, aimed at the incident response plan. CISA's Tabletop Exercise Packages give starting material: objectives, scenarios, discussion questions, and an After Action Report template. NIST SP 800-84 describes a tabletop as discussion-based. Staff talk through their roles and responses. They do not deploy equipment or other resources.

Who decides during the exercise.

The hard questions in a tabletop are rarely technical. They are about authority. Who is in charge of the response? Who may take a system offline? Who may tell a customer or a regulator? Who may pay, or refuse to pay, if a ransom demand appears in the scenario? If those answers are unclear in the room, they will be unclear in a real incident as well.

Before the scenario starts, write each major decision next to one named person: declare the incident, approve outside counsel, speak to customers, call law enforcement. A security leader designs that structure first. In a small firm the leader may be the owner, an IT manager, or a fractional CISO. In an MSP or vCISO practice the leader may design it for a client, then sit with them in the room. If you can, keep the facilitator off the decision list, and keep the person who coordinates the room separate from the person who is busy with the systems.

CISA's tips are plain on this point. "No one is really in charge of that here" is a common observation, and one that might require action. The exercise does not invent the authority. It tests whether that authority holds when the facts are incomplete and the clock is running.

Example scenarios (illustration only).

The scenarios below are examples, not client stories and not a claim about any real incident. Pick the incident your firm could most plausibly face, then swap in your real bank, email provider, and backup vendor. CISA's tabletop packages are a sound place to start for objectives and questions.

Example scenario Key decision it forces Who should be in the room
Ransomware on a shared system Who declares the incident, and who may decide on payment IT lead, finance lead, legal, communications
A vendor payment changed by a forged email Whether to freeze funds, and who may call the bank or counsel Finance, legal, IT
An insider with privileged access Whether and how to revoke access HR, legal, IT
A cloud folder left open to the wrong people What data is in scope, and who may notify customers IT, legal, communications

If a key person cannot attend, CISA's tips say you can write that absence into the scenario. A finance lead who is travelling and unreachable becomes a test of backup authority.

How to run an incident response tabletop exercise.

A good session is a guided conversation on a clock. The facilitator reads a short situation. Players answer in their real roles. Timed updates force the next call. A note-taker logs who decided, and when. CISA's tips also suggest a shared live document, so people can add notes as they go.

Before the session.

Set a few measurable objectives, tied to the plan you want to test. Name the incident manager. Confirm that the incident response plan and the contact list are current. Prepare the opening situation and the later updates. Brief the players that the session is for finding gaps, not for scoring people. If someone important is away, build that fact into the story, as CISA suggests.

During the session.

The facilitator reads the opening situation, and players respond aloud. CISA's tips ask people to think out loud, so the reasoning can be heard and recorded. After each update, ask who decides, then log the decision, the owner, and the time. If the plan is silent, record the gap. Do not invent a policy on the spot. Hold to the clock when you can. The facilitator can still pause to keep the discussion usable.

After the session.

CISA's exercise packages include time for a hot wash after play. Leave room for that conversation before people leave. Ask what worked, what failed, and what surprised them. Turn those points into findings with owners and due dates, and fold the lessons into the incident response plan, not only into the report.

What record a tabletop exercise after-action report should leave.

A useful cybersecurity tabletop exercise report is a record of what happened in the room, not impressions written up the next morning. CISA gives the note-taker that job: document the discussion, and note whether it followed the plan. CISA's packages also include a template for an After Action Report.

The test is simple. Could someone who was not in the room tell, from the document alone, who was present, what updates arrived, what was decided, and which findings now have an owner? If not, you have a memory of the day, not a record. The table below is a writing aid, not a claim that any one format meets a particular rule.

Report part What it records
Exercise overview Type, date, scope, scenario, and who took part
Objective analysis Whether each objective was met, with what was observed
Decision log The decision, who made it, and when
Improvement plan Corrective actions, each with an owner and a due date
Sign-off Facilitator and accountable executive, with the date

A policy says what should happen. The record says what did happen, with a name and a date on it. CISA asks the security programme manager to review the incident response plan quarterly, and after every incident or near miss. Findings need owners and due dates, or they stay as notes.

A firm can keep that report, or share it with an auditor. It can serve as evidence that an exercise happened, who took part, what was decided, and which follow-ups were owned. That is often useful in regulated industries, such as healthcare, finance, and legal, where someone may later ask what the room actually did. Whether the evidence meets a particular requirement is for the auditor or the regulator to decide.

The HIPAA Security Rule does not mandate tabletop exercises. It does require policies and procedures to address security incidents, and a periodic technical and nontechnical evaluation of whether those policies and procedures meet the Rule. Firms that must meet PCI DSS v4.0.1 have a more specific testing duty. Requirement 12.10.2 says the security incident response plan must be reviewed, updated as needed, and tested at least once every 12 months, including the elements listed in Requirement 12.10.1. A tabletop can be one way to test the plan. Whether a particular session meets that requirement is for the assessor to decide.

Reporting clocks can also be a decision the room should practise, but only with the current law in view. The Cyber Incident Reporting for Critical Infrastructure Act directs CISA to issue rules under which covered entities would report a covered cyber incident within 72 hours, and a ransom payment within 24 hours. CISA says those reports are not required until the final rule goes into effect. As of 21 November 2026, the final rule was not in effect. A final-rule package had been submitted to OIRA on 1 October 2026 and was still under review. Check CISA's CIRCIA page before you treat any of those clocks as a binding duty.

What a signed cybersecurity tabletop exercise report can show.

Handvantage publishes a product, CyberDrill, that runs this kind of tabletop in a browser. The public page is the source for what follows. Nothing here is a claim about a particular customer, a result, or a score. If a screen or a report is shown, treat it as a sample to look at, not as a real customer's file.

The clock releases timed updates. The room makes the decisions. A decision releases only the update that follows from it. The other branches do not fire, and the record shows which path the room took. Every participant is signed in by name, so each action, message, and decision is attributed to a person. The facilitator can pause, steer, or drop an unscheduled update.

CyberDrill scenario attack phases with MITRE ATT&CK tags
From CyberDrill: attack phases in a sample scenario, with durations and MITRE ATT&CK tags. This is a sample to look at, not a customer file.
CyberDrill scenario decision point with three choices
From CyberDrill: a sample scenario’s decision point at minute 130, with three choices. This is a sample to look at, not a customer file.
CyberDrill facilitator screen with send update early control
From CyberDrill: a facilitator screen in a rehearsal. The facilitator can send the next update early, or keep it on the clock. This is a practice run with simulated colleagues, not a customer file.

When the exercise is completed, the log is sealed. Updates, actions, messages, and notes are hashed with SHA-256. The after-action report is written from that log, in numbered versions. Each finding can be given an owner and a due date. The completed exercise also exports as one signed document, holding the sealed log, the decisions, the findings, the after-action report, and the later audit entries. The log's hash sits inside it, and a signature covers the whole file. The same page offers a public verification endpoint, which can be used without an account. The signed document can also be delivered to an endpoint the organisation controls when the exercise locks.

Example report (illustration only).

No product screenshot of a sealed log or of findings with owners is included here. The public CyberDrill page shows a completed demonstration exercise. It is an illustration only, not a customer report. In that example the log is locked, the after-action report is at version 2, and findings are listed with owners assigned.

An organisation can run this itself. Nothing has to be installed, and a consultant is not required. A consultant the firm already trusts can be invited as a facilitator. On the public page, that person can plan, run, and close exercises. They cannot touch billing, settings, or the audit log, and they cannot delete a record. A partner can keep each client organisation separate.

CyberDrill does not replace the security leader. It does not write the incident response plan, and it does not sit with you in a real crisis. A fractional CISO who has set the owners still benefits from a signed trail. The product is one way to put the room on a clock and keep a signed cybersecurity tabletop exercise report of what happened.

How small firms, MSPs and fractional CISOs can use both.

If you lead security for a small firm, start with the two questions in the title. Who decides, in writing, before the room sits down? What record will exist when the room stands up? CISA's tips and tabletop packages are a sound place to begin. The right interval is the one you can actually repeat, with findings closed before the next session.

If you are a fractional CISO or vCISO, the design work is probably already yours. The recorded exercise is how you and the client can both see whether that design held. Invite the client's leaders, not only their technical staff. CISA asks the chief executive to take part for that reason. Keep the client's record in the client's organisation. If you are an MSP, you may facilitate, but the client still owns the decisions and the record. Do not let one client's session share a screen or a file with another.

A related piece, First 90 days of AI governance: a tutorial, already suggests a tabletop when you test an escalation path. The same advice holds here.

Frequently asked questions.

What is a tabletop exercise example?

Here is an illustration only, not a real case. A bank calls about a transfer to a vendor's new account. A second transfer did not go through. The only authorised employee says they started neither payment. The team has to decide whether to freeze funds, when to bring in counsel, and who contacts the bank. That kind of prompt can fit a short staff-meeting discussion. CISA describes a scaled-down tabletop as a ten-minute discussion at the start of a meeting.

What is the difference between a tabletop exercise and a simulation?

A tabletop is discussion only. A simulation or drill takes real actions, such as activating backups. In official vocabulary, a drill is a narrow operations-based test of a procedure. A tabletop is discussion-based. People also search for a "security table top exercise". It is the same kind of session.

How often should you run a cybersecurity tabletop exercise, and how long does it take?

CISA's small-business guidance asks the security programme manager to host quarterly tabletop exercises. Firms that must meet PCI DSS v4.0.1 Requirement 12.10.2 also have to review and test the incident response plan at least once every 12 months, as set out above. Add a session after a major change in staff, systems, or leadership, and close findings before the next run.

There is no single required length. CISA's tips say you can run a scaled-down ten-minute discussion at the start of a staff meeting. NIST SP 800-84 says a tabletop typically lasts two to eight hours, depending on the audience, the topic, and the objectives. CISA's packages often plan for about four hours of play, and they leave the actual length to the organiser.

One next step.

A new organisation can start a 30-day trial of CyberDrill's Business features, with no card required. Each account gets one trial. The product is at cyberdrill.handvantage.com. Use it, or any other careful method, to run the exercise on a clock and keep the record. Then assign the findings with the person who owns the plan.

Sources.

All sources below were reviewed through 21 November 2026, America/Vancouver.

Similar Posts

Leave a Reply

Your email address will not be published. Required fields are marked *