GPUCC-ATT-01: GPU attestation report asserts a trusted state¶
| Property | Value |
|---|---|
| Severity | critical |
| Platform | NVIDIA GPU Confidential Computing |
| Lifecycle stage | attest |
| Policy | P-04: Attestation evidence is fresh and fully verified |
| Trust boundary | attestation |
| Assurance | report-derived |
| Mode | Passive: reads only the files and values you pass to the scan. |
What a failure enables¶
- Model keys released to a debuggable GPU
What it checks¶
It passes when:
- Attestation report asserts CC-On, a signed report, and a known GPU.
How to fix¶
- Collect the report from a CC-On (non-DevTools) production GPU with the NVIDIA Attestation SDK, confirm the GPU model and signed report, and reject any report whose cc_mode != on or that carries a debug flag in your key-release path.
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.
Related¶
- Other checks for policy P-04: CCA-CERT-01, CSPACE-ATT-01, CSPACE-ATT-02, CSPACE-ATT-03, GPU-CERT-01, NITRO-ATT-02, NITRO-ATT-03, SE-CERT-01, SGX-CERT-01, SNP-CERT-01, TDX-CERT-01
Generated from untrust 1.3.0 (commit 7ef462d9a0c3).