Breach Risk Direct.
Security Controls

Running a Ransomware Tabletop Exercise: An 8-Step Plan for Finance, Legal and IT

Most ransomware drills stop at containment. This plan also rehearses the insurer call, the extortion decision and the business interruption claim file, then turns the results into evidence for underwriters at renewal.

Breach Risk Direct editorial team · November 2026 · 7 min read

Build the drill around the claim, not just the containment

Most ransomware tabletop exercises end once IT has isolated the infected hosts. The expensive mistakes tend to start after that. Someone hires a forensics firm the insurer hasn't approved. Nobody notifies the carrier inside the policy's notice window. Finance begins reconstructing lost revenue weeks after the outage. Any of these can shrink a recovery that should have been covered.

A ransomware tabletop exercise built around the claim tests four things your technical runbook usually skips. Who calls the insurer's breach hotline, and how fast. Who can escalate an extortion demand, and on what criteria. Which financial records prove a business interruption (BI) loss. And how the results get packaged as proof for underwriters at renewal.

Advertisement

The steps below assume a half-day session with finance, legal and IT in the room, plus your broker. Smaller firms can compress it to two hours. Large groups should run it once per major operating region, because notification and payment rules differ by country.

Assign the roster and the hotline owner before you write a single inject

Start with a short role sheet. Every role needs a deputy, because real incidents land on holidays.

  • Incident commander (usually the CISO or head of IT): makes the technical calls and reports to executives.
  • Insurance notifier (the risk manager, or the CFO at smaller firms): owns the call to the carrier's hotline and the written notice to the broker.
  • Legal lead (general counsel or outside breach counsel): handles privilege, regulator notifications and the legality of any payment.
  • Finance lead: opens the BI loss file on day one.
  • Executive decision-maker: approves or rejects payment and settles conflicting priorities.

Before the session, pull the policy's notice requirement, panel vendor list, consent-to-incur-costs clause, extortion sublimit, retention and BI waiting period onto one page. If nobody can find that page in five minutes on exercise day, you've found your first gap.

Write tabletop exercise scenarios with insurance-specific injects

Good tabletop exercise scenarios release information gradually and force people to commit to decisions under time pressure. Mix technical injects with ones that test the policy. The timeline below suits a mid-size firm; adjust the clock to your own notice and waiting periods.

Exercise clockInjectDecision being tested
T+0Help desk reports encrypted file shares at two sitesWho declares an incident, and who calls the insurer hotline
T+2hYour usual IT contractor offers to start forensics right awayPanel vendor versus non-panel vendor, and whether consent is needed
T+6hRansom note demands the equivalent of $1.8M in cryptocurrency within 72 hoursEscalation path and sanctions screening
T+12hOrder processing is down and the BI waiting period is runningWhether finance has started tracking lost revenue and extra expense
T+24hThreat actor posts a sample of HR files on a leak siteRegulator and data subject notification across jurisdictions
T+48hBackups are only partly restorable, so recovery will take six more daysWhether to pay, how long restoration will run, and what goes into the claim

Hold a few curveballs back, such as an unreachable CFO or a panel firm at capacity. Give one to whichever team looks too comfortable.

Rehearse the hotline call and vendor engagement as a cyber insurance claim rehearsal

Here the notifier actually dials the hotline, with your broker or the facilitator playing claims handler. Can they give the policy number, entity name, discovery time, affected systems and a callback number without searching?

Then test vendor discipline. Many cyber policies cover forensics, breach counsel and negotiators only if they come from the panel or the insurer approves them in advance. Sign a non-panel engagement in the first hour and those costs may be reimbursed at a reduced rate or not at all. Your legal lead should also explain how forensic work will be commissioned. In the US, firms commonly engage forensics through counsel to help protect privilege. Courts in the UK, EU and Asia-Pacific treat privilege differently, so ask counsel in each jurisdiction what actually protects you.

Score this step on time from discovery to first insurer contact, and on whether every vendor engaged was approved.

Escalate the extortion decision as a board ransomware drill

The payment decision should never sit with IT alone. Run this inject as a board ransomware drill: executives receive a written decision memo and must choose within the exercise clock.

The memo should cover:

  • Legality: sanctions screening against relevant lists, such as US OFAC, UK OFSI, and EU and UN regimes, plus any local reporting duties. Some countries, Australia for example, require many businesses to report ransomware payments to the government.
  • Insurer consent: extortion cover usually requires written consent before any payment, and may be capped by a sublimit.
  • Operational need: whether restoring from backups is realistic, and how long it would take.
  • Data exposure: whether paying changes regulatory or contractual notification obligations. It usually doesn't.
  • Reputational and ethical position: whether the board has a standing policy on paying.

Write down who has final authority and at what threshold. One example: "CEO and CFO jointly, with the board chair informed, for any payment above $250,000." Payment law is changing in several countries, so have a licensed adviser confirm the rules wherever you operate.

Collect the records a business interruption claim will need

BI is often the largest part of a ransomware loss and the hardest to prove. Most policies pay lost net profit plus continuing fixed costs during the period of restoration, after the waiting period, along with reasonable extra expense to reduce the loss. Adjusters will want evidence of what you would have earned had the attack not happened.

During the exercise, the finance lead should list where each of these records lives and who can produce it while systems are down:

  • Twelve to twenty-four months of monthly management accounts, plus daily or weekly sales by channel
  • Seasonality data and the order backlog
  • Payroll records and overtime logs for staff kept on during the outage
  • Invoices for temporary hardware, expedited freight, outsourced processing and extra staff hours
  • A timestamped log of when each system went down and came back

Hypothetical example: say a 250-person distributor earns about $40,000 in gross profit per day and is down for four days, with a 12-hour waiting period. The covered income loss is roughly 3.5 days, or about $140,000, plus perhaps $50,000 in overtime and freight. A $100,000 retention comes off before any payout. If finance can't show where the $40,000 daily figure comes from, the adjuster will negotiate it down. And if your ERP is the system that gets encrypted, keep offline copies of the baseline reports.

Score the session and price the facilitation honestly

Within two weeks, write a short after-action report. Record time to declare an incident, time to first insurer contact, time to a payment decision, how many non-panel vendors were engaged and whether the BI file was opened. Every gap gets an owner and a due date.

For a cyber incident simulation for executives run by an outside firm, typical 2026 market ranges are roughly $8,000–$25,000 for a facilitated half-day session, and $25,000–$75,000 or more for multi-session programs with a technical track. Prices vary by region, firm and scope, so confirm with vendors. Some carriers and brokers subsidize these sessions as a policyholder service, so ask before paying full price.

Red flags in a facilitator:

  • Generic scenarios that don't reference your policy
  • No finance or legal injects
  • A report that lists problems without assigning remediation owners

Turn findings into evidence underwriters will accept at renewal

Renewal questionnaires commonly ask whether your incident response plan has been tested in the past 12 months. A yes backed by evidence carries more weight than a checked box. Schedule the exercise roughly 90 to 120 days before renewal so you can close the most important gaps before submission.

Give your broker a one- to two-page summary: date, participants, scenario, metrics, remediation actions and their status. Keep the full report internal, and talk to counsel about privilege before sharing any of it. Evidence of fixes, such as tested offline backups, a distributed hotline card or documented payment authority, gives your broker something concrete to use when negotiating retention or terms. It doesn't guarantee a better price.

A simple rule: if the summary can't name the person who calls the insurer and the person who approves payment, run the exercise again before you submit.

Frequently asked questions

How often should we run a ransomware tabletop exercise?

Once a year is the minimum most underwriters expect. Run another after a major change, such as a new carrier, an acquisition, an ERP migration or a change of CFO or general counsel. Large multinationals often rotate regional sessions through the year so each jurisdiction's notification rules get tested.

Should our insurer or broker attend the exercise?

Your broker usually should. They can play the claims handler and flag where your process conflicts with the policy wording. Including the carrier is less common, though some offer it as a policyholder service. Either way, agree in advance what will be documented and shared.

Do we need board members in the room?

For the extortion and disclosure injects, yes. Ideally that means at least the board chair or the chair of the audit or risk committee. Directors don't need to sit through the technical portion. A short separate session built around the payment decision memo works well for most boards.

Will a tabletop exercise lower our cyber insurance premium?

Not automatically. Premiums depend on market conditions, loss history and core controls such as MFA and backups. A documented exercise with remediation already closed can strengthen your broker's position on terms and retention. Ask your broker how your carriers weigh it.

Written by the Breach Risk Direct editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.