What NIS2 Says About Backups
Article 21(2)(c) names backup management within business continuity, alongside disaster recovery and crisis management. The Directive provides a proportionate risk-management framework rather than a universal requirement for a particular backup product or the same retention period across organisations.
Some digital infrastructure and ICT providers are also subject to the detailed backup and redundancy provisions in the Annex to Commission Implementing Regulation (EU) 2024/2690. Those more specific provisions must not be described as binding identically on every covered sector.
Identify What Must Be Recoverable
Critical data includes more than business records. Configuration files, system images, cryptographic key recovery arrangements and information held in cloud environments may be necessary to restore an application. Map backups to the dependencies identified in the business impact analysis.
Define recovery point objectives with service owners. A daily copy may be inadequate for a service that cannot tolerate losing a full day of transactions, while continuous replication alone may reproduce corruption or malicious changes.
Protect Against Shared Failure
Separating protected backup copies from production accounts and networks reduces the chance that a single compromise destroys both. Apply access controls, monitor administrative activity and consider offline or immutable copies where the threat model warrants them.
Encryption protects confidentiality but does not by itself guarantee recoverability. Key management and recovery permissions must survive the same scenario the backup was designed to address.
Prove Restoration Works
Test representative restoration of data, configurations and complete services. Verify integrity and actual time to resume a useful operation, not merely whether backup software reports success. Document any prerequisite systems needed for recovery.
Test after important architecture changes and significant backup failures. Capture dates, systems, scope, results, measured recovery times, limitations and owners for remediation. Recovery exercises should avoid inadvertently overwriting production data.
Govern Retention and Supplier Responsibilities
Retention should reflect service needs, legal obligations and the risk of retaining sensitive information longer than necessary. Where a cloud or managed service provider performs backup tasks, establish who defines the policy, who executes jobs, who holds keys and who can initiate restoration.
A contract promising backups is not evidence that a particular system can be restored to an acceptable point in time. Confirm the service boundaries, retrieve meaningful evidence and periodically revisit the assumptions.
Connect Backup Evidence to Continuity Plans
Keep an inventory of protected systems, backup schedules, monitoring results, exceptions and restoration test records. Align the backup strategy with crisis escalation and disaster recovery sequencing.
Check the implementing law and competent authority guidance that apply to the entity. A backup programme should evolve as services, threat exposure and technical dependencies change.
Questions on the text
Does NIS2 require immutable backups for all entities?
The Directive does not state a universal immutable-backup requirement for every covered entity. Appropriate protection depends on risk and any more specific applicable rules.
Do successful backup jobs satisfy NIS2 on their own?
No. Recoverability, protection of copies, service dependencies and evidence of effective restoration also matter.