On this page
- Does Google’s SOC 2 report make my company SOC 2 compliant?
- How do I get Google’s SOC 2 Type 2 report?
- How often does Google issue its SOC 2 report?
- What GCP evidence does an auditor ask for, by control?
- Which GCP defaults leave gaps in a Type 2 period?
- What do I send a customer who asks about GCP in a security review?
- How should GCP shape scope and the choice of auditor?
Google Cloud publishes SOC 2 Type 2 reports that cover Google's controls, not yours. You download the report from Google's Compliance Reports Manager, check its period and the services it covers, and add a bridge letter if its dates stop short of your period. Your own audit still tests how you run access, logging, monitoring and change management on GCP.
Does Google’s SOC 2 report make my company SOC 2 compliant?
No. Google’s report is an independent auditor’s opinion on Google’s controls over the services Google runs. Google names Ernst & Young LLP and Coalfire as its auditors on its SOC 2 page. A SOC 2 report is issued to one company about its own system, so yours has to cover how you configure and operate GCP.
In your report Google is a subservice organization. Under the carve-out method your system description names Google’s controls without testing them, and your auditor tests the controls you use to oversee Google, such as reviewing its report and bridge letter. Our carve-out versus inclusive guide explains the difference.
What stays with you is everything configured above the platform: IAM roles and group membership, Organization Policy, logging and alert handling, network exposure, customer-managed encryption keys, production changes and incident response. Google issues Type 2 reports only, but your own first audit can be Type 1 or Type 2; our Type 1 versus Type 2 guide covers that choice.
How do I get Google’s SOC 2 Type 2 report?
Download it from the Compliance Reports Manager. Google’s SOC 2 page sends customers there and tells potential customers to contact Google sales. Organizations that use Audit Manager can also download Google’s compliance documents, audit reports among them, with the Audit Manager Auditor role (roles/auditmanager.auditor) on the organization, as Google documents. Read the terms shown at download before you forward the report to your auditor or a customer, because they decide who may receive it.
Work through it in this order:
- Download the current core Google Cloud and Google Workspace SOC 2 Type II report and the latest bridge letter.
- Compare the report’s coverage period with your audit period or the date your customer needs coverage through.
- Check every GCP service in your system against the in-scope list on Google’s SOC 2 page. Compute Engine, Cloud Storage, GKE, Cloud Run, Cloud SQL and Cloud KMS are on it as of 2026-10-20. A small set of products, including Apigee Edge, AppSheet, Bare Metal Solution and Mandiant, has separate reports issued semi-annually or annually, available through Google sales or support.
- Read the auditor’s opinion, any exceptions and the subservice organization section. Our SOC 2 report reading guide walks through each part.
- List the complementary user entity controls (CUECs) and tie each one to a control you operate, or record why it does not apply. Our CUEC guide explains how to review them.
- File the report and letter in your vendor file with the download date.
A bridge letter covers the gap between a report’s end date and the date you need. Google’s page defines it as an attestation by Google’s management, summarizing material changes or issues in the control environment after the report period ended. Google writes one every month, and the Compliance Reports Manager lists letters for periods ending March 31, June 30, September 30 and December 31. For any other end date or product scope, Google tells customers to contact sales or support. A letter is not a new audit, so your auditor still relies on the report for the tested period. Our bridge letter guide covers the topic from the issuer’s side.
How often does Google issue its SOC 2 report?
Quarterly, and every report is Type 2. As stated on Google’s SOC 2 page, checked 2026-10-20: “The core Google Cloud and Google Workspace SOC 2 Type II reports are issued quarterly”, and “Google Cloud only issues SOC 2 Type II reports.” The page gives these periods:
| Report | Coverage period | Estimated issuance |
|---|---|---|
| First quarter | February 1 to January 31 | Late March |
| Second quarter | May 1 to April 30 | Late June |
| Third quarter | August 1 to July 31 | Late September |
| Fourth quarter | November 1 to October 31 | Late December |
Each period spans twelve months and the four periods overlap, so a new report adds three months to the previous one rather than starting over. On the same page, an FAQ describes a Type II report as assessing controls “within the past six months”. That is a general illustration; the table is the schedule for Google’s core reports, and the period printed on the report you download is the one to use. Read against the table, the most recent scheduled issuance as of 20 October 2026 is late September, covering August 1, 2025 to July 31, 2026. Confirm that on the report itself.
What GCP evidence does an auditor ask for, by control?
For each control, the auditor wants an artifact that shows the configuration, a record of someone acting on it, and dates that cover the whole audit period. The table lists GCP artifacts for the Security criteria that most GCP work lands on. Example controls for each criterion are in our security controls table, and the general request list is in the evidence request list.
| Criterion | GCP artifact | What it proves |
|---|---|---|
| CC6.1 logical access security | Organization Policy constraints exported from the organization, such as iam.allowedPolicyMemberDomains, iam.disableServiceAccountKeyCreation and storage.publicAccessPrevention | A preventive rule applies to every project beneath the folder or organization where it is set, and shows when it was set |
| CC6.1 | Data Access audit logs for the services that hold customer data | Who read or wrote data in those services, from the date you enabled the logs |
| CC6.2 and CC6.3 access granted, changed, removed | Export of Google group membership plus the IAM policy bindings that reference those groups (Cloud Asset Inventory can search IAM policies and export to BigQuery or Cloud Storage) | Who held which role on a given date, which you compare with HR and ticket records for joiners, movers and leavers |
| CC6.3 least privilege | IAM Recommender role recommendations, with the decision recorded for each | Excess permissions were found from actual usage and someone approved or declined the change |
| CC6.2 and CC6.3 | Admin Activity audit logs for IAM policy changes | Each grant or removal, who made it and when, to match against approved requests |
| CC7.2 monitoring for anomalies | Security Command Center findings and the exported Compliance page, with tickets for each finding you acted on or accepted | Detectors watched your configuration, and your team triaged what they raised |
| CC8.1 change management | Terraform pull requests with approvals, the plan output, and the CI run that applied it, matched to Admin Activity entries made by the CI service account | Infrastructure changes were reviewed before they were applied, and the log shows the pipeline did the applying |
For CC8.1, sample the Admin Activity entries made by people rather than the pipeline. Each is a change made outside the reviewed path, and your auditor can ask for its approval.
Which GCP defaults leave gaps in a Type 2 period?
Four defaults decide whether the evidence in that table exists for the whole period. All four come from Google’s documentation, checked 2026-10-20.
Data Access audit logs are disabled by default for every Google Cloud service except BigQuery. Admin Activity audit logs are always on and cannot be disabled. If you enable Data Access logs in month four of a twelve-month period, nothing exists for the first three, so enable them at the organization level before the period starts. Reading them takes the Private Logs Viewer role, and the Editor role does not include it.
Logs live in the _Default bucket, which keeps them 30 days unless you change it, and Data Access logs go there unless you route them elsewhere. Admin Activity logs go to the _Required bucket, whose retention you cannot change. Route both to a bucket or BigQuery dataset you control with a log sink and a retention period that covers the audit period.
Cloud Asset Inventory keeps asset history for up to 35 days, so a resource’s configuration from last quarter is not recoverable on demand. Schedule exports to BigQuery or Cloud Storage and keep them.
The IAM Recommender looks back at most 90 days of permission usage, and by default it generates no recommendations until it has 90 days of data (project-level settings can lower that to 30 or 60). Recommendations are not generated for every role. A recommendation list is not evidence of a review, so keep the record of each decision.
Security Command Center maps its detectors to the SOC 2 2017 Trust Services Criteria, but Google says those additional mappings are included for reference and not every control can be mapped. Use its findings as monitoring evidence and have your control owner confirm the mapping to your own criteria. Reports are generated daily and can be 24 hours stale.
What do I send a customer who asks about GCP in a security review?
Send Google’s current report with the bridge letter, then say which controls you operate yourself and where the evidence for them sits. A questionnaire answer of “we run on Google Cloud” tells the reviewer nothing about period, scope or what you configure. If your own SOC 2 report exists, send it with Google’s. Our vendor security questionnaire guide covers answering with evidence that matches each claim.
How should GCP shape scope and the choice of auditor?
Scope the system to the GCP projects that run or hold data for the service customers buy, and leave out sandboxes and abandoned projects. Every in-scope project, service account and environment creates evidence to produce. A SOC 2 readiness assessment before you sign an engagement will show which of the artifacts above you cannot produce yet.
GCP does not call for a special kind of auditor. Ask candidates whether they have audited companies on GCP, whether they accept log exports and infrastructure-as-code history as evidence, and how they handle Google as a subservice organization. Fees depend on scope, criteria and firm, and our Type 2 audit cost guide covers them; the auditor directory compares firms by fit.
More in Audit Preparation