Definition of immutable backup
An immutable backup is a copy of data which, once written, can be neither modified nor deleted before the end of a retention period set in advance. The prohibition applies to administrator accounts themselves. An ordinary backup, by contrast, can be erased with sufficient rights.
This definition reflects common usage, drawn from the vocabulary of operations teams and vendors. The acronym WORM (write once, read many) refers to the same principle. Immutability applies to the copy, not to its content. An immutable backup faithfully preserves what it received, corrupted data included.
What a locked copy protects
An attacker who has taken control of an administrator account can encrypt production data, then erase the backups that account can reach. A handling error or a malicious insider act can have the same effect. In these scenarios, the locked copy keeps a restore point that has remained out of reach of those accounts.
It therefore helps to meet the maximum tolerable data loss, one of the two objectives in our RTO RPO entry. The recovery time depends on the procedure and the restore environment provided for in the disaster recovery plan.
The DORA Regulation, Regulation (EU) 2022/2554, and the NIS2 Directive, Directive (EU) 2022/2555, deal with backups without using the word “immutable”. Article 12 of the former requires financial entities, outside the simplified framework of its Article 16, to have backup policies and procedures, tested periodically. Article 21 of the latter lists “backup management” among the business continuity measures.
Immutability mechanisms
Usage distinguishes three families of mechanisms.
| Mechanism | What prevents deletion | Point of attention |
|---|---|---|
| Non-rewritable medium (WORM tape or disk) | The hardware | Physical custody of the medium |
| Object lock in object storage | The service, until the end of retention | The lock mode chosen |
| Locked snapshot on a storage array or in backup software | The system, until expiry | Access to the system’s own console |
The degree of immutability is set out in the provider’s documentation. Amazon S3’s documentation distinguishes a “governance” mode, which accounts with a special permission can lift, and a “compliance” mode, in which no user, root account included, can overwrite or delete the protected object version before expiry. Azure Blob Storage’s documentation describes time-based retention policies and legal holds, lifted by explicit decision.
The retention period is chosen with regard to how long an intrusion may take to be discovered: if it is too short, it may leave only copies made after the compromise. The locked volume is paid for until expiry.
Immutable backup, replication, offline copy, archiving: not to be confused
Replication copies every change to a second site, malicious encryption included.
An offline copy is protected by its isolation: it cannot be reached from the network. Immutability protects a copy that has stayed online. The two can be combined.
An ordinary snapshot and versioning keep earlier states, which an account with sufficient rights can purge.
Archiving aims at preserving documents over time. Immutable backup aims at restoring a system.
Example: a mutual insurer’s backups
Take a mutual insurer whose backups are written to the cloud account that hosts production. The operations team checks one point: a production administrator can delete them.
It then moves the copies to a separate account, under different access rights, and enables object lock. It chooses the mode that no account can lift, after agreeing the retention period with the business and estimating the cost of the volume retained. It finishes with a test: restoring a locked copy into an empty environment and measuring the duration.
The place of these backups in the business continuity and disaster recovery plans is described on our cyber resilience page.