CIS Google Cloud Platform Foundation Benchmark v1.2.0/BigQuery/82 of 83
7.2Ensure that all BigQuery Tables are encrypted with Customer-managed encryption key (CMEK)
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. If CMEK is used, the CMEK is used to encrypt the data encryption keys instead of using google-managed encryption keys.
How to implement
ResponsibilityCustomerYou configure and operate this in your own cloud accounts.
BigQuery encrypts all data with keys Google manages. With a customer-managed key from Cloud KMS, you decide who can use the key, can see every use of it, and can cut off access to the table by disabling it. An existing table can't be switched in place, so it is copied into a new table that uses the key.
Before you start
The same on every cloud, before the steps in the tabs.
- Decide which datasets need customer-managed keys, and who may administer and use the keys (1.11).
Evidence
- The list of datasets that need customer-managed keys, and the key owners
Not applicable. This benchmark covers Google Cloud only.
Not applicable. This benchmark covers Google Cloud only.
On Google Cloud the tasks prepare a key in Cloud KMS, copy each table to a version protected by it in BigQuery, and watch with Security Command Center.
Task 1Prepare a key BigQuery can use
- Sign in to the Google Cloud console at console.cloud.google.com and open Security > Key Management.
- Create a key ring in the same location as the dataset, and a symmetric key in it with a rotation period (1.10).
- On the key's Permissions, grant the BigQuery service account of the project (bq-PROJECT_NUMBER@bigquery-encryption.iam.gserviceaccount.com) the Cloud KMS CryptoKey Encrypter/Decrypter role.
- Check it: the key's permissions list the BigQuery service account.
Task 2Copy the table into a table protected by the key
- In BigQuery, open the table and choose Copy.
- Choose a new table name as the destination and, under the advanced or encryption options, choose Customer-managed key and select the key.
- Choose Copy and wait for the job to finish.
- Check the new table's Details tab shows the key under Customer-managed key, then repoint queries and jobs to it.
- Delete the original table, and rename or recreate views as needed.
Task 3Keep it checked with the Security Health Analytics finding BIGQUERY_TABLE_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 BIGQUERY_TABLE_CMEK_DISABLED with state ACTIVE, and select Apply.
- Open each finding, read the resource and the explanation it gives, and copy the table it names into a CMEK table (the detector needs extra configuration before it reports).
- Check it: after the next Security Health Analytics scan, no active BIGQUERY_TABLE_CMEK_DISABLED finding remains.
Evidence
- The Details tab of each table, showing its customer-managed key
- The key's permissions, listing the BigQuery service account
- Security Command Center, with no active BIGQUERY_TABLE_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.