Skip to main content
Five Steps for Cloud Compliance Readiness·A practical playbook for security teamsDownload
CIS Google Cloud Platform Foundation v5.0.0 · 2.1

Cloud Audit Logs should cover all services and users

  • Level 1
  • Logging and Monitoring

This check looks at the audit log configuration of your Google Cloud projects, in particular whether Data Access logs are enabled for all services and are not switched off for particular users. The safe setting is Admin Read, Data Read and Data Write logging on every service, with no exempted principals.

Why it matters

Google Cloud writes Admin Activity audit logs by default, and they cannot be turned off. Data Access logs, which record who read or changed your data, are off by default for most services; only some BigQuery logs are always on. Without them, a question like 'who read this bucket last Tuesday' has no answer.

Audit settings also combine across the resource hierarchy: a project can add logging or exemptions on top of what its folder or organization sets, but it cannot remove what a parent enables. That makes the organization level the best place to set the baseline. Exempting a principal stops the selected log types for that principal, which is easy to forget and creates a blind spot.

Source: Google Cloud documentation, Configure Data Access audit logs.

How to check it yourself

In the Google Cloud console open IAM & Admin > Audit Logs, select the project (then the folder and organization), and look at the Data Access configuration table. Each service should show Admin Read, Data Read and Data Write ticked, and the exempted principals column should be empty.

Read-only with the gcloud CLI. Replace the placeholder with your own project ID:

gcloud projects get-iam-policy PROJECT_ID --format="yaml(auditConfigs)"

This only shows what is set on the project itself, not what is inherited from a folder or the organization, so repeat the check with gcloud organizations get-iam-policy ORG_ID and for folders. A healthy result contains an allServices entry with the three log types and no exemptedMembers lines.

How to fix it

In the console, go to IAM & Admin > Audit Logs, choose the project, folder or organization, select the services (or set the default configuration so future services inherit it), tick Admin Read, Data Read and Data Write in the Permission types tab, remove exempted principals, and save.

With the command line the pattern is: export the policy, edit only the auditConfigs section, and write it back. Keep the bindings and etag sections intact, because writing a policy without bindings removes all access.

# 1. export
gcloud projects get-iam-policy PROJECT_ID --format=json > policy.json
# 2. edit policy.json: add under auditConfigs
#    {"service":"allServices","auditLogConfigs":[
#      {"logType":"ADMIN_READ"},{"logType":"DATA_READ"},{"logType":"DATA_WRITE"}]}
# 3. write back (changes the project, run it yourself after review)
gcloud projects set-iam-policy PROJECT_ID policy.json

ConfigCobra never writes to your Google Cloud; it reports the finding and suggests these steps.

What changes when you fix it

Log volume goes up, sometimes by a lot on busy storage and BigQuery workloads, and Google notes that Data Access logs can add charges to the log usage of your project. Review where the logs are routed and how long they are kept before enabling them everywhere.

People who read the logs need the Private Logs Viewer role, because the Editor role does not include access to Data Access logs. Nothing changes for end users or running workloads; the effect is on log storage, cost and whoever monitors the logs.

Included in

BenchmarkCIS IDProfile
CIS Google Cloud Platform Foundation v5.0.02.1Level 1

Check this on your Google Cloud

ConfigCobra runs this check with every other control of the CIS Google Cloud Platform Foundation Benchmark, read-only.

Get in touch

Let's talk.

Whether you're evaluating ConfigCobra, running an audit, or managing a client fleet — we respond within one business day.

Free trial