Data Sovereignty and Recovery: The Two Pillars of Security
NIS2 and ransomware push companies to change their mindset: it’s not enough to protect data, you must be able to recover it quickly and without compromises.
When cybersecurity enters the realm of operational continuity, the issue is no longer just about preventing intrusion: it’s about being able to restart. The combination of regulatory pressure and the rise of ransomware attacks is forcing businesses, healthcare, and public administrations to face a very concrete question: if systems are compromised, how long does it take to become operational again?
In this scenario, data sovereignty and reliable recovery are not two separate topics. They are two sides of the same strategy: controlling where information resides, who can access it, and how it is protected; but also ensuring that healthy, isolated, and verifiable copies truly exist when needed. Resilience today is measured on both fronts.
NIS2 Shifts Focus from Protection to Resilience
The NIS2 directive requires risk management measures that explicitly include operational continuity, backup management, and disaster recovery. The message is clear: security is not just about preventing attacks, but must also cover service restoration after an incident. For regulated entities, this means formalizing plans, roles, recovery priorities, and periodic checks, rather than relying on “implicit” procedures.
The impact is particularly strong for healthcare and public administration. These sectors cannot afford long downtimes or improvised restorations, because a blocked infrastructure does not only cause technical disruption: it can interrupt treatments, reports, appointments, administrative workflows, and, in the worst cases, essential services for citizens.
Immutable Backups: The Difference Between a Copy and True Defense
Many organizations believe they are covered because they “have backups.” But in a ransomware scenario, the real question is different: can those backups be altered, encrypted, or deleted along with the primary systems? If the answer is yes, the defense plan is incomplete.
Immutable backups solve exactly this problem: once written, they cannot be modified for a certain period. If you add offline copies or copies isolated from the production network, the organization drastically reduces the risk that the attacker also compromises the recovery capability. This is a technical step, but above all a strategic one: it transforms backup from a passive archive into a resilience control.
However, backup quality is not measured only by the presence of a copy. What matters is the ability to restore. If tests are not regular, if restore times are not compatible with the business, if priorities are not defined, protection remains theoretical. A credible plan must demonstrate that data can become usable again, not just that a copy exists.
Data Sovereignty: Control, Trust, and Dependence on Providers
Talking about data sovereignty does not only mean choosing where to host information. It means being able to govern the entire cycle: location, access, encryption, retention, separation of administrative domains, and the ability to exit a provider without losing operational continuity. In regulated sectors, this issue becomes even more relevant because dependence on external platforms can turn into a systemic risk if not accompanied by exit and recovery architectures.
Here two needs often treated separately intersect: compliance and operations. A compliant but unrecoverable solution is weak. A recoverable but unmanaged solution is equally fragile. Companies must therefore design environments where security, portability, and restoration are conceived together from the initial architecture.
What Companies Need to Do Now
The real leap forward is not buying a new tool, but building an operational discipline. The most mature organizations are already working on realistic attack scenarios, with drills, restore tests, and checks on critical dependencies. This is the point where security becomes measurable.
- Define which data and services have restoration priority, with RTO and RPO consistent with the business.
- Adopt immutable backups and isolated copies, to prevent attackers from destroying recovery as well.
- Really test restoration, not just the existence of backups.
- Reduce dependence on a single provider, planning exit and continuity scenarios.
- Align security, compliance, and operations, because NIS2 requires governance, not isolated solutions.
In summary, the lesson is simple but demanding: modern security is not measured only by the ability to prevent an attack, but by how quickly a company can recover when the attack actually happens.