GPUCC-CUDA-01: A CUDA kernel executes only after successful GPU attestation¶
| Property | Value |
|---|---|
| Severity | high |
| Platform | NVIDIA GPU Confidential Computing |
| Lifecycle stage | runtime |
| Trust boundary | attestation |
| Assurance | report-derived |
| Mode | Passive: reads only the files and values you pass to the scan. |
What it checks¶
It passes when:
- A CUDA challenge ran on the attested GPU after a successful nvattest result, with the retained evidence chain intact.
How to fix¶
- Fail closed on nvattest, retain its raw result and receipt, then launch CUDA only after verification succeeds. Bind the CUDA receipt to the exact attestation receipt and require the GPU UUID to match.
- Retain and link nvattest and CUDA receipts; execute only after PASS.
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/validate CUDA runtime evidence: …
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¶
- Runtime detection
DET-G5(NVIDIA GPU CC): CUDA ran without a valid attestation
Generated from untrust 1.3.0 (commit 7ef462d9a0c3).