GUIDE EUROPE · DIGITAL SOVEREIGNTY

Why immutable storage should sit under European jurisdiction

Backups are often the first target of ransomware, so they must stay intact even when administrator credentials are compromised. Immutability blocks deletion for a set period, but location and jurisdiction are separate questions: a provider with European data centres may still be subject to foreign law. This guide explains how to design a backup that holds up, compare storage options and test restores before you rely on them.

Updated october 2026
8 min read
Altovar Technical Editorial Team

1. Why backups are the first target

A modern ransomware attack does not stop at encrypting users' computers. It often goes after backup systems first, because they are the only way to restore data without paying. If backups are connected to the network with the same credentials as the servers, an attacker who gains administrative access can delete or encrypt the copies too. At that point the backup stops being a protection and becomes a target.

That is why the question is not only how much space you need, but how long data stays intact and who can change it. Two aspects must be kept apart: the technical protection against deletion, known as immutability, and the choice of the physical and legal location where the data is kept. Confusing the two leads to poor decisions. A sound design treats them as separate questions from the start.

2. What immutability means

Immutability is a protection that prevents an object from being modified or deleted for a set period, even by someone holding administrative credentials. In object storage it is often implemented with the WORM model (Write Once, Read Many) and with a feature called Object Lock, which blocks deletion until the retention period expires.

The limitation is that immutability only works if it is configured properly. A retention period that is too short may expire before an attack is discovered. A configuration that allows the protection to be switched off with the same administrative credentials offers no real protection. Always ask how it is set up, who can change it and how it is verified over time. A setting that nobody has checked for months can be changed without anyone noticing.

3. Physical residence and jurisdiction: two different questions

Data location indicates where the disks physically sit. Jurisdiction indicates which law can require the operator of the service to give access to the data. A provider based outside the European Union can be reached by the laws of that country even if the data is held in Europe. Conversely, a European provider may have staff or subcontractors in other countries. For this reason, the word Europe alone does not settle the matter.

The statement that backups must sit under European jurisdiction should be read carefully. It is not a universal rule that applies to every company. It depends on the type of data, the sector and contractual obligations. For personal data, the GDPR governs transfers to third countries and requires appropriate safeguards. Regulated sectors may have specific requirements. The choice must be justified and documented.

4. Four storage options compared

Companies choose between very different solutions. The table compares four options on three criteria: immutability, residence and jurisdiction, and the risk of access by third parties. The assessments are qualitative and should be verified with the provider for your specific case, because characteristics vary between products and contracts. Use the table to prepare your questions, not to reach a conclusion without checks. Ask for a copy of the terms and conditions currently in force.

No option is best in absolute terms. An offline copy held on site protects against remote attacks, but it requires manual procedures and can be compromised by a physical incident. A second site you own offers control, but requires investment and management. An external service simplifies management, but shifts the assessment to contractual guarantees. Here too, you need oversight of subcontractors and of the conditions for access.

OptionImmutabilityResidence and jurisdictionRisk of third-party access
Offline media on siteHigh, if the media is disconnectedThe company's premisesLow from outside, high for theft or fire
Immutable object storage from a provider based in the EUHigh, if configured with Object LockEuropean, with subcontractor checksTo be assessed in the contract and across subcontractors
Immutable storage from a provider based outside the EUHigh, if configured correctlyData in Europe can remain subject to foreign lawsHigher, because the provider's jurisdiction matters
Second site you ownDepends on the tools chosenDirect choice by the companyControlled, but must be managed with care

5. How to design a backup that holds up

A resilient backup does not depend on a single tool but on an architecture. The 3-2-1 rule provides a useful basis: three copies, on two different media, with one copy off site. Add immutability to at least one copy and separate the credentials, so that whoever administers the servers cannot also delete the backup. The principle is simple: whoever can change the servers must not be able to change the copies too.

For each step, a verifiable check is worth having. Backup credentials should be held in a separate system protected by strong authentication. Restores should be tested in a test environment, with the time taken measured. A backup that takes a week to restore may not match the downtime the business can tolerate. Restore time should be measured in a real test, not estimated on paper.

  • Three copies of the data, on two different media, with at least one copy off site.
  • Immutability with a defined and documented retention period.
  • Backup credentials separate from server credentials and protected with multi-factor authentication.
  • An offline or disconnected copy, updated through a regular procedure.
  • A restore test in a test environment, with the time measured and the outcome recorded.
  • Monitoring of backup jobs, with an alert when a job fails.
  • A document stating who can change the configuration and how changes are approved.

6. Common mistakes in backup storage

The first mistake is believing that immutability alone is enough. If an attacker obtains the same credentials that can disable the protection, the backup remains vulnerable. The second is setting a retention period that is too short, assuming it will cover the time needed to discover an attack. The third is confusing the existence of a copy with the ability to restore it.

The fourth mistake concerns jurisdiction. Choosing a provider simply because the data sits in a European data centre, without reading the contract, the subcontractors and the access conditions, is an incomplete decision. The fifth is failing to revisit the assessment when the provider, its location or its subcontractors change: a choice that was right two years ago may no longer be right today. Contracts should also be re-read when the structure of the service changes.

7. Getting started: the first concrete step

The first step is to establish which data must be restorable and within what timeframe. List the critical systems, the maximum downtime the company can tolerate and the amount of data it can afford to lose. These two figures, to be agreed with management, drive all the technical choices that follow. Without agreement on these values, the technical choice has no criterion behind it.

Then check your current architecture against the 3-2-1 rule and the separation of credentials. Ask your current provider, or the one you are evaluating, how immutability is configured, who can disable it and where the copies are held. Carry out at least one complete restore test and record the result: it is the first concrete evidence of the real level of protection. Note the time taken and the problems encountered, as they will be needed for the next test.

Frequently Asked Questions

Must backups legally be held in Europe?

There is no general obligation that applies to every company. Rules exist on transfers of personal data to third countries, and specific requirements apply to some regulated sectors. The choice of location should be justified on the basis of your data and contractual obligations. For a specific case, ask your legal adviser for an opinion.

Are Object Lock and WORM the same thing?

They are closely related concepts. WORM describes the write-once, read-many model. Object Lock is the feature that many storage systems use to apply this principle to specific objects, blocking their deletion for a period. Check in the specific product how it is activated and whether it can be switched off.

How long should the immutability period last?

It depends on your retention policy and on the time needed to discover an attack and restore the data. A period that is too short does not protect well. Define it with the data owner and with the people responsible for security, taking into account the retention requirements in your sector.

Is an offline backup still needed if I have immutable storage?

In most cases it is worth having. Immutable storage protects against deletion over the network, but a disconnected copy also protects against compromises that affect the entire connected environment. The two solutions complement each other and address different threats. Choose media that you can disconnect and physically verify.

How do I tell whether my backup provider is reliable?

Ask how immutability is configured, who has administrative access, where the data and the subcontractors are located, and what contractual guarantees apply in the event of an incident. Insist on a documented restore test. A clear and verifiable answer is worth more than a generic promise.

About this content

General informational guide. Regulations and technical requirements change over time: always check the official sources and assess your specific case with a qualified technical or legal advisor.

GET IN TOUCH

Talk to our team.

We'll show how Altovar integrates into your infrastructure. No commitment, no sales pitch. Just a technical conversation.

BOOK A DEMO →