CIS Google Cloud Platform Foundation Benchmark v1.2.0/BigQuery/83 of 83
7.3Ensure that a Default Customer-managed encryption key (CMEK) is specified for all BigQuery Data Sets
Control family: BigQuery
Control description
BigQuery by default encrypts the data as rest by employing `Envelope Encryption` using Google managed cryptographic keys. The data is encrypted using the `data encryption keys` and data encryption keys themselves are further encrypted using `key encryption keys`. This is seamless and do not require any additional input from the user. However, if you want to have greater control, Customer-managed encryption keys (CMEK) can be used as encryption key management solution for BigQuery Data Sets.
How to implement
ResponsibilityCustomerYou configure and operate this in your own cloud accounts.
A default customer-managed key on a dataset makes every new table in it use that key, so nobody has to remember to choose it. It doesn't re-encrypt existing tables; those are copied as in 7.2.
Before you start
The same on every cloud, before the steps in the tabs.
- Decide which datasets need a default customer-managed key, and which key each one uses.
- Agree who may administer and use those keys (1.11).
Evidence
- The list of datasets with their default key and key owners
Not applicable. This benchmark covers Google Cloud only.
Not applicable. This benchmark covers Google Cloud only.
On Google Cloud the tasks set the default key on each dataset in BigQuery, then watch with Security Command Center.
Task 1Set a default customer-managed key on a dataset
- Sign in to the Google Cloud console at console.cloud.google.com and open BigQuery.
- In the Explorer panel, choose the dataset and then Edit details.
- Under the encryption or advanced options, choose Customer-managed key and select the key prepared in 7.2.
- Choose Save.
- Check it: a newly created test table shows the key on its Details tab.
Task 2Keep it checked with the Security Health Analytics finding DATASET_CMEK_DISABLED
- 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 DATASET_CMEK_DISABLED with state ACTIVE, and select Apply.
- Open each finding, read the resource and the explanation it gives, and set a default key on the dataset it names, and copy its older tables as in 7.2.
- Check it: after the next Security Health Analytics scan, no active DATASET_CMEK_DISABLED finding remains.
Evidence
- The Dataset info of each dataset, showing its default customer-managed key
- Security Command Center, with no active DATASET_CMEK_DISABLED 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.