CIS Google Cloud Platform Foundation Benchmark v1.2.0/BigQuery/81 of 83
7.1Ensure that BigQuery datasets are not anonymously or publicly accessible
Control family: BigQuery
Control description
It is recommended that the IAM policy on BigQuery datasets does not allow anonymous and/or public access.
How to implement
ResponsibilityCustomerYou configure and operate this in your own cloud accounts.
A BigQuery dataset shared with allUsers or allAuthenticatedUsers can be queried by anyone on the internet or anyone with a Google account. Datasets are shared only with named people, groups and service accounts.
Before you start
The same on every cloud, before the steps in the tabs.
- Agree that datasets are shared only with named people, groups and service accounts, and who approves sharing.
- Record any dataset that is meant to be public, with its approver.
Evidence
- The data sharing standard and the list of approved public datasets
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 datasets in BigQuery, block them with an organization policy, and watch with Security Command Center.
Task 1Remove public access from a dataset
- Sign in to the Google Cloud console at console.cloud.google.com and open BigQuery.
- In the Explorer panel, choose the dataset to open its Dataset info.
- Choose Sharing > Permissions.
- In Dataset Permissions, find allUsers and allAuthenticatedUsers, and remove their access.
- Check it: the dataset's permissions list only named principals.
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: sharing a dataset with allUsers is refused.
Task 3Keep it checked with the Security Health Analytics finding PUBLIC_DATASET
- 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_DATASET with state ACTIVE, and select Apply.
- Open each finding, read the resource and the explanation it gives, and remove the public principal from the dataset it names.
- Check it: after the next Security Health Analytics scan, no active PUBLIC_DATASET finding remains.
Evidence
- The Permissions of each dataset, with no public principals
- Security Command Center, with no active PUBLIC_DATASET 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.