SOC 2 CC7 on Google Cloud covers monitoring, incident response and recovery, and Google handles each of these for Google infrastructure under Google's SOC 2 report. The customer owns all three for customer workloads: which logs are kept and for how long, who reviews alerts, how incidents are handled, and whether backups can be restored.
At a glance
- Logs on by default: Admin Activity and System Event audit logs, kept 400 days in the
_Requiredbucket at no charge. Policy Denied logs are also on by default and billed for storage. - Logs to turn on: Data Access audit logs (off by default except BigQuery), VPC Flow Logs, and firewall rule logging
- Default retention: 30 days in the
_Defaultbucket, configurable up to 3,650 days for project-level buckets - Detection: Security Command Center Premium for threat detection and full misconfiguration detectors. New Standard-tier organizations get Compliance Manager Security Essentials and vulnerability findings without Security Health Analytics.
- Recovery gap to check: Cloud SQL instances created with gcloud, Terraform or the API have no automated backups unless backups are set explicitly
- Google's incident commitment: Google notifies customers of a data incident promptly and without undue delay, under the Cloud Data Processing Addendum, sent to the notification email address on file
What does the shared responsibility model mean for SOC 2 CC7 on Google Cloud?
The shared responsibility model divides SOC 2 CC7 the same way as access control: Google monitors, responds to and recovers Google infrastructure, and the customer does the same for everything the customer builds and configures. Google's SOC 2 Type II report is the evidence for Google's side. Customer controls are the evidence for the rest.
| CC7 activity | Google's part | Customer's part |
| Logging | Writes Admin Activity and System Event audit logs that cannot be turned off | Turns on Data Access logs, VPC Flow Logs and firewall logging, sets retention, protects logs from deletion |
| Detection | Monitors Google infrastructure and services | Configures Security Command Center, Google SecOps or another SIEM, and reviews the findings |
| Incident response | Responds to incidents in Google infrastructure and notifies customers of data incidents | Operates an incident response process for workloads, users and data, and notifies the company's own customers |
| Recovery | Keeps managed services available within published SLAs | Configures backups, retention and restore testing for company data and services |
Customer controls also depend on the service model. Data Access logs, backup settings and alert routing are customer settings on every GCP service. Patch and vulnerability work for the operating system is a customer task on Compute Engine and a Google task on managed services such as Cloud SQL and GKE Autopilot. The SOC 2 access controls on GCP guide covers the service-model split in detail.
Which SOC 2 CC7 criteria does Google Cloud cover, and which does the customer own?
Every SOC 2 CC7 criterion stays with the customer for customer workloads, with Google features doing much of the work. The table below maps each CC7 criterion to the main GCP features involved.
| SOC 2 criterion | What the criterion asks (paraphrased) | Main GCP features |
| CC7.1 Detection of changes and vulnerabilities | Configuration changes and new vulnerabilities are detected and monitored | Security Command Center, Cloud Asset Inventory feeds, VM Manager, Artifact Analysis, Web Security Scanner |
| CC7.2 Monitoring for anomalies | Systems are monitored for anomalies that point to malicious acts, errors or natural disasters | Cloud Audit Logs, aggregated log sinks, log-based alerts, Event Threat Detection, Google SecOps |
| CC7.3 Evaluation of security events | Security events are evaluated to decide whether they are incidents | Google SecOps detection rules and cases, Security Command Center findings and mute rules |
| CC7.4 Incident response | A defined process contains, fixes and communicates incidents | Incident response plan, Essential Contacts, SecOps SOAR playbooks, Personalized Service Health |
| CC7.5 Recovery from incidents | Activities to recover from incidents are identified and carried out | Backup and DR backup vaults, Cloud SQL point-in-time recovery, Cloud Storage soft delete and versioning |
The criterion text is AICPA copyrighted material, so the descriptions are paraphrased. The SOC 2 Trust Services Criteria guide covers the full set.
Which GCP logs are on by default, and which must be turned on for SOC 2?
Google Cloud writes some audit logs automatically, but the logs a SOC 2 auditor asks about for data access and network traffic are off until the customer turns them on.
| GCP log type | Default | Setting for a SOC 2 audit |
| Admin Activity audit logs | Always on, 400 days in _Required, no charge | Nothing to turn on. Route a copy to the central log bucket for longer retention and analysis. |
| System Event audit logs | Always on, 400 days in _Required, no charge | Same as Admin Activity |
| Data Access audit logs | Off, except BigQuery (on and cannot be turned off) | Turn on for services that hold in-scope data, such as Cloud Storage and Cloud SQL. Data Access logs can be high volume, so scope them to sensitive projects. |
| Policy Denied audit logs | On, billed for storage | Keep. Exclusion filters can drop them, but they show blocked access attempts. |
_Default bucket (all other logs) | 30 days | Raise retention for project-level buckets, or route logs to a dedicated bucket. Folder and organization _Default buckets cannot take custom retention. |
| VPC Flow Logs | Off on new subnets | Turn on for subnets in production |
| Firewall rule logging | Off for VPC firewall rules, set per rule on firewall policies | Turn on for allow and deny rules on production traffic |
A SOC 2 Type II auditor samples events across the whole observation period, so log retention has to cover the full period plus time for the audit itself. Many companies set 365 days. Retention beyond 30 days costs $0.01 per GiB per month.
A central logging setup for a SOC 2 audit on Google Cloud uses one aggregated sink at the organization level to route audit logs from every project into a log bucket in a dedicated logging project. A locked log bucket stops anyone from changing retention or deleting the bucket before the retention period ends. Bucket lock is permanent and can only be set with gcloud or the API, so confirm the retention period first.
gcloud logging sinks create org-audit-sink \
logging.googleapis.com/projects/LOG_PROJECT/locations/global/buckets/audit-logs \
--organization=ORG_ID --include-children \
--log-filter='logName:"cloudaudit.googleapis.com"'
gcloud logging buckets update audit-logs --location=global --project=LOG_PROJECT --locked
How do you meet SOC 2 CC7.1 detection of changes and vulnerabilities on Google Cloud?
SOC 2 CC7.1 on Google Cloud is met by detecting configuration drift and new vulnerabilities continuously, then tracking each finding to a fix or an accepted risk.
Key insight
Example CC7.1 control on GCP.
Security Command Center scans the organization continuously for misconfigurations and vulnerabilities. Critical and high findings create tickets automatically and are fixed within the timelines set in the vulnerability management policy. Changes to IAM policies and organization policies trigger alerts through Cloud Asset Inventory feeds.
| GCP feature for CC7.1 | What the feature does | Notes |
| Security Command Center | Misconfiguration and vulnerability findings across the organization | Premium includes all Security Health Analytics detectors. New Standard organizations get Compliance Manager Security Essentials and vulnerability findings instead. |
| Cloud Asset Inventory feeds | Pub/Sub messages when resources, IAM policies or organization policies change | Conditions can narrow a feed, for example to IAM bindings that grant access to allUsers. Feed changes take up to 10 minutes to apply. |
| VM Manager | OS inventory, patch jobs and vulnerability reports for Compute Engine | Needs the OS Config agent. CVE data reaches Security Command Center within about two hours. |
| Artifact Analysis | Scans container images pushed to Artifact Registry | Covers images for GKE and Cloud Run |
| Web Security Scanner | Scans public web applications for common vulnerabilities | Weekly managed scans come with Premium |
Evidence for SOC 2 CC7.1 on GCP: the Security Command Center findings export with ticket links, patch job history from VM Manager, and the feed configuration.
gcloud asset feeds list --organization=ORG_ID
gcloud scc findings list organizations/ORG_ID --filter='state="ACTIVE" AND severity="HIGH"'
gcloud compute os-config patch-jobs list --project=PROJECT_ID
The CC7.1 vulnerability management guide covers remediation timelines and risk acceptance.
How do you meet SOC 2 CC7.2 security monitoring on Google Cloud?
SOC 2 CC7.2 on Google Cloud is met by sending the right logs to one place, keeping them for the full audit period, and alerting on the events that point to an attack or a mistake.
Key insight
Example CC7.2 control on GCP.
Audit logs from all projects are routed through an organization-level sink to a locked log bucket with 365-day retention. Google SecOps ingests Google Cloud logs and alerts the on-call engineer on high-risk events, including IAM role grants to external identities, service account key creation, and changes to logging configuration.
| GCP feature for CC7.2 | What the feature does | Notes |
| Aggregated log sink and locked bucket | One central, tamper-resistant copy of audit logs | See the logging setup above |
| Log Analytics (Observability Analytics) | SQL queries on log buckets | GA. Upgrading a bucket is one-way and works only for unlocked project buckets, so upgrade before locking. |
| Log-based alerts | Alerts when a log entry matches a filter | One condition per policy, limited to 20 alerts a day. Logs from folders or the organization need a log-based metric or a SIEM instead. |
| Event Threat Detection | Detects threats in logs, such as credential misuse and data exfiltration | Security Command Center Premium |
| Google SecOps | SIEM with detection rules across Google Cloud and other sources | Direct ingestion sends Admin Activity and System Event logs by default, with Data Access logs optional. No backfill, so turn ingestion on before the observation period starts. Default retention is 12 months. |
Evidence for SOC 2 CC7.2 on GCP: the sink and bucket configuration, a list of alert policies or SIEM rules with their owners, and a sample of alerts with their review records.
gcloud logging sinks list --organization=ORG_ID
gcloud logging buckets describe audit-logs --location=global --project=LOG_PROJECT
gcloud alpha monitoring policies list --project=PROJECT_ID
The CC7.2 security monitoring guide and the security logging and monitoring architecture guide cover log design beyond Google Cloud.
How do you meet SOC 2 CC7.3 security event evaluation on Google Cloud?
SOC 2 CC7.3 on Google Cloud is met by giving every alert an owner, a triage decision and a record. Auditors test CC7.3 by sampling alerts and checking that each one was reviewed and either closed with a reason or escalated as an incident.
| GCP feature for CC7.3 | What the feature does | Notes |
| Google SecOps detection rules | YARA-L 2.0 rules that create alerts and open cases | Curated detections for cloud threats depend on the SecOps package. The Standard package includes a subset. |
| Google SecOps cases | Record of triage, decisions and links to related alerts | Case history is also CC7.3 evidence |
| Security Command Center mute rules | Hide expected findings so reviewers see real ones | Dynamic mute rules are recommended. Record the reason for each rule, because an auditor will ask. |
| Security Command Center continuous export | Sends findings to Pub/Sub for ticketing, or to BigQuery for reporting | Notification configs connect findings to Jira or ServiceNow through Pub/Sub |
| Attack exposure scores and attack paths | Ranks findings by how reachable high-value resources are | Security Command Center Premium, activated at the organization level |
Evidence for SOC 2 CC7.3 on GCP: a sample of alerts or findings, each with the linked case or ticket, the triage decision, and the time to review. The CC7.3 security event evaluation guide covers triage criteria, and the ticketing and SLA guide covers how to evidence response times.
How do you meet SOC 2 CC7.4 incident response on Google Cloud?
SOC 2 CC7.4 on Google Cloud is met by an incident response plan that names how cloud incidents are contained, who is told, and how Google's own incident notices reach the right people.
Key insight
Example CC7.4 control on GCP.
The incident response plan covers Google Cloud scenarios, including compromised credentials, exposed storage and a Google service outage. Security and technical Essential Contacts are set at the organization level. The plan is tested with a tabletop exercise each year.
| GCP feature for CC7.4 | What the feature does | Notes |
| Essential Contacts | Sends Google notifications by category (Security, Technical, Legal and others) to named contacts | Set at the organization level so notices reach a monitored group mailbox |
| Data incident notification | Google notifies customers promptly and without undue delay after becoming aware of a data incident | Commitment in the Cloud Data Processing Addendum, sent to the notification email address on file |
| Personalized Service Health | Shows Google Cloud incidents that affect the customer's projects | Alerts can be routed through Cloud Monitoring |
| Google SecOps SOAR playbooks | Automated containment and notification steps, such as disabling a user or revoking a key | Case-level playbooks are in Preview |
Containment steps to write into the plan for Google Cloud: disable or delete a compromised service account key, suspend a user in the identity provider, revoke a Privileged Access Manager grant, remove public access from a bucket, and snapshot affected disks before changing them. The CC7.4 incident response guide covers the plan structure.
Evidence for SOC 2 CC7.4 on GCP: the incident response plan, the Essential Contacts configuration, tabletop exercise records, and records of any real incidents in the period.
gcloud essential-contacts list --organization=ORG_ID
How do you meet SOC 2 CC7.5 incident recovery on Google Cloud?
SOC 2 CC7.5 on Google Cloud is met by backups that an attacker or a mistake cannot delete, recovery targets for each system, and restore tests that prove the backups work.
Watch out
Do not assume Cloud SQL backups are on for instances created with Terraform, gcloud or the API.
Automated backups are on by default only for instances created in the Google Cloud console. Point-in-time recovery needs automated backups, and the default log retention for point-in-time recovery is 7 days on Enterprise edition and 14 days on Enterprise Plus.
| GCP feature for CC7.5 | What the feature does | Notes |
| Backup and DR backup vaults | Backups with enforced minimum retention, from 1 day to 99 years, that nobody can delete early | The retention setting can be locked permanently. Since November 1, 2026, projects with enforced-retention vaults get an automatic lien that blocks project deletion. |
| Cloud SQL automated backups and point-in-time recovery | Daily backups plus transaction logs for restore to a specific time | Set backups explicitly in infrastructure code |
| Compute Engine snapshot schedules | Scheduled disk snapshots | No vault-level enforced retention |
| Cloud Storage soft delete | Keeps deleted objects for 7 days by default, configurable up to 90 days | On by default. Pair with Object Versioning for overwritten objects. |
Evidence for SOC 2 CC7.5 on GCP: backup plan and vault configuration, Cloud SQL backup settings, and a restore test record for each critical system with the date, the result and the time taken.
gcloud sql instances describe INSTANCE --format='yaml(settings.backupConfiguration)'
gcloud storage buckets describe gs://BUCKET --format='yaml(soft_delete_policy)'
The CC7.5 incident recovery guide covers recovery planning in general.
What SOC 2 CC7 evidence do Security Command Center, Wiz and Google SecOps provide?
Security Command Center, Wiz and Google SecOps each cover a different part of SOC 2 CC7 on Google Cloud. The triage records, incident reports and restore tests come from the security program that operates the tools.
| Tool | SOC 2 CC7 evidence the tool provides | What the program still adds |
| Security Command Center | CC7.1 misconfiguration and vulnerability findings, CC7.2 threat detection (Premium), finding exports for CC7.3 | Remediation tickets, mute rule reasons, review of findings |
| Wiz | CC7.1 posture and vulnerability findings across GCP, AWS and Azure | The same remediation and review records |
| Google SecOps | CC7.2 detection, CC7.3 cases, CC7.4 SOAR playbooks | On-call ownership, triage decisions, the incident response plan |
The Enterprise tier of Security Command Center is deprecated and shuts down on or after May 21, 2027, so Premium is the tier to plan around.
In what order should SOC 2 CC7 controls be rolled out on Google Cloud?
The order below gets logging in place first, because Google Cloud logs exist only from the day collection starts, and the observation period needs a full record.
- Create the organization-level sink and central log bucket, and set retention. Lock the bucket once the retention period is final.
- Turn on Data Access logs for in-scope services, VPC Flow Logs and firewall logging.
- Start Google SecOps ingestion, or connect another SIEM. Ingestion has no backfill.
- Enable Security Command Center Premium or Wiz, and route findings to ticketing.
- Set Essential Contacts and update the incident response plan for Google Cloud scenarios.
- Configure Backup and DR vaults and explicit Cloud SQL backups, then run a restore test.
Get SOC 2 CC7 right on GCP
Truvo builds and operates the effective security program behind the logging, detection and recovery evidence.
Frequently asked questions about SOC 2 monitoring on Google Cloud
How long should Google Cloud logs be kept for SOC 2?
SOC 2 sets no fixed log retention period. Log retention for a SOC 2 Type II audit has to cover the whole observation period plus time for the audit. Many companies keep Google Cloud audit logs for 365 days in a locked log bucket. Admin Activity logs stay in _Required for 400 days at no charge.
Are Data Access audit logs required for SOC 2?
SOC 2 names no specific Google Cloud logs. Auditors testing CC7.2 expect records of access to in-scope data, and Data Access audit logs provide those records. Turn them on for services holding customer data, such as Cloud Storage and Cloud SQL. BigQuery Data Access logs are always on.
Does Google notify customers about security incidents?
Google commits in the Cloud Data Processing Addendum to notify customers promptly and without undue delay after becoming aware of a data incident. The notice goes to the notification email address on file. Essential Contacts and Personalized Service Health route other security and service notices to named people.
Does the Standard tier of Security Command Center cover SOC 2 CC7?
The Standard tier of Security Command Center covers part of CC7.1. New Standard organizations get Compliance Manager Security Essentials and vulnerability findings. Threat detection for CC7.2, the full set of misconfiguration detectors, and the SOC 2 framework in Compliance Manager need Premium.
Do Cloud SQL instances have backups turned on by default?
Cloud SQL turns on automated backups by default only for instances created in the Google Cloud console. Instances created with gcloud, Terraform or the Admin API need backups set explicitly. Point-in-time recovery also needs automated backups.
Sources
- AICPA Trust Services Criteria (TSC section 100), 2017, revised points of focus 2022
- Cloud Audit Logs overview
- Log storage and retention
- Log buckets and bucket lock
- Aggregated sinks
- Log-based alerting policies
- VPC Flow Logs
- Cloud Asset Inventory feeds
- Security Command Center service tiers
- SCC continuous exports to Pub/Sub
- SCC attack exposure
- VM Manager
- Web Security Scanner
- Google SecOps data retention
- Google SecOps curated detections
- Google SecOps Google Cloud ingestion
- Essential Contacts
- Cloud Data Processing Addendum
- Personalized Service Health
- Backup and DR backup vaults
- Cloud SQL point-in-time recovery
- Cloud Storage soft delete
- Google Cloud SOC 2
Ready to Start Your Compliance Journey?
Get a clear, actionable roadmap with our readiness assessment.
Contact Us
Sample SOC 2 Control List
Input your email to download the list.
About the Author
Former security architect for Bank of Canada and Payments Canada. 20+ years building compliance programs for critical infrastructure.