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 05:40 on a Monday at a 900-person auto-parts manufacturer running three shifts. Office laptops started showing ransom notes an hour ago. Now the night-shift supervisor reports that two HMI screens on the stamping line show the same note, and the historian server has stopped updating. The PLCs are still running and the presses are still making parts, but operators can no longer see process values on screen. The first shift arrives in 80 minutes. Do you keep the line running blind, shut it down, or cut the plant off from the corporate network first?
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?