Immutable Backup

An immutable backup is a backup copy that can't be changed or deleted for a set period, even by an administrator. It protects businesses from ransomware attackers who try to destroy backups before encrypting systems.

IntermediateCategory: Data protection, encryption and privacy

Also called: immutable storage, WORM backup, object lock, air-gapped backup, offline backup

What is an immutable backup?

An immutable backup is written once and then locked so that nobody can modify, encrypt or delete it until a retention period you choose, such as 30 days, runs out. The lock applies to everyone, including administrators and anyone who has stolen an administrator's password.

Why it matters

Ransomware attackers know that good backups mean victims won't pay. CISA's #StopRansomware Guide warns that many ransomware variants try to find and delete or encrypt accessible backups. Attackers often spend days inside a network looking for backup consoles, then wipe backups just before encrypting everything. An immutable copy survives that, because even a fully compromised admin account can't remove it.

How it works

  • Cloud object lock. Cloud storage services such as Amazon S3, Azure Blob Storage and Wasabi offer object lock or "write once, read many" (WORM) settings. CISA's guide notes that some cloud vendors offer immutable storage that protects data without a separate environment.
  • Hardened backup appliances that enforce retention locks in their own operating system, separate from your Windows domain.
  • Offline or air-gapped copies, such as rotated drives or tape stored disconnected. These are immutable in practice because nothing on the network can reach them.

Immutability is one part of a 3-2-1 strategy, not a replacement for it.

What to check when setting it up

  1. Use compliance or governance mode carefully. Some services let a privileged user remove a lock early. A strict mode prevents that but can't be undone, so plan storage costs before you turn it on.
  2. Set the retention period longer than an attacker is likely to hide. Attackers can sit undetected for weeks, so a short lock may expire before you notice.
  3. Protect the backup console with separate credentials and phishing-resistant MFA.
  4. Encrypt the backups so stolen copies can't be read.
  5. Test restores from the immutable copy, not just the local one.

Ask your managed IT or security provider whether your backups are immutable. It is a common question on cyber insurance applications.

Related terms

Sources

  1. #StopRansomware Guide (CISA)
  2. Data Integrity: Recovering from Ransomware and Other Destructive Events (SP 1800-11) (NIST NCCoE)

Drafted with AI assistance, then edited and fact-checked by a person. How we use AI.