Why ransomware threatens recovery
Attackers may seek backup administration credentials, remove restore points or encrypt accessible storage before disrupting production. Replicated data may also contain malicious changes. A backup status dashboard showing completed jobs does not demonstrate that independent and trustworthy copies remain available.
Prioritise systems whose prolonged outage would interrupt covered services. Identify whether common identity infrastructure, privileged accounts or network access could allow the same attacker to reach both production and backup environments.
Separate privileges and recovery paths
Use dedicated backup roles and narrowly scoped permissions. Protect administrative accounts with strong authentication and review who can delete backup sets, change retention or disable monitoring. Separate critical recovery credentials from systems likely to be unavailable during an incident.
Separation can be organisational as well as technical. When a supplier operates the backup platform, establish which party controls privileged access and who can authorise emergency restoration.
Maintain recoverable copies
Consider offline or immutable backup copies according to the threat model and service requirements. Test retention controls rather than relying on product descriptions. Encryption supports confidentiality, but access to required keys must survive a compromise.
Evaluate how long protected historical copies are retained, which systems they cover and how quickly they can be retrieved. If attackers have been present for weeks, the newest available restore point may already be contaminated.
Restore safely after compromise
Recovery planning should coordinate with incident response. Determine which restore points are trustworthy, scan restored systems where suitable and verify identity, network and configuration dependencies before reconnecting services.
A quick restoration into an uncleared environment can recreate the incident. Document the decision to resume service, the validation performed and the remaining risks accepted by responsible management.
Test and document actual resilience
Run exercises that assume primary administration accounts or networks are unavailable. Measure whether operators can access protected copies and meet the agreed recovery time and data loss objectives. Capture failed steps and retest after remediation.
The detailed rules in Implementing Regulation (EU) 2024/2690 apply to specified digital and ICT provider categories, not to all NIS2 entities. Check relevant Member State law and sector guidance before describing any particular technique as mandatory.
Questions on the text
Does NIS2 universally require immutable backups?
Article 21 establishes proportionate continuity and backup obligations, but does not impose one identical immutable-backup technology on every covered entity.
Can ransomware affect replicated backups?
Yes. Replication may also reproduce deletion, corruption or malicious changes, so independent recovery points remain important.