Skip to main content

💼 4.11 Ensure That Compute Instances Have Confidential Computing Enabled - Level 2 (Automated)

  • ID: /frameworks/cis-gcp-v2.0.0/04/11

Description

Google Cloud encrypts data at-rest and in-transit, but customer data must be decrypted for processing. Confidential Computing is a breakthrough technology which encrypts data in-use—while it is being processed. Confidential Computing environments keep data encrypted in memory and elsewhere outside the central processing unit (CPU).

Confidential VMs leverage the Secure Encrypted Virtualization (SEV) feature of AMD EPYC™ CPUs. Customer data will stay encrypted while it is used, indexed, queried, or trained on. Encryption keys are generated in hardware, per VM, and not exportable. Thanks to built-in hardware optimizations of both performance and security, there is no significant performance penalty to Confidential Computing workloads.

Similar

  • Sections
    • /frameworks/cis-gcp-v3.0.0/04/11
    • /frameworks/cis-gcp-v1.3.0/04/11
  • Internal
    • ID: dec-c-d850549e

Similar Sections (Take Policies From)

SectionSub SectionsInternal RulesPoliciesFlagsCompliance
💼 CIS GCP v1.3.0 → 💼 4.11 Ensure That Compute Instances Have Confidential Computing Enabled - Level 2 (Automated)1no data
💼 CIS GCP v3.0.0 → 💼 4.11 Ensure That Compute Instances Have Confidential Computing Enabled - Level 2 (Automated)1no data

Similar Sections (Give Policies To)

SectionSub SectionsInternal RulesPoliciesFlagsCompliance
💼 CIS GCP v1.3.0 → 💼 4.11 Ensure That Compute Instances Have Confidential Computing Enabled - Level 2 (Automated)1no data
💼 CIS GCP v3.0.0 → 💼 4.11 Ensure That Compute Instances Have Confidential Computing Enabled - Level 2 (Automated)1no data

Sub Sections

SectionSub SectionsInternal RulesPoliciesFlagsCompliance

Policies (1)

PolicyLogic CountFlagsCompliance
🛡️ Google GCE Instance Confidential Compute is not enabled🟢1🟢 x6no data