Data destruction is the deliberate deletion, corruption, or encryption of data to cause harm or cover an attacker's tracks. It shows up as ransomware, wiper malware, and insider sabotage. Unlike theft, the damage is to availability and integrity, so the only reliable defense is backups you have tested restoring, plus tightly limiting who can delete data at scale.
What counts as data destruction?
Data destruction is any deliberate act that makes your data unavailable or untrustworthy: deleting it, corrupting it, or encrypting it beyond your reach. It is the third leg of the classic security triad. Where a leak or exfiltration attacks confidentiality, destruction attacks availability and integrity, the ability to use your data and to trust that it is correct.
That distinction matters because the recovery is completely different. You cannot un-leak stolen data, but you can restore destroyed data, if, and only if, you kept a copy the attacker could not also reach.
Where it comes from
Destruction takes a few common forms:
- Ransomware, which encrypts data and holds the key for payment.
- Wiper malware, which destroys data outright, sometimes disguised as ransomware with no working key.
- Insider sabotage, a disgruntled employee deleting or corrupting systems.
- Cloud account or key deletion, where an attacker with admin access deletes storage, snapshots, or the keys needed to decrypt.
- Accidental mass deletion, which is not an attack but causes the same outage and belongs in the same recovery plan.
Why it is different from theft
Stolen data is a confidentiality and compliance problem. Destroyed data is an operational one: systems stop, orders cannot be processed, and the business can halt entirely until data is restored. That is why ransomware, which weaponises availability, has been so effective.
Sophisticated attackers also destroy data to cover their tracks, wiping logs and evidence so you cannot see what they did or how they got in. That makes recovery and investigation harder at the same moment.
How to defend and recover
Because you cannot prevent every destructive act, resilience is the goal:
- Keep 3-2-1 backups (three copies, two media types, one off-site) and, crucially, make at least one immutable or offline so an attacker with admin cannot delete it.
- Test restores. A backup you have never restored is a guess.
- Limit who can delete at scale. Least privilege and multi-factor authentication on cloud and backup admin accounts.
- Turn on versioning and soft-delete where your platforms offer it.
- Monitor for mass-deletion and encryption so you catch it early.
A penetration test that reaches your backup and admin planes tells you whether an attacker could actually destroy your recovery options, which is the failure that turns an incident into a catastrophe.
References
- [1]Data Destruction (Technique T1485)(MITRE ATT&CK)
- [2]StopRansomware(CISA)
- [3]Computer Security Resource Center Glossary(NIST)
Destruction is the one threat you recover from rather than prevent. Protect the recovery: keep a copy your attacker cannot reach, and prove you can restore it.