compliance.tf
Google Cloud Compliance ControlsGoogle Cloud Compute Engine

Disks for critical VMs should use Customer-Supplied Encryption Keys (CSEK) for encryption

Customer-Supplied Encryption Keys (CSEK) are a feature in 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.

What this control checks

Checks disk encryption settings for critical VMs

Framework mappings

The clauses this control is mapped to in each framework.

SOC 2

  • C1.1 The entity identifies and maintains confidential information to meet the entity's objectives related to confidentiality

PCI DSS v4.0

  • 3.5.1: Primary account number (PAN) is secured wherever it is stored.
  • 8.3.2: Strong cryptography is used to render all authentication factors unreadable during transmission and storage on all system components
  • 10.3.2: Audit logs are protected from destruction and unauthorized modifications.
  • 10.3.4: File integrity monitoring or change-detection mechanisms is used on audit logs to ensure that existing log data cannot be changed without generating alerts

ISO/IEC 27001:2022

  • A.8.12 Data leakage prevention

NIS2 Directive (EU 2022/2555)

  • 9 Cryptography
  • 12 Asset management

NIST SP 800-53 Rev 5

  • IA-5: Authenticator Management
  • SC-28 Protection Of Information At Rest

NIST Cybersecurity Framework v2.0

  • ID.AM-01: Inventories of hardware managed by the organization are maintained.
  • PR.DS-01

CIS GCP Benchmark v3.0.0

  • 4.7 Ensure VM Disks for Critical VMs Are Encrypted With Customer-Supplied Encryption Keys

CIS GCP Benchmark v4.0.0

  • 4.7 Ensure VM Disks for Critical VMs Are Encrypted With Customer-Supplied Encryption Keys (CSEK)

BSI C5:2025

  • CRY-01.02AC The cloud provider's PQC strategy is aligned with cryptography policies and procedures and includes the following aspects: - Maintenance of an inventory of cryptographic mechanisms in use, including priority levels to each inventory item based on the impact and probabilities of the...
  • CRY-03.01B The cloud service provider ensures that encryption, authentication and key management practices are regularly audited in accordance with COM-02 to identify and address potential vulnerabilities. At a minimum, reviews are performed annually and immediately following security incidents...
  • IAM-08.06B If cryptographic mechanisms are used, they follow the policies and procedures from CRY-01.
  • OIS-08.02B The following aspects are taken into account when identifying risks, insofar as they are applicable to the cloud service provided and are within the area of responsibility of the cloud service provider: - Processing, storage or transmission of cloud service customer data and cloud...
  • OPS-31.02B Remote attestation functionalities are based on cryptographic means rooted in trusted hard- and software.

CIS GCP Benchmark v1.2.0

  • 4.7 Ensure VM disks for critical VMs are encrypted with Customer-Supplied Encryption Keys (CSEK)

CIS GCP Benchmark v1.3.0

  • 4.7 Ensure VM disks for critical VMs are encrypted with Customer-Supplied Encryption Keys (CSEK)

CIS GCP Benchmark v2.0.0

  • 4.7 Ensure VM disks for critical VMs are encrypted with Customer-Supplied Encryption Keys (CSEK)

HIPAA Security Rule 2003

  • 164.308(a)(1)(ii)(B) Risk management
  • 164.310(d)(1) Device and media controls
  • 164.312(a)(2)(iv) Encryption and decryption
  • 164.312(e)(2)(ii) Encryption

NIST Cybersecurity Framework v1.0

  • PR.DS-1: Data-at-rest is protected.

Tool mappings

Use these identifiers to cross-reference this control across tools, reports, and evidence.

  • Compliance.tf Control: compute_disk_encrypted_with_csk
  • Powerpipe Control: gcp_compliance.control.compute_disk_encrypted_with_csk
  • Prowler Check: compute_instance_encryption_with_csek_enabled

Last reviewed: 2026-10-09

View all Google Cloud controls →

On this page

Ask AI about this

Help improve this page