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.
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 16:30 on a Thursday a developer at a 200-person subscription software company runs a data-retention cleanup script against what he believes is the staging database. It is production. Before he kills it, the script has deleted 38% of customer account records and their linked invoices. The app is still up, but thousands of customers now see empty accounts or ‘user not found’. Support tickets are arriving at 40 a minute. The last full backup finished at 02:00. Nobody acted maliciously. How do you get the data back, and what do you tell customers?
A severe storm has hit the region served by a 1,200-person home insurer, and claims calls are at five times normal volume. At 08:20 the cloud contact-centre platform your agents use for calls, chat and call recording goes down across the provider’s entire region. The provider’s status page says ‘investigating’ and gives no estimate. Agents can still log into the claims system but cannot take calls. Customers with flooded homes are getting a dead line, and local radio has started asking why. Your contract’s service credit is worth one month’s fees. What is your plan for the next eight hours?
Accounts payable at your industrial equipment manufacturer pays $860,000 to a long-standing steel supplier, and three days later the supplier asks where its money is. The bank details on file were changed through your supplier self-service portal two weeks ago, by a login using the supplier's own account. The same account uploaded six updated 'drawing packages' that your design engineers have since opened. Two other suppliers report odd password-reset emails from your portal. The portal is run by a SaaS vendor your procurement team chose. What do you check, freeze and tell suppliers today?
A customer of your 400-person HR software company opens a support ticket with a screenshot: their dashboard search returned salary records belonging to another customer's employees. Engineering traces it to a caching change deployed nine days ago that sometimes keys results by query text instead of by tenant. Logs show the faulty path ran at least 6,000 times, but nobody yet knows how many of those responses held another tenant's data, or which tenants saw what. You process data for 1,100 business customers, most of them in the EU and UK. The fix is ready. Do you ship it now?
Your project-management SaaS has been degraded for six hours. Officially the cause is 'database performance'. In reality the security team took two clusters offline after finding an attacker's web shell on an API server, and nobody yet knows whether customer data was accessed. The public status page still shows a yellow 'degraded' banner. Enterprise customers are asking about SLA credits, two have asked outright whether this is a security incident, and one has a contractual 48-hour breach-notice clause. Sales wants the status page to say 'scheduled maintenance'. What does the status page say now?
Your accounting software company refused a ransom demand last week after a data theft. This morning hundreds of your small-business customers received an email from the attacker. It quotes each customer's own invoice data as proof, says you 'chose not to protect them', and invites them to pay 500 dollars each to have their records deleted. Support has 900 tickets in the queue. Two customers have posted the email on social media, and one says they have already paid.