What is ransomware prevention?
Ransomware prevention is the set of technical controls that stop ransomware from getting in, spreading and destroying recovery, such as multi-factor authentication, network segmentation, least-privilege access and immutable storage locks. No control set blocks every attack, so prevention also covers protecting the backups that recovery depends on.
Which controls block entry and spread?
- Multi-factor authentication on remote access, email and administration consoles, so a stolen password alone does not sign anyone in.
- Patching of internet-facing systems such as VPN gateways and remote access services, a common entry point.
- Network segmentation, which limits which systems can reach each other once an attacker is inside.
- Least-privilege access, in the sense used by zero trust security: each account reaches only what its role needs, and network position grants nothing.
- Email filtering and endpoint protection, which reduce how often malicious attachments and links run.
How is backup storage hardened?
- Separate identities: backup administration uses accounts outside the production directory, with their own multi-factor sign-in, part of a logical air gap.
- Storage-enforced retention: an immutable backup lock in compliance mode means no account can delete or shorten retention on locked copies.
- Split permissions: the credentials backup software uses can write new data but cannot delete data or change locks.
- Approval for destructive changes: deleting repositories or reducing retention requires a second person.
- Alerts on configuration changes, so retention cuts and disabled jobs, the signs of backup tampering, are seen when they happen.
Why do locked backups matter when other controls fail?
Entry and spread controls lower the chance and duration of an attack, and each has failure modes: a phished user, an unknown flaw, a valid stolen login. A copy that cannot be deleted before its retention date behaves differently. It is either there on the day of recovery or it is not, and the attacker's skill does not change that. The question that tests a plan is what a stolen backup administrator login can delete. If the answer is anything, that login's administrative blast radius includes the recovery path.
What prevention does not cover
Locked backups protect recovery, not production. A successful attack still causes downtime while systems are restored, and stolen data is not returned by a restore. Getting systems back is the subject of ransomware recovery.
Frequently asked questions
Can ransomware be fully prevented?
No control set guarantees it, so prevention plans assume some attacks will get through and protect the backups accordingly.
Does patching matter if backups are locked?
Yes. Locked backups protect recovery, not production, so a successful attack still causes downtime and, where data is stolen, a breach.
Where does staff training fit?
It reduces how often phishing succeeds, but one successful click is enough for entry, so it works alongside technical controls rather than replacing them.
