Detections
Analytics
8.1 Ensure that Dataproc Cluster is encrypted using Customer-Managed Encryption Key
Information
When you use Dataproc, cluster and job data is stored on Persistent Disks (PDs) associated with the Compute Engine VMs in your cluster and in a Cloud Storage staging bucket. This PD and bucket data is encrypted using a Google-generated data encryption key (DEK) and key encryption key (KEK). The CMEK feature allows you to create, use, and revoke the key encryption key (KEK). Google still controls the data encryption key (DEK).Rationale:
'Cloud services offer the ability to protect data related to those services using encryption keys managed by the customer within Cloud KMS. These encryption keys are called customer-managed encryption keys (CMEK). When you protect data in Google Cloud services with CMEK, the CMEK key is within your control.
Impact:
Using Customer Managed Keys involves additional overhead in maintenance by administrators.
Solution
From Google Cloud ConsoleLogin to the GCP Console and navigate to the Dataproc Cluster page by visiting https://console.cloud.google.com/dataproc/clusters.
Select the project from the projects dropdown list.
On the Dataproc Cluster page, click on the Create Cluster to create a new cluster with Customer managed encryption keys.
On Create a cluster page, perform below steps:
Inside Set up cluster section perform below steps:
-In the Name textbox, provide a name for your cluster.
From Location select the location in which you want to deploy a cluster.
Configure other configurations as per your requirements.
Inside Configure Nodes and Customize cluster section configure the settings as per your requirements.
Inside Manage security section, perform below steps:
From Encryption, select Customer-managed key.
Select a customer-managed key from dropdown list.
Ensure that the selected KMS Key have Cloud KMS CryptoKey Encrypter/Decrypter role assign to Dataproc Cluster service account ('serviceAccount:service-<project_number>@compute-system.iam.gserviceaccount.com').
Click on Create to create a cluster.
Once the cluster is created migrate all your workloads from the older cluster to the new cluster and delete the old cluster by performing the below steps:
On the Clusters page, select the old cluster and click on Delete cluster.
On the Confirm deletion window, click on Confirm to delete the cluster.
Repeat step above for other Dataproc clusters available in the selected project.
Change the project from the project dropdown list and repeat the remediation procedure for other Dataproc clusters available in other projects.
From Google Cloud CLI
Before creating cluster ensure that the selected KMS Key have Cloud KMS CryptoKey Encrypter/Decrypter role assign to Dataproc Cluster service account ('serviceAccount:service-<project_number>@compute-system.iam.gserviceaccount.com').
Run clusters create command to create new cluster with customer-managed key:
gcloud dataproc clusters create <cluster_name> --region=us-central1 --gce-pd-kms-key=<key_resource_name>
The above command will create a new cluster in the selected region.
Once the cluster is created migrate all your workloads from the older cluster to the new cluster and Run clusters delete command to delete cluster:
gcloud dataproc clusters delete <cluster_name> --region=us-central1
Repeat step no. 1 to create a new Dataproc cluster.
Change the project by running the below command and repeat the remediation procedure for other projects:
gcloud config set project <project_ID>'
See Also
Item Details
Audit Name: CIS Google Cloud Platform v3.0.0 L2
Category: IDENTIFICATION AND AUTHENTICATION, SYSTEM AND COMMUNICATIONS PROTECTION
References: 800-53|IA-5(1), 800-53|SC-28, 800-53|SC-28(1), CSCv7|14.8
Plugin: GCP
Control ID: 2147fcfbc3b7477b45c3d1176c1f0ff5b0142d90e34ef039be7981ab53396666