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.
At 22:47 a payables clerk receives 31 MFA push requests in eight minutes. On the 32nd, half asleep, she taps Approve. By the time she reports it next morning, the account has signed in from a hosting provider, registered a new MFA device and created an inbox rule that moves any email containing 'invoice' or 'payment' to an obscure folder. Two supplier payment runs are scheduled for 11:00 today. Your SOC saw the overnight push alert and closed it as user error. What do you do before 11:00?
Your accounts payable team receives an email from your largest packaging supplier, sent from their real address and replying to a genuine invoice thread. It says they have changed banks after an audit and attaches a signed letter with new account details. The clerk calls the number on the letter, gets a confirmation, updates the vendor record and pays $186,000 on Tuesday. On Friday the supplier's credit controller phones to ask why the invoice is overdue. Your bank says the receiving account is at another bank, which has not replied. What happens in the next hour?
Your filling-machine supplier emails every customer on a Thursday afternoon: an attacker had access to its remote-support platform for at least three weeks and 'may have used customer connections'. Your beverage plant gives this supplier always-on remote access to the line controllers so it can tune machines without a site visit. Your firewall shows sessions from the supplier's platform on four evenings when the supplier says no engineer was working. Its account manager wants the connection left open because a firmware fix is scheduled for Monday. Do you cut them off, and what do you look at first?
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?
At 10:20 your SOC escalates a confirmed business email compromise: an attacker in the CFO's mailbox has redirected a 1.3 million dollar supplier payment due to leave at 15:00. At 10:35 a second escalation: crypto-mining containers are running in production Kubernetes after a leaked deploy token, and the same token can push images. You have four incident responders, one of them on leave, and a retainer firm that can send two people tomorrow. Who works on what first?