# SOC 2 with AI on Google Cloud

> SOC 2 on GCP: evidence by service area, what Google covers and what you do, and prompts to prepare with an AI assistant. CPA firm audit from $4,400.

- Canonical: https://auditsuisse.com/soc-2-with-ai-on-google-cloud
- Language: en
- Author: Sébastien Ruosch, CPA — Director of Audits
- Published: 2026-11-15
- Updated: 2026-11-15
- Alternates: fr → https://auditsuisse.com/fr/soc-2-avec-l-ia-sur-google-cloud, es → https://auditsuisse.com/es/soc-2-con-ia-en-google-cloud

SOC 2 on your stack

 The short answer

For SOC 2 on GCP (Google Cloud), the evidence is a set of exports and configuration listings from your own projects: IAM bindings, audit log settings, keys, firewall rules, backups and deployment records. Each one states its source, command or query, date and record count. An AI assistant can write the read-only gcloud commands; your team runs and checks them. Google Cloud is a subservice organization in your report, and a licensed CPA firm examines what you provide.

## Key takeaways

- Access is inherited down the resource hierarchy, so a project-by-project listing shows only part of who has access.
- Service accounts and their keys are identities and belong in the access population.
- The assistant drafts commands; a person runs them and sends the output unedited. AI-guided preparation, CPA-performed audit.

## What evidence does a SOC 2 auditor ask for on Google Cloud?

Your auditor’s request list sets the exact items; these are the types. Most support CC6 Logical and Physical Access Controls, CC7 System Operations and CC8 Change Management: see the [SOC 2 controls list](https://auditsuisse.com/soc-2-controls-list-by-trust-services-criteria).

SOC 2 evidence on Google Cloud by service area: where the evidence lives and the artifact an auditor asks for.

| Service area | Google Cloud services | Artifact an auditor asks for |
| --- | --- | --- |
| Identity and access | Google Cloud IAM, Cloud Identity or Google Workspace, Cloud Asset Inventory | The IAM bindings at organization, folder and project level, the service accounts and their keys with creation dates, and the 2-Step Verification status of users. For selected joiners and leavers, the request and the date access changed. |
| Logging and monitoring | Cloud Audit Logs, Cloud Logging, Cloud Monitoring, Security Command Center | The audit log configuration showing which Data Access logs are enabled, the log sinks and retention settings, the alerting policies, and the period’s Security Command Center findings with the ticket for each. |
| Encryption and key management | Cloud KMS; settings of Cloud Storage, Compute Engine disks and Cloud SQL | The listing of keys with rotation schedule and the roles granted on them, and the resources that use customer-managed keys where your policy requires them. |
| Network | VPC firewall rules and policies, Cloud Armor, Organization Policy | The listing of firewall rules, with those open to any address marked, the instances with external IP addresses, the buckets open to the public, and the organization policy constraints in force. |
| Backups and recovery | Cloud SQL backups, disk snapshot schedules, Backup and DR Service | Backup settings per database, snapshot schedules, the period’s backup runs, and the record of a restore test (what, when, by whom, result). |
| Change and deployment | Cloud Build, Cloud Deploy, Terraform, Cloud Audit Logs | The population of production deployments for the period. For selected changes, the pull request, review and approval. Admin Activity log entries for console changes. |

## What does Google cover, and what stays with us?

Google Cloud describes its model as shared responsibility and shared fate. Its page says the provider remains responsible for the underlying network and infrastructure, and the customer for access policies and data. The rest depends on the service: more is yours with virtual machines, less with managed services. Read [Google Cloud’s page on shared responsibility and shared fate](https://docs.cloud.google.com/architecture/framework/security/shared-responsibility-shared-fate) for the detail.

In your report, Google Cloud is a subservice organization, normally carved out. Your description names it and the services you use. See [subservice organizations: carve-out vs inclusive](https://auditsuisse.com/subservice-organizations-carve-out-vs-inclusive) and [vendor management for SOC 2](https://auditsuisse.com/vendor-management-for-soc-2-compliance). The related guide for the other two clouds, [SOC 2 on AWS and Azure](https://auditsuisse.com/soc-2-on-aws-and-azure), applies the same model.

## How do the organization, folders and projects change what we export?

Google Cloud resources sit in a hierarchy: organization, folders, projects. A role granted on the organization or on a folder is inherited by every project beneath it. A listing taken project by project therefore misses inherited access. Export the bindings at each level, or search the whole organization with Cloud Asset Inventory, and write the scope on the artifact: organization ID, folder, project IDs. Start from the projects in scope (see [how to scope systems for SOC 2](https://auditsuisse.com/how-to-scope-systems-for-soc-2)).

Service accounts are identities too. Their role bindings and keys belong in the same population as your people’s access, and in your [user access review](https://auditsuisse.com/soc-2-user-access-review). Auditors test such listings for completeness and accuracy before relying on them. See [tests of controls, IPE and IUC](https://auditsuisse.com/tests-of-controls-ipe-iuc) and [audit evidence management best practices](https://auditsuisse.com/audit-evidence-management-best-practices).

## Which prompts write read-only gcloud commands for these exports?

Run the commands yourself with an identity that can only read. Google Cloud has predefined roles for this, such as Security Reviewer. The general method is in [collect SOC 2 evidence with an AI agent](https://auditsuisse.com/soc-2-evidence-collection-with-ai-agents). Before you paste output into an assistant, read [is it safe to put security documents into ChatGPT or Claude](https://auditsuisse.com/is-it-safe-to-use-ai-for-soc-2).

### Prompt: an access listing across the hierarchy

```
You are helping my team prepare SOC 2 access evidence from Google Cloud. I will run every command myself with a read-only role.

Ask me first for our resource hierarchy (organization, folders, projects), which projects are in scope, whether our identities come from Google Workspace or Cloud Identity, and how access is granted today. Wait for my answers.

Then write gcloud commands that list: IAM bindings at organization, folder and project level; service accounts in each project; user-managed service account keys with creation dates. Use only list, describe, get-iam-policy and search commands. Never write a command that changes configuration or grants access. Do not create or alter evidence.

Each command saves its raw output to a file with a header: source (organization, folder or project ID), the exact command, date and time in UTC, and record count. Tell me which bindings a project inherits from a higher level.

Mark every assumption as [ASSUMPTION].
List anything you assumed that I need to verify.
```

### Prompt: listings for logging, network and backups

```
I need read-only configuration listings from Google Cloud for a SOC 2 audit: audit log configuration and log sinks, firewall rules, instances with external IP addresses, Cloud SQL backup settings and disk snapshot schedules.

Ask me which projects are in scope, which of these services we use, and how we deploy infrastructure today. Wait for my answers.

Then write one gcloud command per listing, looping over the projects I named. Use only list and describe commands; never change configuration. For each output file, record the project ID, the exact command, the date and the record count. If a command returns nothing for a project, record zero; do not skip the project.

Do not create or alter evidence, and do not judge whether a setting is adequate; a person on my team decides. Mark every assumption as [ASSUMPTION].
List anything you assumed that I need to verify.
```

AI-written policies and descriptions are acceptable only if they describe what your company actually does. The audit tests how controls operate, not how documents read. See [what auditors accept from AI](https://auditsuisse.com/what-auditors-accept-from-ai).

## Who does what

Auditsuisse explains the criteria and sends its evidence request list once engaged. Your management designs and operates the controls; the firm does not configure your projects or choose your controls.

Who does what when you prepare SOC 2 evidence on Google Cloud.

| Task | Your team (with or without AI) | Your AI assistant | The auditor |
| --- | --- | --- | --- |
| Write export commands | Reviews each command before it runs | Drafts gcloud list and describe commands with the header for each output | No role |
| Run the exports | Runs them with a read-only role and keeps the raw output | Needs no access to your projects | Requests the populations and listings on the evidence request list |
| Review inherited access | Decides whether each binding is still needed | Points out bindings inherited from a folder or the organization | Tests that the listing is complete and accurate, then inspects selected items |
| Change a binding or a rule | Decides and makes the change | Explains the setting and its options | No role |

## Zero-Platform SOC 2 Audit: the fee

A Zero-Platform SOC 2 audit from Auditsuisse costs $4,400 for Type I and $5,500 for Type II for companies of up to 50 people, fixed fee, Security criteria.

No compliance platform is required, so you save the platform fees, which start at about $10,000 to $15,000 a year for a GRC platform (an illustrative figure, not any vendor’s price).

Zero-Platform SOC 2 Audit fees for companies with 1–50 employees (USD, fixed fee, Security Trust Services Category). Fees as of November 15, 2026.

| Company headcount | SOC 2 Type I | SOC 2 Type II | Type I + Type II (combined) |
| --- | --- | --- | --- |
| 1–50 employees | $4,400 | $5,500 | $7,700 |

[See all headcount tiers](https://auditsuisse.com/zero-platform-soc-2-audit#fees)

Fees as of November 15, 2026.

## Free kit: prepare for SOC 2 without a platform

The prompt library from these guides, a policy index, the gap-assessment scoring sheet, the risk register template and the cost worksheet, as CSV and Markdown, with a short guide to the workflow. Free to use with attribution; not a substitute for an examination. Our evidence request list is not part of the kit: you receive it once the engagement letter is signed.

## Frequently asked questions

### Is Google Cloud treated differently from AWS or Azure in a SOC 2 audit?

No. The model is the same; the service names and commands differ. Compare [SOC 2 with AI on AWS](https://auditsuisse.com/soc-2-with-ai-on-aws) and [SOC 2 with AI on Azure](https://auditsuisse.com/soc-2-with-ai-on-azure).

### Does Google Workspace belong in the same evidence?

For identity, yes, if your people sign in with Workspace or Cloud Identity accounts: the user list, 2-Step Verification status and administrator roles come from the admin console. Whether Workspace itself is in scope is a scoping decision for your management.

### Do we need a compliance platform to collect Google Cloud evidence?

No. A platform connects to Google Cloud and collects these listings continuously. Without one, you run the exports and send them to the auditor. The [Zero-Platform SOC 2 audit](https://auditsuisse.com/zero-platform-soc-2-audit) is built for that, and the [guide to SOC 2 with AI](https://auditsuisse.com/soc-2-with-ai) covers the rest of the preparation.

## Sources & further reading

AICPA, [2017 Trust Services Criteria (with revised points of focus, 2022)](https://www.aicpa-cima.com/resources/download/2017-trust-services-criteria-with-revised-points-of-focus-2022); SSAE No. 18, AT-C sections 105 and 205. Google Cloud, [Shared responsibilities and shared fate on Google Cloud](https://docs.cloud.google.com/architecture/framework/security/shared-responsibility-shared-fate).

**Related:** [SOC 2 with AI on AWS](https://auditsuisse.com/soc-2-with-ai-on-aws), [SOC 2 with AI on Azure](https://auditsuisse.com/soc-2-with-ai-on-azure), [SOC 2 on AWS and Azure](https://auditsuisse.com/soc-2-on-aws-and-azure).

Product names are trademarks of their owners. Auditsuisse is not affiliated with these vendors.

---
Source: https://auditsuisse.com/soc-2-with-ai-on-google-cloud · This Markdown edition is generated from the same content as the HTML page.
