Skip to content
Technology transformation expertise firm · ARDIANE Group Innovate, secure, succeed

Glossary

Immutable backup: definition, mechanisms and limitations

Domain

Cloud and platforms

In brief

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, including by an administrator account. It preserves a restore point when production and ordinary backups have been encrypted or erased.

Page contents

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.

FAQ

Frequently asked questions

Another question? Ask us

What is an immutable backup?

An immutable backup is a copy of data that can be neither modified nor deleted before the end of a retention period set in advance. The prohibition also applies to administrator accounts, which is what distinguishes it from an ordinary backup. The acronym WORM (write once, read many) refers to the same principle.

Does an immutable backup protect against ransomware?

An immutable backup is designed to prevent ransomware, or the attacker controlling it, from encrypting or erasing the locked copy. It protects neither against data theft nor against backing up a system that is already compromised, which the copy preserves as it is. Its usefulness is proven by a restore test, whose duration is compared with the recovery objective.

What is the difference between an immutable backup and an offline backup?

An offline backup is protected by its isolation: the medium, for example a tape taken out of the tape library, cannot be reached from the network. An immutable backup stays online, and it is the storage system that refuses its modification and deletion until the expiry date. The two protections can be combined, the offline copy also covering compromise of the storage system itself.

Does the DORA Regulation require an immutable backup?

Regulation (EU) 2022/2554, known as DORA, does not use the word "immutable". Its Article 12 requires financial entities, outside the simplified framework of Article 16, to have backup policies and procedures, periodic testing and, where they restore using their own systems, systems that are physically and logically segregated from the source system. Immutable backup is one of the technical means of protecting copies, to be assessed against these requirements and the technical standards that specify them.

A project to bring to completion?

A first conversation is enough to understand your challenge, identify the right people and tell you frankly what we can bring.