An independent information publicationDirective (EU) 2022/2555 · The NIS2 DirectiveNot an official publication
The Independent NIS2 Desk
NIS2 Compliance
Independent information on the NIS2 Directive, for the organisations it covers.
HomeArticlesOffline and Immutable Backups Under NIS2
Business Continuity / 2026-10-09

Offline and Immutable Backups Under NIS2

Offline and immutable backups are two ways to reduce the risk that an attacker or operational mistake destroys recovery copies. They can support the backup management duty in Article 21(2)(c), but NIS2 does not establish a universal requirement to deploy both technologies for every entity.

Offline and immutable are different properties

An offline copy is disconnected from ordinary production access for at least part of its lifecycle. An immutable copy is protected from modification or deletion during an established period by configured storage controls. Some immutable systems remain online, and some offline media can be overwritten after reconnection.

Do not assume that the presence of either label proves resilience. Assess who can shorten retention, change policy, compromise credentials or access the physical media.

Choose protection based on threats and service needs

Map critical data and systems to realistic threats: ransomware, privileged account misuse, storage failure and site disruption. Decide which recovery copies need stronger isolation and how that decision affects restoration speed.

A removable copy stored offsite may reduce exposure to a compromised network but take longer to retrieve. An online immutable copy may restore faster while depending on cloud account security and reliable retention settings.

Design for integrity and accessibility

Verify encryption, key escrow or recovery procedures, storage health and inventory accuracy. Document the process for authorising the restoration of a protected copy. Restrict retention-policy changes and log privileged operations.

Protection should extend to application configurations, identities and supporting infrastructure where their loss would stop the recovery of critical services.

Test under adverse conditions

Exercise a scenario in which production administrators cannot authenticate or the primary backup console is inaccessible. Restore into a separate environment and verify both the age and integrity of the recovered information.

Measure elapsed restoration time and actual data loss against approved RTO and RPO values. Document failures, owners and corrective measures, including whether historical copies can be located without production records.

Record scope and review decisions

Keep the selection rationale, protected-system inventory, retention settings, administration roles, monitoring and restoration evidence. Reassess after changes to architecture, suppliers or the organisation's risk profile.

The general Directive is supplemented by Member State law and, for specified provider types, Implementing Regulation (EU) 2024/2690. Controls should be justified against the applicable requirements rather than promoted as universally compulsory.

Questions on the text

Are offline backups and immutable backups the same?

No. Offline refers to connection and access, while immutability refers to protection against changes during a specified period.

Does immutability guarantee recovery?

No. Copies can be incomplete, unusable or dependent on unavailable keys or systems. Restoration testing remains necessary.

More from the Desk

The texts relied on

General editorial guidance only: it does not determine your organisation's legal obligations. See our editorial policy for how this site works and corrects errors.