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.
The head of sales operations clicked a link to a shared proposal on Monday and signed in as usual, MFA and all. This morning your identity logs show her session in use from a hosting provider while she is also active from the office, with no new sign-in and no MFA prompt. Overnight the session read 900 emails, downloaded the pricing folder, exported contacts from the CRM through single sign-on and consented to a new mail app. The help desk reset her password an hour ago. The activity has not stopped. Why not, and what do you revoke?
On Tuesday afternoon, a caller claiming to be a regional sales director phones the IT help desk from a number that is not on file. He sounds stressed, says he has a new phone and is about to present to a major customer, and knows his employee ID and his manager's name. The agent resets his MFA and sends a temporary password. Ninety minutes later the real director, sitting in your office, gets a sign-in alert. Since then the account has opened the CRM and the shared drive for an acquisition project. What now, and how did this get through?
Your help-desk software provider emails all customers at 18:00: an attacker accessed its production environment and "may have obtained" OAuth tokens that customers granted for integrations. Your instance has integrations with your CRM, your file-sharing platform and your code host, all granted with broad scopes two years ago by someone who has since left. The provider's notice gives no indicators, no timeline and a link to a status page. Your support team has 4,000 open tickets, many with customer attachments. The provider's account manager is not answering.
At 02:15 a help-desk agent reset MFA for a cloud administrator after a convincing phone call. By 03:00 the attacker had registered a new device, created an access key in your production cloud account and disabled two logging trails. By 05:30, 3 TB had left a storage bucket holding customer documents. Your SOC sees an impossible-travel alert at 07:50. The identity, cloud and data teams each hold part of the picture, and each believes someone else is containing it.