Glossary

Immutable backup

Definition

A backup protected against alteration or deletion for a defined period.

Immutability prevents a protected backup from being changed or removed during its retention period. It does not establish that the backup is complete or safe to restore.

A customer may include “Immutable backup” in a supplier security questionnaire or spreadsheet. They want to understand whether this topic affects the service you provide and what safeguards or evidence support your answer.

An immutable backup is protected against changes or deletion for a defined period. The aim is to preserve a recovery copy even if an attacker, a faulty script or an administrator tries to remove it. The protection is a property of the storage and its configuration, not simply a label on a backup product.

For example, a small software company could keep protected daily database copies for a set recovery window. If an intruder deletes the live database and ordinary backups, a locked copy may remain available. The company still needs the credentials, keys and instructions required to restore it.

Immutability has limits. It can preserve incomplete or already compromised data. It may also increase storage costs because protected copies cannot be removed early. Some systems offer modes that privileged administrators can override; others enforce a retention period more strictly. Those differences matter when administrator compromise is the threat.

Check which copies are locked, for how long, who can bypass the lock and whether backup credentials are separate. Test restoration regularly; immutable and offline copies reduce different failure paths. Check whether encryption keys could be deleted independently. An immutable online copy and a disconnected offline copy use different methods, and neither removes the need to test restoration.

Sources

Amazon S3: Object Lock and retention modes

Amazon S3: Object Lock considerations