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.
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?
You run a municipal water utility serving 38,000 people. At 11:05 an operator watches the cursor move across the SCADA screen on its own and raise the sodium hydroxide dosing setpoint from 90 to 5,400 parts per million. He resets it within a minute, and downstream pH alarms would have caught it before treated water reached a tap. The workstation runs remote-access software installed years ago so the on-call operator could work from home. The mayor’s office has already heard about it from a council member. Do you tell the public, and what do you say?
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?
You run IT for a mid-sized water utility in the EU, classed as an essential entity under NIS2. At 06:30 monitoring shows that the remote-access gateway used by contractors has been accepting logins from an unfamiliar country for two nights, and the telemetry server it reaches is behaving oddly. Nothing has failed, and operations say pumping is normal. The national CSIRT expects an early warning within 24 hours of becoming aware of a significant incident. Is this significant, when did the clock start, and who sends it?