The popular picture is a user opening an attachment and every screen going dark at once. The modern reality is slower and worse. An attacker gets in, often through a phished credential, an exposed remote access service or a known flaw on an internet-facing system. They spend days or weeks moving through the network, escalating privileges, finding the backup servers and the file shares, and copying out the data they will threaten to publish. Only then, usually at a weekend or a holiday, do they deploy the encryption, having first deleted or encrypted the backups they found. The encryption is the last step of a long intrusion, and the defences that matter are the ones that interrupt the earlier steps or survive the last one.
| Stage | What the attacker does | What stops or limits it |
|---|---|---|
| Initial access | Phishing, exposed remote access, an unpatched public system | Phishing-resistant MFA, no exposed remote desktop, patching exposed systems first |
| Escalation and movement | Steals more credentials, becomes an administrator, maps the network | Least privilege, time-boxed admin rights, internal segmentation, endpoint detection |
| Exfiltration | Copies out the data to threaten publication | Egress monitoring, data classification, knowing what left |
| Destroying recovery | Deletes or encrypts backups reachable from the network | Backups the network cannot write to: offline, immutable, or in a separate account |
| Encryption | Deploys the payload everywhere at once | Detection and response fast enough to isolate; otherwise, the backups |
| Extortion | Demands payment; threatens to publish | A rehearsed decision, legal advice, and the knowledge of what was taken |
Double extortion, the theft before the encryption, changed the arithmetic. An organisation with perfect backups can restore its systems and still face publication of its customers' data, so the backup is no longer the whole answer; it is the answer to half the problem. The other half is knowing what left, which requires logging that most organisations do not have, and the notification obligations that follow, which are set by regulation rather than by the attacker's timetable. The management-level security credentials examine ransomware as a governance question for exactly this reason: who decides, who is told, what was promised to customers about their data.
