Active
--:--:-- UTCSyed Dayaan Shah
Incident ResponseSeverity · critical60 minutes (in-scenario)

Ransomware response — a branching 60-minute drill

Interactive scenario built from real IR playbooks I've worked from. Four decision points — detect, identify, contain, recover — with three branching choices each. Wrong call and the blast radius grows, right call and you close the incident with the postmortem intact.

Decision points

4

Branch outcomes

12

Scoring range

-9 → +12

Replay value

High

[01]Objective

Take a live ransomware page from first EDR ping to closed incident. Every decision you make changes what happens next.

[02]Live Lab · Ransomware response drill
Interactive · runs in your browser
Ransomware response · timedT1486 · data encrypted for impact

02:14 CT. Defender fires: vssadmin delete shadows /all on SRV-FS01, 43 hosts encrypting. Put your response in order before the clock runs out.

00:45
[03]Stack · Tools & Platforms

Tools

  • Defender XDR
  • Sentinel
  • Live Response
  • MISP / VT
  • Immutable Veeam backups

Platforms

  • Windows Server
  • Entra ID
  • Palo Alto NGFW
[04]Method
  1. 01

    Modeled real BlackFang-family behavior — vssadmin canary, JA3-fingerprinted C2, admin-token abuse.

  2. 02

    Each stage exposes real IR levers (isolation, JA3 block, token revocation, immutable restore) with realistic trade-offs.

  3. 03

    Scorecard grades containment speed vs. business impact so you can see the shape of your own decisions.

[05]Outcome

Interactive lab — your call at every branch, real scorecard at the end, with decision trace for review.

[06]Lessons learned
  • Network isolation beats process-kill — persistence hooks respawn the process, but not the socket.
  • Identity revocation is a first-class containment lever, not a cleanup step.
  • Immutable backups make 'don't pay' a real option instead of a slogan.

Next case · PHISH-001

Phishing kit dissection — anatomy of a credential harvester

Open →