Prepare and test your skills

Prepare and test your skills

Governance and policy enforcement mechanisms are the rules and controls that keep Google Cloud resources and data inside approved geographic boundaries. Data residency is the practice of keeping data within specific geographic boundaries because of legal, regulatory, or organizational requirements. Regulations such as GDPR, HIPAA, and PIPEDA can make residency a legal necessity, because violations can lead to fines or legal action.
The Organization Policy Service enforces data residency by applying organization policy constraints to Google Cloud resources. The constraint gcp.resourceLocations blocks deployment of resources in unauthorized geographic areas by allowing new resources only in approved regions. The constraint gcp.restrictServiceUsage limits which services can be used inside an Assured Workloads (opens in a new tab) folder, which prevents creation of non-compliant resources for unsupported services.
| Organization policy constraint | Violation it addresses | What it enforces |
|---|---|---|
| gcp.resourceLocations | Non-compliant resource location | Resource location must be in an approved region |
| gcp.restrictServiceUsage | Non-compliant resources in folder | Only allowed services can be created in an Assured Workloads folder |
The gcp.resourceLocations constraint is used by many control packages, including:
Exam tip: Use gcp.resourceLocations to control where resources can be located, and use gcp.restrictServiceUsage to control which services can be used in an Assured Workloads folder.
Secret Manager (opens in a new tab) enforces data residency at the service level through regional secrets. When a regional secret is created, the creator specifies the location where it should be stored, and Secret Manager keeps the secret data within that location's infrastructure at rest, in use, and in transit. Only applications or services running within the same location can access the regional secret. Unlike global secrets, which are often replicated across multiple locations for high availability, regional secrets are not automatically replicated, which supports strict residency requirements.
Combined policy and service controls enforce data residency at different layers of Google Cloud. The gcp.resourceLocations constraint controls where resources can be deployed, while gcp.restrictServiceUsage controls which services can be created in an Assured Workloads folder. Regional secrets then control where secret data is stored and which applications or services can access it. Other services such as Certificate Authority Service (opens in a new tab) also list data residency as a supported security capability, so organizations layer these controls to meet legal and organizational boundary requirements.
Google Cloud resource location controls are the settings that let an organization choose and enforce the geographic places where data is stored and processed. The customer selects a region or zone when creating a resource, and organization policies then block new resources outside approved locations. Together, these choices keep data inside defined boundaries to meet compliance obligations.
Data residency on Google Cloud describes where customer data is stored at rest and, for stricter needs, where it is processed in use and transmitted in transit. Customers enable residency by selecting a specific location during provisioning, such as a region for an Apigee (opens in a new tab) organization or a bucket or dataset location for storage and analytics. That choice cannot be changed later for some services, so a new project or organization is required if a different location is needed. Google Cloud commits to storing Customer Data at rest in the selected location and processing Customer Data in use only within the country of the selected region, or within the European Union if an EU region or multi-region is selected.
Zones, regions, and multi-regions on Google Cloud define how widely data and compute are spread for availability and control. Every general-purpose region is intended to offer a minimum of three physically and logically distinct availability zones. Choosing a smaller scope keeps data tightly bounded, while choosing a larger scope spreads it for resilience but across more geography.
| Location type | Where the resource lives | Example | Availability behavior |
|---|---|---|---|
| Zonal resource | Operates within a single zone | A Compute Engine virtual machine in one zone | A zonal outage can affect some or all resources in that zone |
| Regional resource | Redundantly deployed across multiple zones within one region | An App Engine application or regional managed instance group | Higher availability than a single zone because other zones in the region can continue |
| Multi-regional resource | Managed by Google as redundant and distributed within and across regions | Cloud Storage buckets and BigQuery datasets created in a multi-region | Designed to keep functioning after the loss of a single region, with documented tradeoffs in latency or consistency |
Services with both regional and multi-regional options include Cloud Storage, BigQuery, Firestore, Spanner, Cloud KMS, and Artifact Registry. A regional choice keeps data inside one region, while a multi-regional choice replicates it across regions inside a larger area such as the United States or European Union.
The Resource Locations organization policy is the control that enforces which geographies can be used for new resources. When the constraint constraints/gcp.resourceLocations is set at the organization, folder, or project level, location-based resources can only be created in the allowed list. Assured Workloads (opens in a new tab) builds on this by creating a dedicated folder tied to a compliance control package that automatically limits the regions available for selection.
Enforcement follows an ordered workflow:
If a project already has a location constraint, provisioning fails when it conflicts with the requested location. An organization provisioned without data residency must allow global, because its control plane is global by default, while an organization with data residency must not exclude its chosen control plane region.
Cloud Storage and BigQuery apply geographic control through the location selected for each bucket or dataset. A regional bucket or dataset stores and processes its Customer Data within that region's country, which keeps data inside one national boundary when that is required. A multi-regional bucket or dataset stores data redundantly across regions in that multi-region, which improves resilience to a regional loss but means data resides in more than one country or region within that boundary. Administrators must check the regionality of each service before deploying and replicate or snapshot zonal or regional data to another region or to a multi-regional resource for disaster recovery. Global management functions, load balancing, and internal services such as networking and identity still operate across regions to keep the platform running.
Shared responsibility (opens in a new tab) for location control divides work between Google and the customer. Google provides default encryption, infrastructure controls, and enforcement of the Identity and Access Management (IAM) policies and Assured Workloads controls the customer selects, including restrictions on where data is stored. The customer is responsible for knowing which data has residency requirements, placing that sensitive or regulated data inside the appropriate Assured Workloads folder or project and keeping it there, configuring IAM so only appropriate personnel can access it, and organizing the hierarchy of organizations, folders, and projects so personal data is not exposed.
Customers must also avoid placing sensitive or regulated data in common descriptive fields such as resource names and IDs, project or folder names, labels, and description fields. Those identifiers and attributes are treated as Service Data or metadata rather than Customer Data at rest and sit outside the data residency technical boundary. Sharing information prudently during support and troubleshooting also prevents regulated data from leaving the compliant folder.
Exam tip: Data residency commitments cover Customer Data at rest in configurable services, but they do not cover resource identifiers, attributes, or labels, so sensitive data must never be placed in names or description fields.
Data residency and data sovereignty are related but different requirements for control over organizational data. Data residency is about where data is physically stored and processed, while data sovereignty is about which laws and authorities govern that data. Organizations may need both to meet legal, regulatory, and geopolitical obligations.
Exam tip: Data residency answers “Where is the data stored?” while data sovereignty answers “Which laws and authorities govern the data?”
Data residency is the practice of keeping data within specific geographical boundaries because of legal, regulatory, or organizational requirements. It is not just a preference for some businesses because regulations such as GDPR, HIPAA, or PIPEDA can make it a legal and operational necessity. Organizations use data residency to comply with those regulations and to reduce the risk of fines or legal action.
Secret Manager (opens in a new tab) helps enforce data residency through regional secrets. When an organization creates a regional secret, it specifies the location where the secret is stored, and Secret Manager keeps the secret data within that location's infrastructure at rest, in use, and in transit. Regional secrets can only be accessed by applications or services running in the same location, which limits access to authorized entities within that region. Unlike global secrets, which are often replicated across multiple locations for high availability, regional secrets are not automatically replicated, which supports strict residency.
Data sovereignty is the legal and jurisdictional control over data, meaning which country's laws and authorities govern it. Data sovereignty focuses on legal oversight rather than only physical location. Legal, regulatory, and geopolitical factors can require strict control over both the physical location and the jurisdictional oversight of organizational data.
For example, in the Kingdom of Saudi Arabia, the Communications, Space and Technology Commission (CST) granted Google Cloud a Class C license in the Dammam region. That qualification is based on an assessment by the National Cybersecurity Agency (NCA) against the Essential Cybersecurity Controls (ECC) and the Cloud Cybersecurity Controls (CCC). The ECC sets minimum cybersecurity requirements for organizations in scope, while the CCC extends the ECC to reduce cybersecurity risks for cloud service providers and cloud service tenants.
Data residency and data sovereignty answer different questions and can require different controls. Residency controls keep data in a chosen location, while sovereignty requirements may also require local licensing or compliance with national cybersecurity controls. Organizations often use residency controls to help satisfy sovereignty obligations, but the two concepts are not interchangeable.
| Concept | Main question | What it controls | Example driver | Google Cloud example |
|---|---|---|---|---|
| Data residency | Where is data stored? | Physical or geographic location | GDPR, HIPAA, PIPEDA | Regional secrets in Secret Manager |
| Data sovereignty | Which laws or authorities govern data? | Legal jurisdiction and oversight | Local licensing and cybersecurity rules | CST Class C license in the Dammam region; NCA ECC and CCC |
Other Google Cloud services also support these needs, including Cloud Key Management Service (KMS) (opens in a new tab) for regulatory support and Assured Workloads (opens in a new tab) control packages for boundary enforcement. A residency control such as a regional secret keeps data in a chosen location at rest, in use, and in transit. A sovereignty requirement adds the layer of which authority has oversight, so both location choice and jurisdictional compliance must be addressed together.
gcp.resourceLocations constraint blocks creation of resources outside approved regions, while gcp.restrictServiceUsage limits which services can be used in an Assured Workloads folder.Data residency is the practice of keeping data within specific geographic boundaries because of legal, regulatory, or organizational requirements and answers where data is stored. Data sovereignty is the legal and jurisdictional control over data and answers which country's laws and authorities govern it. Organizations often use residency controls to help satisfy sovereignty obligations, but the two concepts are not interchangeable.
The Organization Policy Service enforces data residency with the gcp.resourceLocations constraint which blocks deployment of resources in unauthorized geographic areas by allowing new resources only in approved regions. It also uses the gcp.restrictServiceUsage constraint which limits which services can be used inside an Assured Workloads folder to prevent creation of non-compliant resources for unsupported services.
When a regional secret is created the creator specifies the location where it should be stored and Secret Manager keeps the secret data within that location's infrastructure at rest, in use, and in transit. Only applications or services running within the same location can access the regional secret and unlike global secrets regional secrets are not automatically replicated which supports strict residency requirements.
A healthcare organization must comply with strict national data residency laws for its cloud workloads. The leadership team has established the following governance requirements:
Which Google Cloud governance mechanism should the organization implement to meet these requirements?
Last updated