Decision Tree — Ransomware Response: Restore, Pay or Rebuild
An incident-response cost tree: restoring from immutable backups, with a fallback rebuild if they were also encrypted, rolls back to an expected $676k against $1,980k for rebuilding and $1,995k for paying the ransom, whose tail runs to $4,000k when the decryptor fails. Illustrative values.
Make it your own.
title "Ransomware on the file servers — restore, pay or rebuild?"
subtitle "Expected total incident cost, US$ thousands — downtime, recovery labour, legal and notification"
currency $
unit k
objective min
measure "E[cost]"
probabilities percent
branches orthogonal
risk-profile compare
note "Paying a ransom may breach sanctions law and does not end a data-theft extortion; take legal advice first."
note "Illustrative values for a fictional 600-seat firm with immutable nightly backups."
decision "Recovery route"
"Restore from immutable backups" cost 120 -> chance "Backup integrity"
"Clean restore point" p 70% -> 300
"Partly corrupted" p 25% -> 860
"Backups also encrypted" p rest -> chance "Fallback rebuild"
"On schedule" p 60% -> 2,300
"Overruns" p rest -> 3,100
"Pay the US$1.2M demand" cost 1,200 -> chance "Decryptor"
"Works fully" p 65% -> 300
"Works partially" p 20% -> 900
"Fails or re-extorts" p rest -> 2,800
"Rebuild from scratch" cost 400 -> chance "Rebuild duration"
"Three weeks" p 60% -> 1,300
"Five weeks" p rest -> 2,000