CSPACE-VM-01: Confidential VM runs SEV-SNP with Shielded boot¶
| Property | Value |
|---|---|
| Severity | high |
| Platform | GCP Confidential Space (AMD SEV-SNP) |
| Lifecycle stage | deploy |
| Mode | Passive: read-only cloud API calls. |
What it checks¶
It passes when:
- Instance is a SEV-SNP Confidential VM with Shielded boot enabled.
How to fix¶
- Recreate the instance with confidentialInstanceType=SEV_SNP, enableConfidentialCompute=true, and Shielded VM (Secure Boot, vTPM, integrity monitoring) enabled.
After the fix, scan again: the check should report PASS.
When it is not assessed¶
SKIP:
- Need --gcp-instance, --gcp-zone, and --gcp-project; skipping check.
ERROR:
- Could not read instance config: …
Scan inputs¶
The untrust scan options this check reads:
| Option | Description |
|---|---|
--gcp-instance |
Confidential VM instance name. |
--gcp-project |
GCP project ID. |
--gcp-zone |
Zone of the Confidential VM. |
Permissions¶
The cloud API calls this check makes, read from the scanner's source:
| Cloud | API call | Permission | Access |
|---|---|---|---|
| Google Cloud | compute.instances.get |
compute.instances.get |
read |
See Required permissions for every check on this platform.
Related¶
- Runtime detection
DET-C11(GCP Confidential Space): Shielded VM protection weakened on the workload VM - Runtime detection
DET-C13(GCP Confidential Space): Public IP added to the workload Confidential VM - Runtime detection
DET-C15(GCP Confidential Space): Confidential VM disk snapshotted or imaged - Runtime detection
DET-C2(GCP Confidential Space): Confidential VM launched from the debug image or with log redirect
Generated from untrust 1.3.0 (commit 7ef462d9a0c3).