Double-extortion ransomware
Hypervisors encrypted on a Friday night, data on a leak site, and a ransom demand on the table.
- Duration
- 3 h
- Injects
- 9
- Audience
- Technical · Executive · Legal & privacy
Incident-response tabletop exercises
A practical library for running cyber tabletop exercises: the method to plan and facilitate them, and ready-to-run scenarios with timed injects, discussion questions and scoring rubrics.
TTX-01 · Double-extortion ransomware
EDR alert: mass file renames on a file server.
Users report shared drives will not open.
Hypervisor cluster unreachable; ransom note found.
Decision point
Isolate the virtualization network now, knowing it takes production offline?
The method
Six phases take you from a blank page to a signed-off improvement plan. Each one has a detailed guide with templates.
Scenario library
Every scenario card gives you the threat, difficulty, duration and audience at a glance. Open one for objectives, the inject timeline and discussion questions.
Hypervisors encrypted on a Friday night, data on a leak site, and a ransom demand on the table.
A supplier's “new bank details” and a wire that already left. Can finance and IT claw it back?
A long-lived key pushed to a public repo, a billing spike and storage buckets being listed.
A privileged engineer resigns and gigabytes flow to personal cloud storage. HR, legal and security must act together.
A trusted vendor's signed update was trojanized, and it is installed on hundreds of your machines.
Your storefront and API buckle under a multi-vector flood, then an extortion email arrives.
Principles
Every inject is written to force a decision someone will actually face: isolate or monitor, pay or restore, notify now or investigate further.
Scoring rubrics evaluate plans, processes and communications. Nobody is graded, so people speak freely about gaps.
Each exercise ends with an after-action report and an improvement plan that has owners and dates, then a re-test.
Start with the planning guide, then run the business email compromise scenario. It is short, needs no deep technical staff and exposes real process gaps.
Start with the planning guide