100 ready-to-run cyber tabletop exercises across 15 incident domains. Search them, pick one at random, or tell us who will be in the room and we'll rank the scenarios that fit those people best. Every exercise shows who to involve, how long it runs and an outline — and the scenario prompt is free to copy and read out.
Running one for real? Pro adds the facilitator's run sheet for each exercise: a minute-by-minute timeline, timed injects, step-by-step facilitation guide and the questions to put to each person. Or build your own with the Tabletop Runbook Generator.
Who's in the room?
Pick the people you have — we'll suggest exercises that fit them.
Executive
Business
Technical
Matching exercises
2 of 100
Outage / resilienceIntermediateExecutive 1 h 30 min
At 07:15 on a Tuesday, your EU payment institution loses its core transaction database after a fault at the cloud provider that hosts it. Card authorisations are failing for about 40% of merchants across four member states. The provider's status page says 'degraded performance' and gives no estimate. By 09:00 your service desk has logged 2,300 merchant complaints. Your head of compliance asks the question nobody has answered yet: is this a major ICT-related incident under DORA, and if so, when did the clock start? The CEO wants to know what goes to the regulator, and when.
You run IT for a mid-sized water utility in the EU, classed as an essential entity under NIS2. At 06:30 monitoring shows that the remote-access gateway used by contractors has been accepting logins from an unfamiliar country for two nights, and the telemetry server it reaches is behaving oddly. Nothing has failed, and operations say pumping is normal. The national CSIRT expects an early warning within 24 hours of becoming aware of a significant incident. Is this significant, when did the clock start, and who sends it?