CIS Google Cloud Platform Foundation Benchmark v1.2.0/Logging and Monitoring/16 of 83
2.1Ensure that Cloud Audit Logging is configured properly across all services and all users from a project
Control family: Logging and Monitoring
Control description
It is recommended that Cloud Audit Logging is configured to track all admin activities and read, write access to user data.
How to implement
ResponsibilityCustomerYou configure and operate this in your own cloud accounts.
Admin Activity audit logs are always on, but Data Access logs, which record who read or changed data, are off for most services until you turn them on. The benchmark wants Admin Read, Data Read and Data Write logged for every service, with nobody exempted, so every access can be traced.
Before you start
The same on every cloud, before the steps in the tabs.
- Estimate the extra log volume and cost, and set a budget alert for logging before turning Data Access logs on everywhere.
Evidence
- The logging cost estimate and the budget alert
Not applicable. This benchmark covers Google Cloud only.
Not applicable. This benchmark covers Google Cloud only.
On Google Cloud the tasks set the default audit configuration in IAM & Admin, remove exemptions, and watch with Security Command Center.
Task 1Turn on Data Access audit logs for all services
- Sign in to the Google Cloud console at console.cloud.google.com and pick the organization (or each project) in the project picker.
- Open IAM & Admin > Audit Logs and choose Set default configuration.
- On the Log types tab, select Admin Read, Data Read and Data Write, and choose Save.
- On the Exempted principals tab, choose Delete next to each listed principal, and choose Save.
- Back on Audit Logs, open each service that still shows an exempted principal and remove it the same way.
- Check it: Logging > Logs Explorer shows data_access entries for the services you use.
Task 2Keep it checked with the Security Health Analytics finding AUDIT_LOGGING_DISABLED
- Open Security Command Center > Findings for the organization (Security Health Analytics runs on the Premium tier for most detectors).
- In the query editor, filter on category AUDIT_LOGGING_DISABLED with state ACTIVE, and select Apply.
- Open each finding, read the resource and the explanation it gives, and turn on the missing log types for the resource it names.
- Check it: after the next Security Health Analytics scan, no active AUDIT_LOGGING_DISABLED finding remains.
Evidence
- The Audit Logs default configuration, with all three log types on and no exemptions
- Security Command Center, with no active AUDIT_LOGGING_DISABLED finding
Console steps as of 5 November 2026. Not every step has been confirmed in a live console yet, and menus and labels can move between releases, so look for the nearest match if one has changed.