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 new data-loss prevention pilot produces its first weekly report. In seven days, staff pasted content into a free public AI chatbot 1,840 times. The sample includes a production database connection string, a customer contract with pricing, two HR investigation notes and a spreadsheet of patient appointment details. Your acceptable-use policy says nothing about AI. The approved enterprise AI tool, bought six months ago, has 30 active users out of 1,200. A department head replies to your email: "Everyone uses it. Banning it will just push people to their phones."
A parent forwards your district office an email from someone claiming to hold the records of every student in your 14-school district: names, addresses, grades, special-education plans and medical notes. Attached is a spreadsheet with her own child's details, correct as of last month. Your student information system is hosted by a vendor, and their support desk says they are 'looking into an incident affecting several customers'. The superintendent has a school board meeting tonight, and the local parents' group online already has 200 comments. What do you tell parents before the meeting?
A misconfigured analytics export at your online learning company exposed records for 640,000 students and staff in the EU, the UK, the United States, Canada and Australia. Fields include names, email addresses, dates of birth and, for 12,000 US users, partial payment data. You confirmed the exposure at 09:00 today. Each jurisdiction has different triggers, deadlines and regulators, and some of your customers are universities that are controllers in their own right. Counsel wants a single notification plan by end of day.
A security researcher posted on social media that your insurance comparison site had left a storage bucket of 80,000 quote applications open to the internet. You closed it within an hour and decided, after a quick assessment, that it did not need to be notified. Eleven days later a letter arrives from the data protection authority. It asks when you became aware, who accessed the data, why you did not notify, and for a copy of your breach register entry. Replies are due in 14 days. Your breach register entry is two lines long.
Four days after you notified 210,000 customers that their names, addresses and loyalty account details were exposed, a plaintiffs' law firm publishes a press release saying it is investigating claims against your retail chain and inviting affected customers to get in touch. A demand letter citing a state privacy statute arrives the next day. Customer support is fielding calls asking whether people should join. Your forensic firm is still finishing its report. What gets written down now may be read in court later.