Dataproc Clusters are not encrypted with Customer-Managed Encryption Keys Affecting Dataproc service in Google


Severity

0.0
medium
0
10
Severity Framework
Snyk CCSS
Rule category
Data/ Encryption at Rest

Is your environment affected by this misconfiguration?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
Frameworks
  • Snyk IDSNYK-CC-00742
  • creditSnyk Research Team

Description

Clusters without customer-managed encryption keys (CMEK) risk exposure of sensitive data due to default encryption management. Enforcing CMEK enhances data security by giving users control over the encryption keys and the underlying hardware security modules that protect the keys.

How to fix?

Set the kms_key_name attribute in google_dataproc_cluster resource to valid CMEK.

Example Configuration


resource "google_dataproc_cluster" "allow" {
  name     = "clustera1"
  region   = "us-central1"

  cluster_config {
    encryption_config {
        kms_key_name = "projects/zelarsoft-snyk/locations/global/keyRings/kerberos-key-ring/cryptoKeys/kerberos-crypto-key"
  }
}
}