GPUCC-MODE-01: GPU is in CC-On mode, not CC-DevTools or CC-Off¶
| Property | Value |
|---|---|
| Severity | high |
| Platform | NVIDIA GPU Confidential Computing |
| Lifecycle stage | runtime |
| 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
What it checks¶
It passes when:
- GPU reports CC-On (production Confidential Computing mode).
How to fix¶
- Set the GPU to CC-On (not CC-DevTools) before running production workloads on a CC-capable driver, and confirm
nvidia-smi conf-compute -freports ON. Never run confidential workloads in DevTools mode. - Run the GPU in CC-On, never DevTools, for production workloads.
After the fix, scan again: the check should report PASS.
When it is not assessed¶
SKIP:
- No --gpu-cc-mode specified; skipping check.
- CC mode is asserted from the signed attestation report (GPUCC-ATT-01); skipping the unauthenticated live-mode re-check to avoid double-counting.
Scan inputs¶
The untrust scan options this check reads:
| Option | Description |
|---|---|
--gpu-attestation-report |
Path to a captured NVIDIA GPU attestation report (JSON). |
--gpu-cc-mode |
CC mode (nvidia-smi conf-compute -f): on|devtools|off. |
Permissions¶
None. The check reads only the files or values you pass to the scan.
Related¶
- Runtime detection
DET-G1(NVIDIA GPU CC): GPU left production CC mode
Generated from untrust 1.3.0 (commit 7ef462d9a0c3).