GPUCC-KEY-01: Model/data key and workload identity are not an attestation bypass¶
| Property | Value |
|---|---|
| Severity | high |
| Platform | NVIDIA GPU Confidential Computing |
| Lifecycle stage | attest |
| Policy | P-03: Key release requires an attested measurement |
| Trust boundary | inputs |
| Assurance | operator-declared |
| Mode | Passive: reads only the files and values you pass to the scan. |
What a failure enables¶
- Model key and plaintext weights in host memory
What it checks¶
It passes when:
- DEK is KBS-released + rotated, and the workload SA can't be impersonated.
How to fix¶
- Release the DEK only from an attestation-gated KBS (never via host env), rotate it, remove workload-SA user-managed keys, and scope serviceAccountTokenCreator/actAs so nothing can impersonate the workload.
- KBS-release + rotate the DEK; drop SA keys; scope impersonation.
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.
Related¶
- Other checks for policy P-03: CSPACE-KEYBIND-01, CSPACE-KEYBIND-03, CSPACE-KMS-01, CSPACE-KMS-02, GPUCC-BIND-01, GPUCC-DECRYPT-01, HSM-01, KBS-01, KMS-01, VAULT-01
Generated from untrust 1.3.0 (commit 7ef462d9a0c3).