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?
At 09:31 on the morning of a major interest-rate announcement, your online brokerage's order-entry service starts returning errors. Customers can log in and see positions but cannot place or cancel orders. Traffic is four times a normal day. A configuration change to the order-routing gateway went out at 08:50, and the network team is also seeing a surge from a few thousand IP addresses that could be a DDoS or could be your own customers' apps retrying. Customers with open positions are posting angrily on social media. Roll back, scale out or block traffic? You have one move to make first.
Two days before a municipal election, a 40-second audio clip spreads on social media. It sounds like your county's chief election official telling a colleague that ballots from two precincts 'will be handled differently this year'. A second post, styled like your website, says three polling places have moved. Your official never said this, and nothing has moved. By noon the clip has 300,000 plays, your phone lines are jammed, and a candidate is demanding an explanation. Your public results website is also seeing unusual traffic. How do you respond without amplifying the fake?
Monday: ransomware encrypts file servers at your online travel agency, but customer bookings still work. Wednesday: after you decline to engage, a DDoS takes the booking site down at peak hour. Thursday: the attacker emails journalists a sample of passport scans and threatens to call your largest corporate customers. Each pressure point lands on a different team that is already exhausted. The attacker's latest message sets a 24-hour deadline and promises the DDoS will stop the moment you pay.