Prepare and test your skills

Prepare and test your skills

Confidentiality, integrity, and availability are the three core principles that protect information and keep cloud services reliable. Confidentiality keeps Customer Data private so only authorized parties can see it. Integrity keeps data and systems accurate and free from unauthorized change. Availability keeps services running and data usable when needed.
In Google Cloud, these principles are applied through deny-by-default access, auditable justifications, universal logging, strong authentication, and shared duties. Google infrastructure (opens in a new tab) provides homogeneous, automated systems with limited privileged access. Customers control their own data, access policies, and configurations. Shared responsibility (opens in a new tab) between Google and the customer connects all three principles.
Confidentiality in Google Cloud means Customer Data belongs to the customer organization and is not visible to others by default. Google personnel are denied access by default, and Access Approval (opens in a new tab) requires explicit approval from the content owner before human access to user content in many cases. Access by a Google employee using an internal support tool to view a Spanner database for a support case is administrative access, while access granted directly by the customer through Identity and Access Management (IAM) at the project level is non-administrative access.
Confidentiality is also supported by inherited controls such as default encryption and infrastructure protections, which customers can use as evidence for auditors. Human access to user content is recorded for review, while purely automated access is not. For example, a program that periodically hashes customer content to check for corruption does not let any human view or export content, so it does not create human-access logs.
Exam tip: Human access to user content creates Access Transparency logs, while automated system checks with no human viewing do not.
Integrity in Google Cloud means Customer Data and production systems are protected from improper or unauthorized change. Every administrative access requires an auditable, valid business justification, so support or engineering access must state why the access is needed. Binary Authorization for Borg requires production software to be reviewed and approved before deployment, which reduces the chance that unreviewed code or a compromised account can act alone to reach user data.
Integrity threats can trigger emergency access when there is an urgent threat to Google services, infrastructure, or customer services or content. Emergency access can override an organization's Access Approval policy and is logged in Access Approval with the auto-approved status. Non-emergency access, such as viewing data to resolve a filed support request, follows the normal approval path. Deployment integrity logs record internal exceptions about code changes, and exception monitoring helps ensure that unreviewed source code does not run in privileged environments.
Availability in Google Cloud means services remain running, resilient, and protected from disruption. Google always remains responsible for the underlying network and infrastructure, while customers always remain responsible for their access policies and data. This division means Google protects the platform with automated infrastructure and limited privileged access, and customers protect what they store and who can reach it.
Availability depends on strongly authenticated, context-aware access and continuous threat detection. Jobs in production prove identity with cryptographic credentials and use application layer transport security (ALTS). Access decisions evaluate user identity, location, device ownership, configuration, and fine-grained policies rather than only static credentials or network location. Threat indicators built from past incidents, network traffic, access logs, anomalous behavior, and offensive security exercises are used to scan logs, match malicious activity, revoke access, and alert staff.
Logging and monitoring in Google Cloud make confidentiality, integrity, and availability auditable and accountable. Administrative access to Customer Data is logged by default. After Access Transparency is enabled, near real-time audit logs of Google personnel access are published to each project's logs for external review and internal auditing.
Google infrastructure uses three complementary log types:
Together, strong authentication, justification requirements, approval controls, and universal logging ensure that data stays private, changes stay authorized, and threats to reliable service are detected and answered quickly.
Shared responsibility and control models define which security duties belong to Google Cloud and which belong to the customer. Google Cloud controls its own personnel, service infrastructure, and compliance certifications. The customer controls data, access choices, configuration, and monitoring.
The shared responsibility framework in Google Cloud divides security duties between the provider and the customer. Google Cloud restricts what its personnel can see, requires a valid justification for privileged access to Customer Data, and provides transparency tools such as Access Transparency (opens in a new tab). The customer chooses compliance regimes, data locations, encryption key options, and access criteria for Google support personnel.
| Responsibility area | Google Cloud role | Customer role |
|---|---|---|
| Personnel access | Restricts personnel visibility and requires justification, confidentiality agreements, and Code of Conduct | Selects access criteria for support personnel through Assured Workloads (opens in a new tab) |
| Data location | Provides data residency and location controls through organization policies | Chooses region and configures organization policies |
| Encryption | Offers Google-owned and Google-managed keys that are FIPS-140-2 compliant | Can use customer-managed keys for added control |
| Compliance | Meets ISO 27001, SOC 1/2/3, PCI DSS, FedRAMP, and HIPAA and provides blueprints | Selects regime, automates implementation, and monitors compliance |
| Monitoring | Provides Access Transparency, VPC Flow Logs, and Security Command Center | Uses logs and alerts to audit access and noncompliance |
The boundary is clear: Google Cloud manages the provider side of security and compliance, and the customer manages how its data and resources are configured and monitored. Assured Workloads bridges the two sides by automatically setting baseline personnel access controls for the selected compliance regime.
Administrative controls are policies and processes that govern who can access systems and data. Google Cloud requires all employees to sign a confidentiality agreement and follow Google's Code of Conduct. Access to Customer Data requires a valid business justification, and Access Transparency logs show near real-time when administrators access customer content.
These controls protect confidentiality by limiting what Google personnel can see and by recording when access happens. They also support accountability because access must have a documented reason.
Technical controls are mechanisms that enforce security boundaries and protect data. VPC Service Controls (VPC-SC) sets security perimeters around Google Cloud resources to prevent data exfiltration. Data residency keeps data at rest and resources in a selected region. Encryption options include Google-managed keys and customer-managed keys.
These controls enforce boundaries between the customer's environment and the outside, and between Google's management access and customer data. They also give the customer direct control over encryption keys and network perimeters when more separation is needed.
Operational controls are ongoing activities that monitor, audit, and automate compliance. Google Cloud provides logging and monitoring tools that help customers detect access, network activity, and noncompliance. Assured Workloads automates parts of compliance implementation, and blueprints with Terraform modules provide recommended configurations.
These operational controls keep governance active after deployment by watching activity, alerting on problems, and automating repeatable compliance steps.
Exam tip: Google-managed encryption keys are FIPS-140-2 compliant and support FedRAMP Moderate, while customer-managed encryption keys (CMEK) add customer control and separation of duties.
Compliance and regulatory alignment means matching cloud controls, configurations, and evidence to the laws and industry frameworks an organization must follow. Google Cloud supports alignment with automated compliance controls, recommended deployment blueprints, monitoring logs, third-party audit documents, and service-specific certifications. These capabilities help organizations show that data is controlled, confidential, and available while meeting assurance and reporting requirements.
Assured Workloads (opens in a new tab) builds on Google Cloud controls to help organizations meet compliance obligations. When an organization selects a compliance regime, Assured Workloads automatically sets the baseline personnel access controls for that regime. It also lets the organization set data location with organization policies, select key-management options such as key rotation period, select access criteria for Google support personnel such as background checks, and choose between Google-managed keys and customer-managed keys.
Google-managed keys are FIPS-140-2 compliant and support FedRAMP Moderate compliance. For added control and separation of duties, the organization can use customer-managed encryption keys (CMEK). Google Cloud blueprints and solution guides provide recommended configurations and Terraform modules for a compliance regime. Organizations can modify these blueprints to incorporate their security policies into infrastructure deployments, including blueprints for FedRAMP and HIPAA.
Monitoring compliance activities means creating logs and alerts for the access-related and network events that most regulations require. Google Cloud provides several tools that record activity or warn about unapproved use. Firewall Rules Logging records TCP and UDP connections for customer-created rules, which helps audit network access. VPC Flow Logs record traffic flows sent or received by VM instances.
Together, these tools let customers audit access, network activity, and key use, and receive alerts when activity suggests noncompliance.
Audit Manager lets organizations download the most recent Google Cloud compliance documents that third-party auditors create when they audit Google's environment. These documents help organizations understand how Google addresses its responsibilities for various regulatory frameworks. The documents include business continuity plans, disaster recovery testing reports, audit reports, certifications, statements of applicability, and vendor risk assessments for frameworks such as C5:2020, CSA STAR Registry, FedRAMP Customer Responsibility Matrix, IRAP Protected level, ISO/IEC 27001:2022 and 27018:2019, Portugal GNS, and Spain ENS.
To download compliance documents, an administrator must grant the Audit Manager Auditor role on the organization. The user then follows an ordered workflow:
Anything marked Google Confidential Information is shared under the confidentiality obligations in the customer or partner agreements covering Cloud Services.
Service certifications and data boundaries show how specific Google Cloud services meet compliance and residency needs. Certificate Authority Service supports VPC Service Controls, Access Transparency, Access Approval, Workforce identity federation, and data residency. It meets standards including ISO 27001, ISO 27017, ISO 27018, SOC 1, SOC 2, SOC 3, PCI DSS, C5, FedRAMP Moderate and FedRAMP High, IRAP, HIPAA, CJIS, ITAR, and ISMAP.
Google Security Operations supports data residency and boundaries through Advanced Data Residency and sovereign data boundaries. Most country-specific and regulatory data boundaries, such as Australia, Canada, EU, Israel, Japan, KSA, US, and healthcare data boundaries, are managed through Assured Workloads. For US public sector and defense workloads, Google Security Operations supports FedRAMP High and Moderate impact levels and Department of Defense Impact Levels 2, 4, and 5. It also satisfies HIPAA and PCI DSS, supports customer-managed encryption keys for data at rest, and uses VPC Service Controls to prevent data exfiltration.
Confidentiality protections and government request handling define how Google limits visibility into Customer Data. Google personnel are strictly restricted in what is visible to them. All access to Customer Data requires a valid justification for privileged access, and Access Transparency logs show when administrators access customer content. All Google employees must sign a confidentiality agreement, follow the Code of Conduct, and complete onboarding, security, and privacy training.
If Google receives a government request for Customer Data, its policy is to direct the government to request the data directly from the Google Cloud customer. The customer then responds to government requests for its own data. This separation keeps control of customer content with the customer organization.
Exam tip: Assured Workloads configures controls for a chosen compliance regime, while Audit Manager provides third-party audit documents for assurance and reporting.
Access Transparency provides near real-time audit logs of human access by Google personnel to user content in each project's logs for external review and internal auditing, while Audit Manager provides a library to download third-party audit reports, certifications, and other compliance documents about Google's environment as a ZIP file containing PDFs. Human access to user content creates Access Transparency logs, while purely automated checks with no human viewing do not.
Google-managed keys are FIPS-140-2 compliant and support FedRAMP Moderate compliance, while customer-managed encryption keys (CMEK) managed in Cloud Key Management Service add customer control and separation of duties. Assured Workloads lets an organization choose between Google-managed keys and customer-managed keys and select key-management options such as key rotation period for a selected compliance regime.
Emergency access for an urgent threat to Google services, infrastructure, or customer services or content can override an organization's Access Approval policy and is logged in Access Approval with the auto-approved status. Non-emergency access, such as viewing data to resolve a filed support request, follows the normal approval path requiring explicit approval from the content owner.
A financial services company is preparing for an annual regulatory assessment. To satisfy assurance and reporting requirements under the shared responsibility model, the compliance team must provide external regulators with the following items verifying Google Cloud's underlying environment:
Which Google Cloud tool should the team use to download these third-party compliance documents?
Access Transparency
Security Command Center
Audit Manager
Assured Workloads
Last updated