An IT stack can remain in use for years after the assumptions behind its design have changed. A service becomes unavailable in a market, a transfer arrangement needs review, or a supplier faces restrictions that affect support and updates.
As an IT leader, I want those possibilities considered alongside cost, performance and the team’s ability to operate the system. I cannot predict the next policy change. I can ask which dependencies would be difficult to replace and what the organization would do if one became a problem.
That leads to a more useful architecture discussion than trying to label a whole vendor or country safe or unsafe. The answer depends on the workload, its data, the contract and the alternatives available.
Data location and legal jurisdiction are different questions
For a European organization, the GDPR’s international-transfer requirements are part of that assessment. They allow transfers under defined conditions, including adequacy decisions and appropriate safeguards. They do not impose a general requirement that all EU personal data stay in the EU. The European Commission’s guidance on international transfers is a useful starting point for identifying the applicable mechanism.
The consequences of getting that assessment wrong can be substantial. In May 2023, Ireland’s Data Protection Commission announced a €1.2 billion fine against Meta Ireland over the transfer arrangements examined in its Facebook inquiry. That was a decision about those arrangements, not a blanket ruling against every transfer to the United States.
Storage in Europe also does not answer every question about access. The U.S. Department of Justice’s CLOUD Act explanation describes obligations on providers subject to U.S. jurisdiction to respond to valid legal process for data in their possession, custody or control, regardless of storage location. The relevant analysis includes jurisdiction and control over the data, rather than the address of the data center alone.
I would therefore assess where the data is stored, where it is processed, who can access it and which legal entities provide the service. Those answers may differ for support, backups, telemetry and integrations. They belong in the review before a data-residency promise is passed on to customers.
Regional requirements need a specific assessment
China also needs a specific assessment. Its March 2024 regulations on cross-border data flows include thresholds and exemptions for particular transfer scenarios. Whether a transfer is permitted depends on the applicable rules and circumstances.
A company operating across jurisdictions needs to establish which rules apply to its entities, data and processing. Sometimes that will require separate regional services or restricted flows. Sometimes a transfer is possible under the relevant conditions. Both the legal assessment and the design should be specific enough to explain which case applies.
Separate environments also have costs. They can create duplicated operations, reporting gaps and inconsistencies between records. Those consequences need to be included when deciding where to isolate a workload or a dataset.
Technology supply can be restricted as well
The U.S. Bureau of Industry and Security’s October 2023 package of semiconductor controls illustrates how access to advanced computing hardware and manufacturing equipment can depend on destination, end use and the parties involved.
For an IT team, the practical concern extends beyond the initial purchase. Can the supplier continue to deliver replacements, updates and support in the places where the organization operates? What would happen if it could not?
I would identify critical dependencies before deciding where a second supplier is justified. Spare hardware, an approved alternative product or a tested recovery option may be appropriate for one system. Another may be cheap enough to replace when needed. The response should follow the consequence of losing the component and the time available to recover.
Open-source software belongs in this review too. Access to source code can make replacement or independent maintenance more feasible, but a project may still depend on a small group of maintainers, a hosting service or a commercial support provider. I want to know how updates would continue if that arrangement changed.
What a sovereign cloud can and cannot settle
A sovereign-cloud offering may provide useful controls over location, operations, access and the legal entity delivering the service. I would evaluate those controls individually, against the workload’s requirements.
The label alone does not establish compliance or immunity from another jurisdiction’s legal demands. Nor does it establish that the application can move easily to another provider. The contract, operational arrangements and technical design need to support the particular assurance being made.
The questions I would take into a review are concrete. Who operates the environment and can access its data? Who controls encryption keys? Which services or support processes sit outside the stated boundary? What evidence is available? What happens if the provider changes the service or ends the agreement?
A local or sovereign provider may be a good fit for a sensitive workload. A global platform may be appropriate for another. The architecture should make that choice deliberate and document the remaining dependencies.
Keep exit options proportionate to the risk
Vendor concentration can make an organization easier to operate. One platform, a familiar set of controls and a team that understands it have real value. That concentration also makes some failures or restrictions harder to work around.
A multi-cloud strategy is one possible response, but a second provider does not automatically create a working exit. Applications may depend on managed databases, identity services, networking, proprietary APIs and operational practices that do not transfer with a container image. Data movement and contractual constraints can take longer to resolve than deployment.
I would choose the systems that need a credible alternative and test those alternatives. For other workloads, documented recovery steps, usable exports and a realistic replacement plan may be sufficient. Running everything on two platforms can add cost and complexity without addressing the most important dependency.
The same reasoning applies to modularity. Clear interfaces and portable data formats can reduce the work involved in replacement. They are useful where a component is likely to change or where losing it would be costly. Abstracting every service in advance can leave the team maintaining infrastructure it never needs.
Put the assumptions through an exercise
For a critical system, I would ask the team to work through a loss-of-service scenario. Assume a provider can no longer serve one of the organization’s markets. Which data can be exported? Which functions must continue? Who can authorize the move, and where could the system run?
Then test enough of the plan to find the difficult parts. Restore a usable dataset. Check an alternative integration. Verify that the receiving environment has the required permissions and operational support. Record the work still needed and the time it would take.
The exercise should include legal, procurement and the people operating the service. A technically feasible migration can still be blocked by a license, a data-transfer issue or the absence of someone able to support the replacement.
I would also assign responsibility for watching material policy and supplier changes. The team needs a route from new information to a decision about the affected systems. A list of risks that nobody owns will not help when a condition changes.
Give the board a decision it can assess
In my experience, these investments are easier to discuss when they are tied to continuity and a specific exposure. What happens if the dependency fails? How long can the business tolerate it? What does a credible alternative cost to prepare and maintain?
That makes it possible to choose between reducing a risk, accepting it or changing the scope of the service. It also avoids presenting maximum independence as a goal without accounting for its cost.
I would leave the discussion with an owner for each material dependency, the recovery or exit option chosen, and the assumptions that should trigger another review. Those are things the organization can act on when the circumstances change.
