For years, organisations treated the location of their data as an operational detail. Choose a cloud region, put the right contracts in place, secure the environment and move on. However, that approach is becoming harder and harder to sustain.
As governments tighten rules around privacy, critical infrastructure and cross-border data transfers, organisations are increasingly being asked to understand not only how their data is protected, but where it resides, who can access it, how it moves and which jurisdictions have authority over it.
For regulated sectors such as financial services, healthcare, government and critical infrastructure, data sovereignty is no longer simply a legal or compliance concern. It is becoming an architectural one.
Residency is only part of the picture
Data residency, localisation and sovereignty are often used interchangeably, but they describe different things. Data residency is about where information is physically stored. Whereas data localisation refers to legal requirements that certain information remain within a country or region, or that specific conditions are met before it can be transferred elsewhere.
Data sovereignty goes even further. It considers the laws that apply to the data, the organisations controlling it and the circumstances under which access may be required. That distinction matters because storing information in a local data centre does not automatically resolve every sovereignty concern.
Organisations also need to know who operates the infrastructure, where administrators are based, who controls encryption keys, which third parties have access and whether data can be replicated or transferred into another jurisdiction.
In distributed cloud environments, several jurisdictions can potentially touch the same workload. Organisations therefore need visibility and control across the full data lifecycle, not simply confidence in where a server happens to be located.
A regulatory map that keeps changing
There is no single global model for data governance. In Europe, the General Data Protection Regulation (GDPR) continues to shape how personal data can be transferred internationally, while legislation such as the Digital Operational Resilience Act (DORA) and the NIS2 Directive has increased scrutiny of operational resilience, cybersecurity and third-party risk.
Other markets take different approaches. China maintains controls over certain categories of data and cross-border transfers, while India’s data protection framework continues to develop following the introduction of its Digital Personal Data Protection Act and subsequent rules.
Many other countries are also introducing localisation, privacy and sector-specific requirements, particularly around financial, government and critical infrastructure data.
For multinational organisations, the result is a regulatory map that is fragmented and constantly evolving. Infrastructure that satisfies requirements in one country may not be appropriate in another, and architecture that is compliant today may need to operate differently as rules change, which means flexibility is increasingly important.
Compliance is moving upstream
Historically, compliance could often be addressed relatively late in the technology procurement process. An organisation might select its preferred platform and cloud environment, then determine which region should host the workload and what contractual safeguards were required.
That sequence is becoming harder to justify. If a new rule requires certain information to remain within national borders, restricts who can access it or introduces stronger audit requirements, the underlying infrastructure must be capable of adapting.
If it cannot, organisations may be forced to duplicate systems, introduce additional security layers, redesign data flows or maintain separate versions of an application for different markets. Those workarounds add cost and complexity, as well making the next regulatory change even harder to absorb.
The challenge, therefore, is not simply complying with the rules that exist today. It is in building infrastructure that can respond as those rules evolve.
The questions technology leaders should be asking
For organisations evaluating databases, cloud platforms and wider data infrastructure, geography is only the starting point. Deployment flexibility is one of the first considerations that should be explored. Can workloads run in a public cloud region, private infrastructure, on-premise environment or sovereign cloud without requiring major application changes?
Control over encryption is another. Encryption at rest and in transit is now standard, but organisations increasingly need to understand who controls the keys themselves and whether the infrastructure provider can access the underlying information.
Access controls also need to be sufficiently granular. A global organisation may want employees in several countries to use the same application, while restricting access to particular records or sensitive fields according to geography, role or regulatory status.
Auditability is equally important. Regulators, customers and internal risk teams increasingly expect organisations to demonstrate how controls operate, rather than simply state that they exist. Technology leaders must therefore be able to answer questions such as:
● Where is our data stored, processed and replicated?
● Who can access it, and under what conditions?
● Who controls the encryption keys?
● Can access rules vary by jurisdiction, role or data type?
● Can we produce a clear and exportable audit trail?
● How quickly could we respond to a new localisation requirement?
These are no longer simply security questions. They affect procurement, application design, cloud strategy and operational resilience.
Designing for a moving target
There is little sign that data sovereignty will become simpler. Governments want greater control over sensitive and strategically important information. Regulators are paying closer attention to international transfers and third-party risk.

At the same time, businesses are moving more data across borders through cloud services, globally distributed applications and AI systems.
The organisations best placed to manage that tension will be those that treat sovereignty as a design principle rather than a compliance exercise carried out after infrastructure decisions have already been made.
The key question is no longer simply whether data is secure. Organisations increasingly need to know where it is, who can access it, which rules apply to it and how quickly those answers can change when the regulatory environment does.
By Mani Nagasundaram, VP, Financial Services, MariaDB plc.
- Cybersecurity in FinTech
- Data & AI
- Fintech & Insurtech
- Infrastructure & Cloud









































