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.
It is 09:00 on Black Friday at an online homeware retailer that takes 18% of its annual revenue in the next four days. Requests to the checkout API jump to 40 times normal, response times pass ten seconds and the site starts returning errors. An email arrives at the press address: pay 5 bitcoin or the site stays down all weekend. Your CDN has basic DDoS protection, but the checkout API sits outside it on a separate hostname. Marketing has a promotional email going to 3 million customers at 10:00. What do you do in the next hour?
Your acquiring bank emails: card-fraud analysis links 212 fraudulent transactions to cards used on your online store over the past five weeks, and they want a forensic investigation. Your developers find nothing changed in your own code. Then a front-end engineer notices the checkout page loads a chat widget from a vendor's CDN, and the script now contains 40 extra lines of obfuscated JavaScript that post form fields to an unfamiliar domain. The widget is on every page, including payment. Peak-season trading starts in nine days. What do you remove, what do you keep, and what do you tell the bank?