CIS Google Cloud Platform Foundation Benchmark v1.2.0/Logging and Monitoring/19 of 83
2.4Ensure log metric filter and alerts exist for project ownership assignments/changes
Control family: Logging and Monitoring
Control description
In order to prevent unnecessary project ownership assignments to users/service-accounts and further misuses of projects and resources, all `roles/Owner` assignments should be monitored.
Members (users/Service-Accounts) with a role assignment to primitive role `roles/Owner` are project owners.
The project owner has all the privileges on the project the role belongs to. These are summarized below:
```
- All viewer permissions on all GCP Services within the project
- Permissions for actions that modify the state of all GCP services within the project
- Manage roles and permissions for a project and all resources within the project
- Set up billing for a project
```
Granting the owner role to a member (user/Service-Account) will allow that member to modify the Identity and Access Management (IAM) policy. Therefore, grant the owner role only if the member has a legitimate purpose to manage the IAM policy. This is because the project IAM policy contains sensitive access control data. Having a minimal set of users allowed to manage IAM policy will simplify any auditing that may be necessary.
How to implement
ResponsibilityCustomerYou configure and operate this in your own cloud accounts.
Owner is the most powerful role on a project. Granting it to another person, or inviting someone to become an owner, should be rare and always deliberate, so every change to ownership raises an alert.
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
Not applicable. This benchmark covers Google Cloud only.
Not applicable. This benchmark covers Google Cloud only.
On Google Cloud the tasks create a logs-based metric in Cloud Logging that counts Owner role changes, alert on it in Cloud Monitoring, and confirm with Security Command Center.
Task 1Count the changes with a logs-based metric
- Sign in to the Google Cloud console at console.cloud.google.com and pick the project to monitor.
- Open Logging > Log-based Metrics and choose Create metric.
- Under Metric type, select Counter.
- Under Details, enter project-ownership-changes as the Log-based metric name, add a short description and set Units to 1.
- Under Filter selection, replace the text in the Build filter box with this filter, exactly: (protoPayload.serviceName="cloudresourcemanager.googleapis.com") AND (ProjectOwnership OR projectOwnerInvitee) OR (protoPayload.serviceData.policyDelta.bindingDeltas.action="REMOVE" AND protoPayload.serviceData.policyDelta.bindingDeltas.role="roles/owner") OR (protoPayload.serviceData.policyDelta.bindingDeltas.action="ADD" AND protoPayload.serviceData.policyDelta.bindingDeltas.role="roles/owner")
- Choose Create metric.
- Check it: the metric appears under User-defined metrics.
Task 2Alert the security team when it happens
- On Log-based Metrics, under User-defined metrics, find project-ownership-changes, open its More menu and choose Create alert from metric.
- Choose Next, keep the threshold so a single matching entry triggers the alert, and enter a Condition name.
- 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).
- Enter an Alert name such as project-ownership-changes-alert, and choose Create policy.
- Check it: grant and then remove Owner for a test account in the same project, and confirm the notification arrives.
Task 3Keep it checked with the Security Health Analytics finding OWNER_NOT_MONITORED
- 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 OWNER_NOT_MONITORED with state ACTIVE, and select Apply.
- Open each finding, read the resource and the explanation it gives, and create the metric and alert in the project it names.
- Check it: after the next Security Health Analytics scan, no active OWNER_NOT_MONITORED finding remains.
Evidence
- Logging > Log-based Metrics, showing project-ownership-changes with its filter
- Monitoring > Alerting, showing the project-ownership-changes-alert policy and its notification channel
- Security Command Center, with no active OWNER_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.