Free · complete · nothing held back
When did you last test the plan?
It is the question insurers ask on the application form, auditors ask in the room and NIS2 expects you to be able to answer — and for most small organisations the honest answer is never. A tabletop exercise is the cheapest way to change that: ninety minutes, a printed page, and no system touched.
What a tabletop actually is
Eight events are read aloud in sequence. The group decides what it would do. Nobody logs into anything, nothing is switched off, and no technical knowledge is needed by anyone in the room — including whoever runs it. What it produces is a record of what your organisation would decide, and a list of what it does not yet know. The second list is the point. An exercise that raises no findings was facilitated too gently.
Roles
Hand each person one role. If you are small, people double up. Coordinator · IT lead or IT provider · Owner or managing director · Finance · Communications / customer contact · Note-taker (records every decision and every unanswered question).
The scenario: a Monday in November
| Time | Inject (read aloud) | What the room must decide |
|---|---|---|
| 07:14 | The office manager reports the shared drive is “very slow” and some files have odd extensions. | Who is told first? Who can authorise disconnecting machines? |
| 07:41 | A ransom note appears on three screens. It claims data has been copied and gives 72 hours. | Who is now coordinating? Is the log open? |
| 08:05 | Your IT provider says their first free engineer is available at 14:00. | What do you do in the meantime? Who else can you call? |
| 08:30 | You discover the backups stopped nineteen days ago without anyone noticing. | What can you restore, and from when? What cannot you restore? |
| 09:15 | The attackers email a sample: a spreadsheet of customer names, addresses and IBANs. | Is this a personal data breach? When did you become aware? Has the GDPR 72-hour clock started — and does NIS2 reporting apply to you? |
| 10:30 | A customer rings asking why their invoice was changed to new bank details last week. | Is this connected? Who rings the bank, and who rings the customer? |
| 12:00 | A journalist from a local paper emails asking for comment. | Who speaks, and what do they say — and not say? |
| 15:00 | Your insurer asks when you first became aware and what you have done since. | Can you answer from the log? Will they cover the IT provider’s time? |
Complications, for when the room finds it too easy
- The coordinator is on a flight to Boston until Wednesday.
- The attacker’s email arrives in a language nobody in the room reads well enough to be sure what it says.
- The finance director suggests quietly paying to “make it go away”.
- A staff member has already posted on LinkedIn that “systems are down”.
- The spreadsheet sample includes data about children from a sports club you sponsor.
- Your largest customer is a bank and asks for a formal incident notification within 24 hours under its DORA obligations.
Evidence of exercise
Afterwards, the note-taker writes one page: date, participants and roles, scenario, decisions taken, questions nobody could answer, actions with an owner and a date. Keep it with your incident plan. That page is exactly what an insurer’s “when did you last test the plan?” question is asking for. It evidences that you rehearsed decisions; it does not evidence that your backups restore, and it should say so.
Three more scenarios
Supplier compromise; an insider leaving for a competitor; an AI tool leaking a client list. Each with its own deck, facilitator’s guide and complications, written for the GDPR, NIS2 and DORA clocks.
- Printable card decks
- Facilitator’s guide
- Decision log and after-action report
€175+ VAT at launch
Register interestWant it facilitated?
An outsider running it, recording it, and giving you a findings report an insurer accepts.
- Scenario built for your business
- Half a day, up to fifteen people
- Written record within five working days
From €3,100+ VAT
Facilitated exerciseRan it, and it hurt?
That is the point. The first-hour checklist and the incident runbook are the other half.
