CIS Google Cloud Platform Foundation Benchmark v1.2.0/Virtual Machines/44 of 83
4.7Ensure VM disks for critical VMs are encrypted with Customer-Supplied Encryption Keys (CSEK)
Control family: Virtual Machines
Control description
Customer-Supplied Encryption Keys (CSEK) are a feature in Google Cloud Storage and Google Compute Engine. If you supply your own encryption keys, Google uses your key to protect the Google-generated keys used to encrypt and decrypt your data. By default, Google Compute Engine encrypts all data at rest. Compute Engine handles and manages this encryption for you without any additional actions on your part. However, if you wanted to control and manage this encryption yourself, you can provide your own encryption keys.
How to implement
ResponsibilityCustomerYou configure and operate this in your own cloud accounts.
Compute Engine always encrypts disks. Customer-supplied encryption keys add a layer you control: Google uses your key to protect the disk's keys and doesn't store it, so without the key the disk can't be read or started. You also carry the risk: lose the key and the data is gone. The benchmark asks for this on critical VMs only.
Before you start
The same on every cloud, before the steps in the tabs.
- Decide which VMs are critical enough to need customer-supplied keys.
- Set up how the keys are generated, stored, backed up and supplied when a VM restarts, since Google can't recover them.
Evidence
- The list of critical VMs and the key management procedure
Not applicable. This benchmark covers Google Cloud only.
Not applicable. This benchmark covers Google Cloud only.
On Google Cloud the tasks create new disks protected with your own key in Compute Engine, since existing disks can't be switched, then mark them so Security Command Center checks them.
Task 1Create a disk with a customer-supplied key
- Sign in to the Google Cloud console at console.cloud.google.com and open Compute Engine > Snapshots, and take a snapshot of the critical VM's disk.
- Open Disks and choose Create disk.
- Choose the snapshot as the Source type.
- Under Encryption, choose Customer-supplied encryption key and enter your key (a 256-bit key, base64 encoded, kept in your key store).
- Choose Create, then stop the VM, detach the old disk and attach the new one in VM instances > Edit.
- Delete the old disk and the snapshot once the VM runs from the new disk.
- Check it: the new disk's details show customer-supplied encryption.
Task 2Mark the disks so Security Command Center checks them
- Open Security Command Center > Assets.
- In Quick filters, under Resource type, select compute.Disk (use View more to find it).
- Select the critical VMs' disks and choose Set Security Marks, then Add Mark.
- Enter the key enforce_customer_supplied_disk_encryption_keys with the value true, and choose Save.
- Check it: on Findings, no active DISK_CSEK_DISABLED finding remains for the marked disks.
Evidence
- The disk details of each critical VM, showing customer-supplied encryption
- The security marks on those disks, and no active DISK_CSEK_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.