GPUCC-TELEMETRY-01: Host-side GPU telemetry does not leak the confidential workload¶
| Property | Value |
|---|---|
| Severity | medium |
| Platform | NVIDIA GPU Confidential Computing |
| Lifecycle stage | runtime |
| Trust boundary | vmm |
| Assurance | operator-declared |
| Mode | Passive: reads only the files and values you pass to the scan. |
What it checks¶
It passes when:
- Host-side GPU telemetry export is disabled and profiling counters are restricted for the confidential context.
How to fix¶
- Disable host-side GPU telemetry collection for the confidential GPU (stop DCGM exporter / nvidia-smi dmon / NVML metric scraping on the untrusted host, or scope it so the confidential GPU's per-workload utilization/power/memory is not exported), and restrict GPU profiling/performance counters for the confidential context.
- Disable host-side DCGM/NVML/dmon export for the confidential GPU; restrict profiling counters.
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).