5.9.2 Enable Customer-Managed Encryption Keys (CMEK) for Boot Disks (Automated)
Profile Applicability
- Level 2
Description
Use Customer-Managed Encryption Keys (CMEK) to encrypt node boot disks using keys managed within Cloud Key Management Service (Cloud KMS).
Rationale
GCE persistent disks are encrypted at rest by default using envelope encryption with keys managed by Google. For additional protection, users can manage the Key Encryption Keys using Cloud KMS.
Impact
Encryption of dynamically-provisioned attached disks requires the use of the self-provisioned Compute Engine Persistent Disk CSI Driver v0.5.1 or higher.
If CMEK is being configured with a regional cluster, the cluster must run GKE 1.14 or higher.
Audit
Using Google Cloud Console:
- Go to Kubernetes Engine by visiting: https://console.cloud.google.com/kubernetes/list
- Click on each cluster, and click on any Node pools.
- On the Node pool Details page, under the
Securityheading, check thatBoot disk encryption typeis set toCustomer managedwith the desired key.
Using Command Line:
Run this command:
gcloud container node-pools describe $NODE_POOL --cluster $CLUSTER_NAME --zone $COMPUTE_ZONE
Verify that the output of the above command includes a diskType of either pd-standard, pd-balanced or pd-ssd, and the bootDiskKmsKey is specified as the desired key.
Remediation
This cannot be remediated by updating an existing cluster. The node pool must either be recreated or a new cluster created.
Using Google Cloud Console:
To create a new node pool:
- Go to Kubernetes Engine by visiting: https://console.cloud.google.com/kubernetes/list
- Select Kubernetes clusters for which node boot disk CMEK is disabled.
- Click
ADD NODE POOL. - In the Nodes section, under machine configuration, ensure Boot disk type is
Standard persistent diskorSSD persistent disk. - Select
Enable customer-managed encryption for Boot Diskand select the Cloud KMS encryption key to be used. - Click
CREATE.
To create a new cluster:
- Go to Kubernetes Engine by visiting: https://console.cloud.google.com/kubernetes/list
- Click
CREATEand click `CONFIGURE for the required cluster mode. - Under
NODE POOLS, expand the default-pool list and clickNodes. - In the Configure node settings pane, select
Standard persistent diskorSSD Persistent Diskas the Boot disk type. - Select
Enable customer-managed encryption for Boot Diskcheck box and choose the Cloud KMS encryption key to be used. - Configure the rest of the cluster settings as required.
- Click
CREATE.
Using Command Line:
Create a new node pool using customer-managed encryption keys for the node boot disk, of <disk_type> either pd-standard or pd-ssd:
gcloud container node-pools create <cluster_name> --disk-type <disk_type> --boot-disk-kms-key projects/<key_project_id>/locations/<location>/keyRings/<ring_name>/cryptoKeys/<key_name>
Create a cluster using customer-managed encryption keys for the node boot disk, of <disk_type> either pd-standard or pd-ssd:
gcloud container clusters create <cluster_name> --disk-type <disk_type> --boot-disk-kms-key projects/<key_project_id>/locations/<location>/keyRings/<ring_name>/cryptoKeys/<key_name>
Default Value
Persistent disks are encrypted at rest by default, but are not encrypted using Customer-Managed Encryption Keys by default. By default, the Compute Engine Persistent Disk CSI Driver is not provisioned within the cluster.
References
- https://cloud.google.com/kubernetes-engine/docs/how-to/using-cmek
- https://cloud.google.com/compute/docs/disks/customer-managed-encryption
- https://cloud.google.com/security/encryption-at-rest/default-encryption/
- https://cloud.google.com/kubernetes-engine/docs/concepts/persistent-volumes
- https://cloud.google.com/sdk/gcloud/reference/container/node-pools/create
CIS Controls
| Controls Version | Control | IG 1 | IG 2 | IG 3 |
|---|---|---|---|---|
| v8 | 3.11 Encrypt Sensitive Data at Rest | x | x | |
| v7 | 14.8 Encrypt Sensitive Information at Rest | x |