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 SOC flags outbound connections from 40 networked infusion pumps on the oncology and intensive care floors to an IP address in a hosting range nobody recognises. The traffic started after last week's vendor maintenance visit. As far as nursing staff can tell, the pumps are still delivering medication normally. The manufacturer's support line says a patch is 'in validation' and will not commit to a date. Clinical engineering owns the pumps, IT owns the network, and the vendor holds the admin passwords. Pulling the pumps means moving patients to manual pumps you do not have enough of. What do you do in the next hour?