---
title: Compute instances should have confidential computing enabled
description: Datadog, the leading service for cloud-scale monitoring.
breadcrumbs: >-
  Docs > Datadog Security > OOTB Rules > Compute instances should have
  confidential computing enabled
---

> For the complete documentation index, see [llms.txt](https://docs.datadoghq.com/llms.txt).

# Compute instances should have confidential computing enabled
 
## Description{% #description %}

Confidential VM encrypts instance memory with a per-instance key held in dedicated hardware (AMD SEV, AMD SEV-SNP, or Intel TDX), so data stays encrypted while it is processed.

This rule evaluates instances whose machine type and zone support Confidential VM according to Google's supported configurations:

- The N2D and C2D series
- The C3D and C4D series, up to 255 vCPUs (the [general-purpose machine family](https://docs.cloud.google.com/compute/docs/general-purpose-machines) page excludes larger AMD SEV configurations)
- `c3-standard-*`, in the zones listed for Intel TDX, and `c3-standard-*-lssd`, in the zones listed for Intel TDX with Local SSD
- `c4-standard-*`, up to 192 vCPUs without Local SSD, in the zones listed for Intel TDX
- `a3-highgpu-1g`, in the zones listed for NVIDIA Confidential Computing
- `g4-standard-48`

Bare metal, all other machine types, and supported machine types in zones that are not listed are skipped. An instance with an absent or empty machine type, or with a zone-restricted machine type whose zone is not in the machine type URL, fails because eligibility cannot be established. An instance passes when `enableConfidentialCompute` is true or `confidentialInstanceType` is `SEV`, `SEV_SNP`, or `TDX`, because Google reports SEV-SNP and TDX instances only through `confidentialInstanceType`. The CIS audit text names only N2D. The other machine types come from the supported configurations page that the benchmark references.

## Remediation{% #remediation %}

Confidential VM can only be enabled when an instance is created.

1. Create a replacement instance on a supported machine type with `--confidential-compute-type` set to the technology that machine type supports, following [Create a Confidential VM instance](https://docs.cloud.google.com/confidential-computing/confidential-vm/docs/create-a-confidential-vm-instance).
1. Move the workload to the new instance and delete the original instance.

## References{% #references %}

- [Confidential VM overview](https://docs.cloud.google.com/confidential-computing/confidential-vm/docs/confidential-vm-overview)
- [Supported configurations](https://docs.cloud.google.com/confidential-computing/confidential-vm/docs/supported-configurations)
- [Verify that Confidential Computing is enabled](https://docs.cloud.google.com/confidential-computing/confidential-vm/docs/verify-confidential-computing-enabled)
- [General-purpose machine family](https://docs.cloud.google.com/compute/docs/general-purpose-machines)
- [CIS Google Cloud Platform Foundation Benchmark](https://www.cisecurity.org/benchmark/google_cloud_computing_platform)
