Prepare and test your skills
Prepare and test your skills
Differentiating certification scopes and objectives means choosing the compliance framework whose data types, industries, and security goals match the workload. On Google Cloud, meeting regulatory requirements is a shared responsibility between Google and the customer, so the architect must select services whose existing certifications fit the workload requirements. AlloyDB (opens in a new tab) shows how this works because it carries certifications across information security, service controls, payment card, and health domains.
Shared responsibility for regulatory requirements means Google provides certified infrastructure and services while the customer aligns each workload with the correct rules. Google obtains independent certifications for its services, and the customer chooses the services, regions, and configurations that satisfy organizational obligations. This division makes certification scope a design input, because a service is only a valid building block when its certifications match the data and workload requirements.
Industry certification groups on Google Cloud are families of certifications that cover different compliance domains rather than interchangeable approvals. AlloyDB has received certifications in the following groups, which show how one service can span several domains:
The architect distinguishes these groups by the organizational data at issue, such as general information security management versus payment card processing versus health-related data. The ISO group addresses information security management and cloud-specific controls, the SOC group addresses operational controls and trust principles, PCI DSS addresses payment card security, and HIPAA addresses health information handling.
Exam tip: Security operations center (SOC) analysts who respond to findings are different from Service and Organization Controls (SOC) 1, SOC 2, and SOC 3 certifications.
Aligning workloads with compliance evidence and controls means verifying service certifications and then enforcing the chosen framework in the cloud organization. The compliance resource center is the central source for checking which Google Cloud services hold which certifications for different regulatory frameworks. For enforcement, Assured Workloads lets the architect apply controls to specific folders in the Google organization that support regulatory, regional, or sovereign requirements.
Applying the shared responsibility model to certification means dividing audit controls between Google Cloud and the customer architect. Google Cloud secures the underlying platform and proves its controls through platform certifications, while the architect configures workload-level controls and proves them during the customer's own audit. A certification such as SOC 2, ISO 27001, PCI DSS, or FedRAMP is therefore satisfied only when both sides meet their assigned controls.
What the architect must decide for certification controls is which workload-level protections are needed beyond Google's default platform protections. The customer is considered the expert on its own data and must weigh three inputs before choosing controls:
Protection of data is a primary design consideration for Google infrastructure, products, and personnel operations for Customer Data and Service Data. When workloads face specific regulatory or national standards, internal policies may differ from default configuration options. In that case the architect must adopt additional tools and techniques to maintain the required level of compliance.
Controls managed by Google Cloud are the foundational infrastructure elements that the architect inherits but does not directly operate. Google secures physical infrastructure and network security, applies default encryption and infrastructure controls, and builds controls that restrict privileged access. These platform controls are validated through programs such as the FedRAMP High Provisional Authority to Operate (P-ATO), which covers more than 150 services, but they do not automatically certify the customer's workload.
Google also provides enforcement mechanisms that act only after the architect configures them:
Controls the architect must implement to satisfy an audit are the workload, data, and access decisions that Google Cloud cannot make on the customer's behalf. For financial-services and other regulated workloads, the customer is responsible for securing data and applications, configuring access control, and configuring and managing security services. An auditor will check these customer-owned settings even when the underlying platform is already certified:
Exam tip: Google Cloud enforces the IAM policies you set, but you must create them; an empty or overly broad policy is a customer audit failure, not a Google platform failure.
How responsibility shifts by service model determines how many controls appear in the customer's audit scope. The split depends on whether the workload uses Infrastructure as a Service (IaaS), Platform as a Service (PaaS), or Software as a Service (SaaS), and a single enterprise often uses all three at once:
A three-column comparison showing IaaS leaves bulk security to the customer, PaaS shares app and IAM controls, and SaaS leaves bulk security to Google while data and access stay with the customer.
| Service model | Example services | Responsibility split |
|---|---|---|
| Infrastructure as a Service (IaaS) | Compute Engine, Cloud Storage, Cloud VPN, Cloud Load Balancing, Cloud DNS | The bulk of security responsibility belongs to the customer; Google Cloud is responsible for underlying infrastructure and physical security |
| Platform as a Service (PaaS) | App Engine, Google Kubernetes Engine (GKE), BigQuery | Google Cloud owns more controls, varying by service and feature; responsibility is shared for application-level controls and IAM, while the customer remains responsible for data security and client protection |
| Software as a Service (SaaS) | Google Workspace, Google Security Operations, Marketplace SaaS applications | Google Cloud owns the bulk of security responsibility; the customer remains responsible for access controls and the data placed in the application |
In IaaS the architect configures operating systems, networks, and storage access, so misconfiguration risk is highest. In PaaS and SaaS more patching and platform hardening moves to Google, but data classification, identity decisions, and residency choices stay with the architect. Certification evidence must therefore show how controls interact across models rather than treating each service in isolation.
Using Assured Workloads (opens in a new tab) and boundaries to prove compliance means translating a certification regime into enforced technical limits in Google Cloud. The architect creates an Assured Workloads folder and sets the compliance program, such as FedRAMP High or EU controls, and any project under that folder inherits the security and compliance guardrails set at the folder level. Assured Workloads restricts selectable regions through the resource-location Organization Policy Service, so data residency requirements control where resources can be created.
This boundary supports audit evidence in two ways. Traffic and data stay inside the approved control boundary only when the architect keeps regulated data types in the compliant folders and uses private connectivity options to Google managed services. The architect can show which controls are inherited and which were configured by using the Compliance resource center, Customer Responsibility Matrix (CRM), and System Security Plan (SSP). The workload still needs its own authorization because platform authorization plus correct folder configuration together satisfy the audit criteria.
Utilizing compliance documentation and evidence means collecting third-party audit reports, certifications, and technical records that prove a cloud deployment meets regulatory requirements. On Google Cloud, this evidence includes independent certifications for global frameworks and service-specific coverage, plus technical records from build and runtime controls. Architects use this package to align designs with stakeholder trust and to pass regulatory verification.
Industry certifications and compliance coverage on Google Cloud show that Google's controls have been independently audited against global security standards. Architects map these platform certifications to customer compliance needs:
The Google Cloud Business Associate Agreement (BAA) also covers VMware Engine (opens in a new tab), which extends protected health information handling to that environment. For VMware Engine, the VMware Engine security shared responsibility model defines which protections Google manages and which protections the customer manages.
Obtaining audit reports and bridge letters means requesting point-in-time proof through the account team rather than generating it inside the project. For assistance with auditing, the architect contacts the account representative for the latest ISO certificates, SOC reports, and self assessments. Those documents provide the proof auditors request, while bridge letters cover the gap period between formal audit reports. Architects should request the current set during design so controls, timelines, and customer responsibilities match the certified scope.
Using Artifact Registry (opens in a new tab) and supply chain controls as technical evidence means proving that build artifacts and runtime containers meet security policy. Artifact Registry is a scalable and integrated repository service built on Google infrastructure for storing and managing build artifacts such as Docker images, Maven packages, and npm packages. Repository access is managed with Identity and Access Management (IAM), and teams interact with repositories through gcloud, Cloud Console, and native package format tools.
Artifact Registry is one of the Google Cloud components used to protect the software supply chain together with other products and features. That protection covers developer workflows and tools, software dependencies, continuous integration and continuous delivery (CI/CD) systems used to build and deploy software, and runtime environments such as Google Kubernetes Engine (GKE) and Cloud Run. Artifact guard evaluates container images against configurable security policies during build generation, registry storage, and runtime execution, and it centralizes scan results from CI/CD pipelines, artifact registries, and running GKE clusters into a single view in Security Command Center.
Policy enforcement follows an ordered workflow where each stage depends on the prior configuration:
Exam tip: Artifact Registry stores build artifacts such as container images, while ISO certificates and SOC reports for audits are obtained from the account representative.
They cover different compliance domains rather than interchangeable approvals. The International Organization for Standardization (ISO) group addresses information security management and cloud-specific controls, the Service and Organization Controls (SOC) group addresses operational controls and trust principles, Payment Card Industry Data Security Standards (PCI DSS) addresses payment card security, and Health Insurance Portability and Accountability Act (HIPAA) addresses health information handling. AlloyDB illustrates this span because it holds International Organization for Standardization (ISO) 27001, ISO 27017, ISO 27018, ISO 27701, Service and Organization Controls (SOC) 1, SOC 2, SOC 3, Payment Card Industry Data Security Standards (PCI DSS), and Health Insurance Portability and Accountability Act (HIPAA) coverage.
Meeting regulatory requirements on Google Cloud is a shared responsibility where Google provides infrastructure and services while the customer chooses the services, regions, and configurations that satisfy organizational obligations. Google secures physical infrastructure and network security, applies default encryption and infrastructure controls, and builds controls that restrict privileged access, while the customer remains responsible for securing data and applications, configuring access control, and configuring and managing security services.
Assured Workloads lets the architect apply controls to specific folders in the Google organization that support regulatory, regional, or sovereign requirements, and projects under that folder inherit the security and compliance guardrails set at the folder level. It restricts selectable regions through the resource-location Organization Policy Service so data residency requirements control where resources can be created.
A financial software company is deploying a multi-tenant SaaS platform on Google Cloud. The company must satisfy two distinct compliance objectives for its upcoming enterprise launch:
Which compliance frameworks or reports directly satisfy these two requirements?
Last updated