CIS Google Cloud Platform Foundation Benchmark v1.2.0/Identity and Access Management/9 of 83
1.9Ensure that Cloud KMS cryptokeys are not anonymously or publicly accessible
Control family: Identity and Access Management
Control description
It is recommended that the IAM policy on Cloud KMS `cryptokeys` should restrict anonymous and/or public access.
How to implement
ResponsibilityCustomerYou configure and operate this in your own cloud accounts.
Granting a Cloud KMS key or key ring to allUsers or allAuthenticatedUsers lets anyone on the internet, or anyone with any Google account, use or see the key. Keys are granted only to named identities that need them.
Before you start
The same on every cloud, before the steps in the tabs.
- Agree that keys and key rings are shared only with named identities that need them, and who approves such grants.
- Review key permissions on a schedule.
Evidence
- The key access standard and the review record
Not applicable. This benchmark covers Google Cloud only.
Not applicable. This benchmark covers Google Cloud only.
On Google Cloud the tasks remove the public grants from keys and key rings in Key Management, block public principals with an organization policy, and watch with Security Command Center.
Task 1Remove public access from the key or key ring
- Sign in to the Google Cloud console at console.cloud.google.com and open Security > Key Management.
- Open the key ring, and select the checkbox next to the key (or select the key ring itself in the list).
- If the info panel is hidden, choose SHOW INFO PANEL.
- In the Role / Principal filter, search for allUsers and allAuthenticatedUsers.
- Choose Delete next to each match.
- Check it: the info panel lists no allUsers or allAuthenticatedUsers on the key or key ring.
Task 2Prevent it with the organization policy iam.allowedPolicyMemberDomains
- Open IAM & Admin > Organization policies with the organization (or the folder that holds your projects) selected in the project picker.
- Search for iam.allowedPolicyMemberDomains (Domain restricted sharing) and open it.
- Choose Manage policy, select Override parent's policy, choose Add a rule and under Policy values choose Custom, set Policy type to Allow and add your Cloud Identity or Workspace customer ID.
- Choose Set policy.
- Check it: adding allUsers to a key is refused.
Task 3Keep it checked with the Security Health Analytics finding KMS_PUBLIC_KEY
- 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 KMS_PUBLIC_KEY with state ACTIVE, and select Apply.
- Open each finding, read the resource and the explanation it gives, and remove the public grant it names.
- Check it: after the next Security Health Analytics scan, no active KMS_PUBLIC_KEY finding remains.
Evidence
- The permissions of each key and key ring, with no public principals
- Security Command Center, with no active KMS_PUBLIC_KEY 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.