Overview with affiliate links. We receive a commission if you click through via us. Read how
Compare

Data residency and cloud choice: questions for IT teams

This article describes the selection procedure and the questions for providers when requirements apply to data storage in a certain region.

Door de redactie van ClouwinoGepubliceerd Laatst bijgewerkt

Short answer

Data residency in cloud selection means first determining which data may be stored and processed where, and then checking per provider where storage, backups, support and administration take place. The location of storage is not the same as control over access.

Who is it for: IT, security and privacy teams who are selecting a cloud provider for data that is subject to location requirements.

Why is this a selection procedure and not a definition?

What data residency is can be found in the separate explanation of the concept. Here the focus is on practice: how do you turn a requirement into a selection criterion and how do you check it with a provider. That calls for a fixed order, so that the result stays comparable and verifiable.

Whether and how location requirements apply depends on sector, service and region; have it reviewed legally and by your security and compliance team.

Which steps do you go through?

Work from requirement to evidence. This prevents a provider from being chosen on the basis of a general promise.

  1. Classify data: which categories are sensitive or tied to a location?
  2. Record per category which regions and jurisdictions are acceptable.
  3. Make a longlist of providers and have them complete a standard questionnaire.
  4. Verify answers with contract documents, technical documentation and reports.
  5. Test in a trial environment whether region settings are actually enforced.
  6. Record the choice, the assumptions and the reassessment date.

Which questions do you ask a provider?

Bear in mind that storage location is only one component. Data also moves via other routes.

What is the difference between location and control?

Data can be physically in the region while the provider or an administrator falls under a different legal system or has access from another region. Encryption with keys under your own control can help, but does not solve every risk. Assess location, access and legal control separately.

Questions and evidence

Where you can verify the answer to a location question.
TopicQuestion for the providerEvidence
StorageIn which region are data and replicas locatedContract, region settings, test result
BackupWhere and for how long are copies keptService description and configuration overview
Administration and supportFrom which countries is access possibleProcess description, access logs
Sub-processorsWho processes data on behalf of the providerCurrent list and notification procedure
KeysWho manages the encryption keysArchitecture description and key policy

Who is this less suitable for?

Frequently asked questions

How do you check that a region setting is really enforced?

Combine contract terms with technical verification: policies that block other regions, an inventory of resources and periodic spot checks.

What if a provider does not answer a question?

Treat it as an open risk. Ask for written confirmation or choose another solution if the topic is essential to you.

Do development and test environments also have to stay within the region?

If they contain real data, yes. Otherwise use masked or synthetic data, so that the requirement is limited to production.

Ask us
Compare Get in touch

Are you sure?