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

• Contextual name: 💼 4.11 Ensure That Compute Instances Have Confidential Computing Enabled - Level 2 (Automated)
• ID: /frameworks/cis-gcp-v1.3.0/04/11
• Located in: 💼 4 Virtual Machines

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-v2.0.0/04/11
  • /frameworks/cis-gcp-v1.2.0/04/11
• Internal
  • ID: dec-c-e9b96f8d

Similar Sections (Take Policies From)

Section	Sub Sections	Internal Rules	Policies	Flags
💼 CIS GCP v1.2.0 → 💼 4.11 Ensure that Compute instances have Confidential Computing enabled - Level 2 (Automated)			1
💼 CIS GCP v2.0.0 → 💼 4.11 Ensure That Compute Instances Have Confidential Computing Enabled - Level 2 (Automated)			1

Similar Sections (Give Policies To)

Section	Sub Sections	Internal Rules	Policies	Flags
💼 CIS GCP v1.2.0 → 💼 4.11 Ensure that Compute instances have Confidential Computing enabled - Level 2 (Automated)			1
💼 CIS GCP v2.0.0 → 💼 4.11 Ensure That Compute Instances Have Confidential Computing Enabled - Level 2 (Automated)			1

Sub Sections

Section	Sub Sections	Internal Rules	Policies	Flags

Policies (1)

Policy	Logic Count	Flags
📝 Google GCE Instance Confidential Compute is not enabled 🟢	1	🟢 x6