GPUCC-READY-01: Workload attests before trusting the GPU (attestation-bound key release)¶
| Property | Value |
|---|---|
| Severity | critical |
| Platform | NVIDIA GPU Confidential Computing |
| Lifecycle stage | attest |
| Trust boundary | attestation |
| Assurance | operator-declared |
| Mode | Passive: reads only the files and values you pass to the scan. |
What a failure enables¶
- Model keys released to a debuggable GPU
- Model keys released on a fabricated or replayed report
What it checks¶
It passes when:
- Attestation is verified before the GPU is trusted, and key release is bound to it.
How to fix¶
- Verify the GPU attestation report (CC-On, pinned measurements, valid cert chain) BEFORE toggling the GPU ready-state ON and before releasing any DEK/weights; gate KBS/KMS key release on a successful attestation so no key is released to an unverified GPU.
- Verify attestation before ready-state ON; bind key release to it.
After the fix, scan again: the check should report PASS.
When it is not assessed¶
SKIP:
- No --gpu-kbs-policy specified; skipping check.
ERROR:
- Could not read/parse key-release policy: …
Scan inputs¶
The untrust scan options this check reads:
| Option | Description |
|---|---|
--gpu-kbs-policy |
Key-release policy JSON: attest-before-ready, decrypt location. |
Permissions¶
None. The check reads only the files or values you pass to the scan.
Generated from untrust 1.3.0 (commit 7ef462d9a0c3).