Prepare and test your skills
Prepare and test your skills
Data sovereignty, residency, and locality are the rules that decide where regulated data can be stored, where it can be processed, and who can control it. On Google Cloud, architects meet these rules by choosing regional deployment targets and then enforcing them with location constraints, access boundaries, and encryption controls. Cross-border transfer limits and high availability goals directly shape which services and regions remain usable.
Data residency, locality, and sovereignty answer three different compliance questions about the same workload. Data residency describes where Customer Data is stored at rest, such as a specific region or multi-region. Data locality adds where data is processed in use and transmitted in transit, plus where workloads can be accessed from. Data sovereignty adds which jurisdiction governs the data, including which laws apply, which personnel can administer it, and which keys protect it.
| Concept | Core question | Enforced with |
|---|---|---|
| Data residency | Where is data stored at rest? | Resource Locations constraint, regional bucket or dataset location, Assured Workloads (opens in a new tab) folder |
| Data locality | Where is data stored, processed, and accessed? | Regional or zonal services, VPC Service Controls perimeter, Google Cloud Armor geo rules, Identity-Aware Proxy (IAP) |
| Data sovereignty | Which jurisdiction, personnel, and keys control data? | EU data boundary, routing to EU personnel, access approvals, customer-managed encryption keys |
Residency is the narrowest control, while locality and sovereignty build on it for regulated industries. A workload can satisfy residency but still violate locality if it is processed outside its home region, or violate sovereignty if it is administered from outside its jurisdiction. Architects must therefore check storage location, processing location, access location, and administrative control together.
Enforcing location with organization policies and Assured Workloads is how architects prevent resources from being created in the wrong jurisdiction. Organization policies (opens in a new tab) with the Resource Locations constraint define the allowed set of locations for new resources. The constraints/gcp.resourceLocations constraint can be attached at the organization, folder, or project level, and when the policy denies a region, users cannot provision new in-scope resources there.
Assured Workloads packages this enforcement for regulated and sovereign requirements. An Assured Workloads folder applies a selected control package that presets allowed regions and related constraints for every project created inside it. Only resources created inside the compliant folder inherit the protection, so sensitive data with specific residency needs must be placed and kept there. Some resources are out of scope and cannot be restricted, so architects must verify coverage in the supported-services list and Cloud locations catalog.
Enforcement follows an ordered dependency:
This order matters because location is fixed early for some services. In Apigee, for example, the control plane is a global entity by default, data residency is selected only during organization provisioning, and the control plane location cannot be changed later without creating a new Google Cloud project. A mismatched organization policy causes provisioning to fail, such as requiring global when no residency is used or excluding the chosen control-plane region when residency is used.
Designing for locality restrictions and cross-border transfers starts by defining exactly what the regulation limits before choosing services for availability and recovery. The choice of where data rests dictates which services are eligible and which high availability and disaster recovery (opens in a new tab) methods can meet recovery time and recovery point goals. Regionality varies by service, and multi-regional resources are resilient to a regional failure while regional resources are resilient only to a zonal failure and zonal resources fail with their zone.
Define requirements by answering these related questions:
Answers drive concrete tradeoffs between compliance and resilience. If encryption can mitigate the rule, multi-regional and dual-regional services can be used with standard disaster recovery techniques. If processing must stay where data rests, architects use regional Compute Engine deployments across zones, product-specific locality settings such as BigQuery dataset locations, or a hybrid approach with Google Distributed Cloud. A VPC Service Controls perimeter then controls which identities and resources can access the data and which resources can process it.
Access location is controlled separately from storage location. IAP verifies user identity before permitting application access, with domain-restricted sharing limiting which Cloud Identity or Google Workspace domains can appear in Identity and Access Management (IAM) policies. Google Cloud Armor adds IP and geo-based constraints at the edge, while VPC Service Controls provides context-based perimeter security around data and services. For EU workloads, additional sovereign controls include an EU data boundary, support routing to EU persons in EU locations including subprocessors, visibility into administrative access requests, policy-driven access approvals, and custom encryption and key management options.
Shared responsibility for regulated data divides platform protection from customer configuration. Google is responsible for default encryption, infrastructure controls, enforcing the IAM policies the customer sets, and enforcing the selected Assured Workloads or Sovereign Controls for protected data types in configured resources. Google also provides organization policies, resource settings, and Policy Intelligence tools that give insight into access across folders and projects. Customers are responsible for classifying data, placing regulated data inside the correct compliant folders or projects, configuring IAM so only appropriate personnel can access it, and organizing the hierarchy so it does not expose personal data.
This division means a correct policy has no effect if regulated data is stored outside the boundary it protects. Customers must share information prudently during support and troubleshooting and avoid moving regulated data outside compliant folders. Shared responsibility (opens in a new tab) in Assured Workloads and Sovereign Controls (opens in a new tab) follows the same principle: Google protects the platform, the customer controls placement and access.
Residency commitments have a critical handling limit that affects design. Commitments apply to Customer Data at rest for services that can be configured for data location, and Google processes Customer Data in use only within the country of the selected region or the countries of the selected multi-region. If the selected region or multi-region is in the European Union, processing stays within the European Union. Customer Data does not include resource identifiers, attributes, or other data labels, and Service Data such as billing metadata is stored as described in Geography and regions.
Avoid placing sensitive or regulated data in fields that sit outside the technical control boundary:
Exam tip: Data residency commitments cover Customer Data at rest, not resource names, IDs, labels, or Service Data, so never store health information, personal identifiers, cardholder data, or ID numbers in those common fields.
Global privacy and protection frameworks are laws and industry rules that define how personal and health data can be gathered, processed, and stored in the cloud. In Google Cloud, industry rules such as the Health Insurance Portability and Accountability Act (HIPAA) define required security controls, and location rules such as the General Data Protection Regulation (GDPR) define where data must reside. The customer and Google share responsibility for meeting both types of requirements.
The shared responsibility model (opens in a new tab) divides privacy duties between Google and the customer. Google always remains responsible for the underlying network and infrastructure, while the customer always remains responsible for access policies and the data they choose to store. Between those boundaries, customers must understand which controls are their responsibility, which controls are available as part of the cloud offering, and which default controls are inherited.
Inherited controls, such as default encryption and infrastructure controls, are implemented by Google and can be used as evidence of security posture to auditors and regulators. This division means moving a regulated workload to Google Cloud does not transfer legal ownership of compliance to Google. The customer must still configure access, choose regions, and protect sensitive content.
| Framework | Scope | Customer design impact |
|---|---|---|
| Health Insurance Portability and Accountability Act (HIPAA) | United States standards for electronic personal health information (PHI) | Customer must configure controls for PHI on top of Google's HIPAA commitments |
| General Data Protection Regulation (GDPR) | Processing and storage of customer data for people who reside in the European Union (EU) | Customer must keep regulated data in Google Cloud regions in the EU |
| Payment Card Industry Data Security Standard (PCI DSS) | Regulations for payment processors | Customer must implement their share defined in the PCI DSS shared responsibility matrix |
HIPAA protection for health information is the United States law that sets standards for handling electronic personal health information (PHI). HIPAA responsibilities are shared between Google Cloud as the cloud service provider and the customer, with Google documenting how it meets its portion and the customer implementing the remaining controls for their workloads. Customers can review Google's HIPAA posture and related evidence through the Compliance resource center. Architecturally, this means a health workload depends on both sides: Google's infrastructure controls protect the platform, and the customer's access controls, configuration, and data handling protect the PHI stored in that platform.
GDPR protection and data residency is the European Union regulation that governs how customer data for EU residents can be processed and stored. If a business serves customers who reside in the EU, the business may be obligated to keep that customer data in the EU itself. Google provides Google Cloud regions in the EU and documents how it meets its GDPR obligations, but the customer is responsible for ensuring the data they collect remains in those EU regions.
This residency requirement creates a location boundary that the architect must enforce through resource placement. Data flows from users and applications into the selected EU region, processing stays in that region, and supporting artifacts such as inspection jobs and data profiles are also stored in that region. Choosing a non-EU region for storage or exports would break the residency boundary even when the primary database is correctly placed.
Sensitive Data Protection is the Google Cloud service for discovering, inspecting, and de-identifying sensitive personal data in services such as BigQuery and Cloud Storage. For Google Cloud data, inspection is performed by storage methods that process the data in the same region where the data resides and store the inspection job in that region. For data stored anywhere, including outside Google Cloud, hybrid methods let the customer specify where Sensitive Data Protection will process the data and save the job.
The inspection job contains the configuration details and a result summary, and the result summary does not include the inspected data or the actual sensitive strings, called quotes. Data flows from the source table or bucket to Sensitive Data Protection for analysis, then findings can flow to a BigQuery table owned by the customer when export is configured. The customer owns that export table and controls how it is stored, accessed, and protected, and depending on settings the exported findings can include quotes. The job, including its result summary, can be deleted through the Google Cloud console or through the DLP API (Data Loss Prevention API).
Discovery extends the same residency principle to profiling, because Sensitive Data Protection processes data assets in the region or multi-region where they reside and stores the generated data profiles in the same region or multi-region. Custom infoTypes, which are customer-defined detectors built from a regular expression or a list of terms, are stored according to how the terms are supplied:
Exam tip: The inspection result summary never includes quotes, while an exported BigQuery findings table includes quotes only when export settings allow it.
Data ownership and the shared responsibility model define who is accountable for cloud-hosted data and who secures each layer around it. The organization remains the owner of its data in Google Cloud, while Google and the customer split security duties between underlying infrastructure and customer-configured resources. Ownership is made enforceable through tagging, encryption with customer-controlled keys, and fine-grained access management.
Shared responsibility in Google Cloud splits duties between Google-managed infrastructure and customer-managed configuration. Google is responsible for the compliance of the underlying physical infrastructure and platform, while the customer is responsible for the configuration health of resources that run on Google Cloud, such as datasets, tables, instances, and access policies. Security Command Center (opens in a new tab) reflects this boundary by reporting only observable controls in the customer or shared responsibility areas, rather than Google's own infrastructure compliance. Because Security Command Center checks only this subset of controls defined by a standard, its reports help prioritize remediation of misconfigurations but do not replace a formal audit.
| Responsibility area | Owned by | What Security Command Center evaluates |
|---|---|---|
| Underlying infrastructure compliance | Not reported as customer findings; managed by Google Cloud itself | |
| Resource configuration health | Customer and shared | Misconfigurations in customer resources, such as public datasets or missing encryption |
| Compliance posture of workloads | Customer and shared | Passing or failing status for supported observable controls at project, folder, or organization scope |
Compliance statistics roll up by scope, so project-level activation shows only that project, while organization-level activation shows the organization including its folders and projects. Reports are generated daily from active and muted findings.
Establishing data ownership for migrated and cloud-generated data means every data asset is labeled with an accountable owner and a sensitivity level. Data Catalog automatically captures technical metadata from BigQuery tables into a data register, and Tag Engine, an application running on Cloud Run, applies business metadata tags such as owner name and sensitivity level from a reference table. This automated tagging ensures sensitive data carries owner information needed for governance and compliance, and any new asset or change updates the catalog.
Sensitive classification starts with Sensitive Data Protection (SDP), which inspects assets for sensitive information types (infoTypes) such as AGE, DATE_OF_BIRTH, PHONE_NUMBER, and EMAIL_ADDRESS. Data flows from the inspected asset to findings tables, then to tagging and reporting in order:
is_sensitive boolean tag to the table plus a sensitive_category tag and policy tag to the column.The classification taxonomy used for tagging includes four sensitive levels:
A fifth value, Public Information, marks non-sensitive data, and organizations can add categories such as Material Non-Public Information. Findings flag whether sensitive data lacks a sensitive-category tag or lacks a column-level sensitivity tag.
Encryption to maintain organizational authority ensures only key holders can read sensitive data at rest. By default, Google Cloud encrypts stored data with Google-owned and Google-managed encryption keys, as used for services such as Cloud Storage buckets and Cloud SQL databases. Customer-Managed Encryption Keys (CMEK) give the organization control over the keys in Cloud Key Management Service, so access can be revoked or rotated independently of Google.
The data security baseline detects sensitive data that lacks this stronger control. Sensitive Data Protection identifies data sensitivity, and Compliance Manager (opens in a new tab) checks the encryption configuration, so the combined detectors fire only when sensitive data exists without the required protection:
| Protected resource | Control | What triggers a finding |
|---|---|---|
| BigQuery tables with sensitive data | Require CMEK | Sensitive table is not encrypted with a customer-managed key |
| BigQuery datasets with sensitive data | Require CMEK | Sensitive dataset is not encrypted with a customer-managed key |
| Cloud SQL instances with sensitive data | Require CMEK | Sensitive database is not encrypted with a customer-managed key |
| BigQuery datasets and Cloud SQL instances with sensitive data | Block public access | Sensitive data is present in a publicly accessible dataset or instance |
Exam tip: Resolving Security Command Center findings improves configuration health but does not guarantee full regulatory certification.
Access management and entitlements define who can access sensitive data, enforce that decision, and track access over time. By default, only creators and owners are assigned entitlements to sensitive data, and all other access must be explicitly granted and tracked. Identity and Access Management (IAM) manages groups, users, and service accounts for table-level access, while BigQuery policy tags enforce fine-grained column-level access. Cloud Identity, which can be federated with an existing identity provider, ensures only authenticated users can receive those grants.
Policy tags (opens in a new tab) from the cdmc sensitive data classification taxonomy apply directly to columns that contain confidential data in BigQuery tables. The policy applies to the column, and the request from a user to read that column depends on both IAM permission and policy-tag permission. By default, users have no access to columns that have defined policy tags, so a user with table-level IAM access still cannot view a tagged column without the matching policy-tag grant. A scheduled detector checks for entitlement gaps, including a data asset that has a sensitive category but no related policy tag, and a category that does not match its policy tag.
constraints/gcp.resourceLocations organization policy and Assured Workloads folders prevent creation of location-based resources outside allowed regions.Data residency describes where Customer Data is stored at rest, data locality adds where data is processed in use and transmitted in transit plus where workloads can be accessed from, and data sovereignty adds which jurisdiction governs the data including which laws apply, which personnel can administer it, and which keys protect it. A workload can satisfy residency but still violate locality if it is processed outside its home region or violate sovereignty if it is administered from outside its jurisdiction, so storage location, processing location, access location, and administrative control must be checked together.
Organization policies with the Resource Locations constraint define the allowed set of locations for new resources and prevent provisioning of in-scope resources in denied regions at the organization, folder, or project level. An Assured Workloads folder applies a selected control package that presets allowed regions and related constraints for every project created inside it, so sensitive data with specific residency needs must be placed and kept inside the compliant folder because only resources created there inherit the protection.
Under the shared responsibility model Google remains responsible for the underlying network and infrastructure while the customer remains responsible for access policies, region choices, and the data they store. For Health Insurance Portability and Accountability Act (HIPAA) the customer must configure controls for electronic personal health information on top of Google infrastructure controls, and for General Data Protection Regulation (GDPR) the customer must keep customer data for people who reside in the European Union in Google Cloud regions in the European Union.
Sensitive Data Protection processes data assets in the region or multi-region where they reside and stores the inspection job and generated data profiles in that same region or multi-region. The inspection result summary does not include the inspected data or the sensitive strings called quotes, while findings exported to a customer-owned BigQuery table can include quotes depending on export settings and the customer controls how that export table is stored, accessed, and protected.
An enterprise is migrating its sensitive analytics data warehouse to BigQuery. Under regulatory compliance standards and the cloud shared responsibility model, the organization must enforce strict data ownership and least privilege access governance:
Which Identity and Access Management (IAM) role configuration should the organization implement?
Last updated