Infrastructure
Snapshot deletion
Snapshot deletion, recovery-point destruction
Attackers remove snapshots or recovery points to make restoration after an incident more difficult.
Fiche de sensibilisationPrête à diffuser à vos équipes ou clients
MIGHT YOU BE AFFECTED?
Turn knowledge into action.
How does this work?
Compromised management privileges can allow mass deletion of snapshots, shortened retention settings or disabled alerts before destructive attacks such as ransomware.
REAL-WORLD EXAMPLE
« Before encrypting virtual machines, an attacker deletes available cloud snapshots and disables backup notifications. »
Typical sequence
- 1An attacker obtains privileged access to backup or cloud management.
- 2They enumerate existing snapshots and recovery points.
- 3Snapshots are deleted or retention and alerting settings weakened.
- 4The attacker carries out a destructive operation with fewer recovery options remaining.
Warning signs
- Numerous snapshot deletion operations in a short period.
- Unexpected retention-policy or backup configuration changes.
- Backup alerts or logging suddenly disabled.
- Administrative identities performing unusual recovery-system operations.
How to protect yourself
- Require MFA and separate approval for destructive backup actions.
- Maintain immutable or locked backups beyond ordinary administrator control.
- Use separate identities for backup and production management.
- Monitor snapshot deletion and regularly test independent restoration.
If you think you are affected
Disable compromised management identities and immediately protect all remaining recovery copies. Preserve audit logs, assess which restore points survive and verify their integrity before planning recovery.
Last updated: 8 October 2026