CIS Google Cloud Platform Foundation Benchmark v1.2.0/Storage/49 of 83
5.1Ensure that Cloud Storage bucket is not anonymously or publicly accessible
Control family: Storage
Control description
It is recommended that IAM policy on Cloud Storage bucket does not allows anonymous or public access.
How to implement
ResponsibilityCustomerYou configure and operate this in your own cloud accounts.
A bucket granted to allUsers can be read by anyone on the internet, and one granted to allAuthenticatedUsers by anyone with any Google account. Data leaks from cloud storage usually start with a grant like this. Buckets are shared only with named identities, and public access prevention stops new public grants.
Before you start
The same on every cloud, before the steps in the tabs.
- If a bucket must serve public content, such as website assets, record it as an exception and keep it in a separate project.
Evidence
- The register of buckets approved to serve public content
Not applicable. This benchmark covers Google Cloud only.
Not applicable. This benchmark covers Google Cloud only.
On Google Cloud the tasks remove public principals from buckets in Cloud Storage, enforce public access prevention with an organization policy, and watch with Security Command Center.
Task 1Remove public principals from a bucket
- Sign in to the Google Cloud console at console.cloud.google.com and open Cloud Storage > Buckets.
- Choose the bucket and open the Permissions tab.
- Next to View by, choose Roles.
- In the Filter box, search for allUsers and allAuthenticatedUsers.
- Choose Delete to remove every role granted to them.
- Check it: the bucket list no longer shows the bucket as public to the internet.
Task 2Prevent it with the organization policy storage.publicAccessPrevention
- Open IAM & Admin > Organization policies with the organization (or the folder that holds your projects) selected in the project picker.
- Search for storage.publicAccessPrevention (Enforce Public Access Prevention) and open it.
- Choose Manage policy, select Override parent's policy, choose Add a rule and set Enforcement to On.
- Choose Set policy.
- Check it: granting allUsers a role on a bucket is refused.
Task 3Keep it checked with the Security Health Analytics finding PUBLIC_BUCKET_ACL
- 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 PUBLIC_BUCKET_ACL with state ACTIVE, and select Apply.
- Open each finding, read the resource and the explanation it gives, and remove the public grant from the bucket it names.
- Check it: after the next Security Health Analytics scan, no active PUBLIC_BUCKET_ACL finding remains.
Evidence
- The Permissions tab of each bucket, with no allUsers or allAuthenticatedUsers
- The storage.publicAccessPrevention policy, enforced
- Security Command Center, with no active PUBLIC_BUCKET_ACL 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.