Compliancemanzill.com
CIS Google Cloud Platform Foundation Benchmark v1.2.0

CIS Google Cloud Platform Foundation Benchmark v1.2.0/Logging and Monitoring/25 of 83

2.10Ensure that the log metric filter and alerts exist for Cloud Storage IAM permission changes

Control family: Logging and Monitoring

Control description

It is recommended that a metric filter and alarm be established for Cloud Storage Bucket IAM changes.

How to implement

ResponsibilityCustomerYou configure and operate this in your own cloud accounts.

A changed IAM policy on a Cloud Storage bucket can make its data readable by people who shouldn't see it, or by everyone. Every change to bucket permissions raises an alert so it can be checked.

Before you start

The same on every cloud, before the steps in the tabs.

  • Agree who receives these alerts, how quickly they respond and how they record what they found.
  • Decide which projects to cover: every project, or the project that holds an organization-wide log sink (2.2), since a logs-based metric only counts the logs in its own project.

Evidence

  • The alert routing and the response notes for alerts raised during the period

On Google Cloud the tasks create a logs-based metric in Cloud Logging that counts Cloud Storage permission changes, alert on it in Cloud Monitoring, and confirm with Security Command Center.

Task 1Count the changes with a logs-based metric

  1. Sign in to the Google Cloud console at console.cloud.google.com and pick the project to monitor.
  2. Open Logging > Log-based Metrics and choose Create metric.
  3. Under Metric type, select Counter.
  4. Under Details, enter bucket-iam-changes as the Log-based metric name, add a short description and set Units to 1.
  5. Under Filter selection, replace the text in the Build filter box with this filter, exactly: resource.type=gcs_bucket AND protoPayload.methodName="storage.setIamPermissions"
  6. Choose Create metric.
  7. Check it: the metric appears under User-defined metrics.

Task 2Alert the security team when it happens

  1. On Log-based Metrics, under User-defined metrics, find bucket-iam-changes, open its More menu and choose Create alert from metric.
  2. Choose Next, keep the threshold so a single matching entry triggers the alert, and enter a Condition name.
  3. Choose Next, open Notification channels, select the security team's channel and choose OK (add an email or chat channel first under Monitoring > Alerting > Edit notification channels if there is none).
  4. Enter an Alert name such as bucket-iam-changes-alert, and choose Create policy.
  5. Check it: grant and remove a role on a test bucket in the same project, and confirm the notification arrives.

Task 3Keep it checked with the Security Health Analytics finding BUCKET_IAM_NOT_MONITORED

  1. Open Security Command Center > Findings for the organization (Security Health Analytics runs on the Premium tier for most detectors).
  2. In the query editor, filter on category BUCKET_IAM_NOT_MONITORED with state ACTIVE, and select Apply.
  3. Open each finding, read the resource and the explanation it gives, and create the metric and alert in the project it names.
  4. Check it: after the next Security Health Analytics scan, no active BUCKET_IAM_NOT_MONITORED finding remains.

Evidence

  • Logging > Log-based Metrics, showing bucket-iam-changes with its filter
  • Monitoring > Alerting, showing the bucket-iam-changes-alert policy and its notification channel
  • Security Command Center, with no active BUCKET_IAM_NOT_MONITORED 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.