GPUCC-CVM-01: GPU is attached to a verified Confidential VM (real TDX/SEV-SNP quote)¶
| Property | Value |
|---|---|
| Severity | high |
| Platform | NVIDIA GPU Confidential Computing |
| Lifecycle stage | attest |
| Trust boundary | cvm |
| Assurance | report-derived |
| Mode | Passive: reads only the files and values you pass to the scan. |
What a failure enables¶
- Workload trusted on a CPU context nobody verified
What it checks¶
It passes when:
- GPU is attached to a CVM with a verified, vendor-chained quote.
How to fix¶
- Run the GPU inside a genuine confidential VM (Intel TDX / AMD SEV-SNP) and VERIFY its vendor-signed quote (Intel-chained TDX quote / SEV-SNP report) — not a self-asserted flag — keep the CVM out of debug mode, and enable Secure Boot. The GPU boundary is only as strong as the CPU VM it is attached to.
- Run the GPU inside a verified, non-debug TDX/SEV-SNP CVM with a real vendor-signed quote.
After the fix, scan again: the check should report PASS.
When it is not assessed¶
SKIP:
- No --gpu-attestation-report specified; skipping check.
ERROR:
- Could not read/parse attestation report: …
Scan inputs¶
The untrust scan options this check reads:
| Option | Description |
|---|---|
--gpu-attestation-report |
Path to a captured NVIDIA GPU attestation report (JSON). |
Permissions¶
None. The check reads only the files or values you pass to the scan.
Generated from untrust 1.3.0 (commit 7ef462d9a0c3).