CSPACE-ATT-01: Confidential Space token claims meet production policy¶
| Property | Value |
|---|---|
| Severity | critical |
| Platform | GCP Confidential Space (AMD SEV-SNP) |
| Lifecycle stage | attest |
| Policy | P-04: Attestation evidence is fresh and fully verified |
| Assurance | report-derived |
| Mode | Passive: reads only the files and values you pass to the scan. |
What a failure enables¶
- Keys released to a debuggable workload
What it checks¶
It passes when:
- Unverified token claims meet non-debug, supported-image, image-signature presence and AMD SEV-family policy.
How to fix¶
- Launch the workload from a non-debug (production) Confidential Space image, deploy a cosign-signed workload container, and require STABLE/LATEST support. Separately verify token signatures, issuer, audience, freshness and approved image signer before key release. Confirm SNP hardware through independent evidence.
- Launch from a non-debug Confidential Space image, deploy a cosign-signed workload container, and run on an AMD SEV-SNP machine type.
After the fix, scan again: the check should report PASS.
When it is not assessed¶
SKIP:
- No --attestation-token specified; skipping check.
ERROR:
- Could not read a bounded, structurally valid attestation token.
Scan inputs¶
The untrust scan options this check reads:
| Option | Description |
|---|---|
--attestation-token |
Path to a captured Confidential Space attestation token (JWT). |
Permissions¶
None. The check reads only the files or values you pass to the scan.
Related¶
- Other checks for policy P-04: CCA-CERT-01, CSPACE-ATT-02, CSPACE-ATT-03, GPU-CERT-01, GPUCC-ATT-01, NITRO-ATT-02, NITRO-ATT-03, SE-CERT-01, SGX-CERT-01, SNP-CERT-01, TDX-CERT-01
Generated from untrust 1.3.0 (commit 7ef462d9a0c3).