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 group financial controller takes a call from what sounds exactly like the CEO, who is travelling. He says a confidential acquisition must close today, the lawyers will email instructions, and nobody else can know yet. Minutes later an email arrives from an outside law firm with wire details for €1.9 million and a signed letter of intent. The controller is uneasy and calls the CEO's mobile, which goes to voicemail. A voice note then arrives from an unknown number, in the CEO's voice, repeating the request. The bank cut-off is in 45 minutes. What should happen?
On Monday a finance manager joined a video call with what looked and sounded like your CEO and CFO, plus an "external lawyer". They explained a confidential acquisition and asked for three urgent payments to an escrow account, totalling $2.4 million. The manager made the payments after a follow-up email from the CEO's real address, sent through a compromised mail rule. Today the real CEO asks why finance moved money on a deal that does not exist. Your bank says the first transfer has left the receiving bank. The finance manager is distraught.
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?