What is an immutable backup?

An immutable backup is a backup copy stored in a write once, read many (WORM) state, so it cannot be changed, overwritten or deleted until its retention period ends. The storage system enforces the lock, so it holds even when the backup software or an administrator account is compromised.

Why are backups locked?

Backups are how an organization recovers from ransomware without paying, so attackers go after them before encrypting working data. With stolen administrator logins they delete restore points or shorten retention, which is backup tampering. A locked copy keeps a way to recover even when the backup software is under the attacker's control.

How do WORM locks work on storage?

Under the WORM model, data is written once and can then be read any number of times, but not altered or removed while its retention period runs. A change creates a new version and leaves the locked one in place. On object storage this comes from S3 Object Lock: the backup software sets a retention mode and a retain-until date on each object version as it writes it, and the storage refuses any request to delete or overwrite that version before the date, whichever credential sends the request.

Governance and compliance modes

PropertyGovernance modeCompliance mode
Who can remove the lock earlyUsers granted a special bypass permissionNo one, the account owner included
Can retention be shortenedYes, by those usersNo, only extended
What it guards againstAccidental deletion and ordinary usersAny account, including a stolen administrator login

A lock that a stolen login can lift does not protect against a stolen login, which is why ransomware protection relies on compliance mode or an equivalent.

How far back do locked copies reach?

Retention has to outlast the time it takes to notice an intrusion, find a clean copy and restore it. If attackers sit inside for weeks, restore points locked for days were all taken after the intrusion began. Longer locks also mean more data kept, since locked copies stay until their date even when the backup software would have expired them sooner.

What immutability leaves open

Immutability stops changes, not reading. A locked copy can still be copied out, so access controls and a logical air gap remain separate protections. It also preserves whatever was backed up: if ransomware had already damaged files when a backup ran, the locked copy holds the damage, and restore testing is what shows whether locked copies recover cleanly and in time.

Frequently asked questions

Is an immutable backup the same as an air-gapped backup?

No. An air gap keeps a copy out of reach of production, while immutability keeps a copy that can be reached but not changed. Many designs use both.

Can an immutable backup be deleted?

In compliance mode, no one can delete it before the retention date. In governance mode, a user with a special bypass permission can remove the lock.

Do immutable backups use more storage?

Yes. Locked copies stay in storage until their retention date, even if the backup software would have expired them sooner.