CSPACE-KEYBIND-03: Confidential Space key release requires Secure Boot¶
| Property | Value |
|---|---|
| Severity | medium |
| Platform | GCP Confidential Space (AMD SEV-SNP) |
| Lifecycle stage | attest |
| Policy | P-03: Key release requires an attested measurement |
| Mode | Passive: read-only cloud API calls. |
What it checks¶
It passes when:
- WIF provider condition requires assertion.secboot == true.
Example failures:
- WIF provider condition could not be parsed as CEL — its structure cannot be verified, so Secure-Boot binding is treated as unproven (fail closed).
- WIF provider condition does not require assertion.secboot == true — a VM that did not boot with Secure/Measured Boot could still release the key.
How to fix¶
- Add a Secure-Boot conjunct to the WIF provider attribute condition, e.g.: assertion.secboot == true kept ANDed with the code-measurement bindings (dbgstat == 'disabled-since-boot' and a pinned image_digest) from CSPACE-KEYBIND-01, so the key is released only to a VM that booted with Secure/Measured Boot. This check gates P-03 (key release requires an attested measurement): a FAIL blocks a gated release, so an existing Confidential Space deployment whose condition does not require secboot will newly block until 'assertion.secboot == true' is added.
After the fix, scan again: the check should report PASS.
When it is not assessed¶
SKIP:
- No --wip-provider specified; skipping check.
- WIF provider has no attribute condition; CSPACE-KEYBIND-01 reports this unbound provider. Secure-boot binding not assessed.
ERROR:
- Could not read WIF provider condition: …
Scan inputs¶
The untrust scan options this check reads:
| Option | Description |
|---|---|
--wip-provider |
WIF provider resource gating key release. |
Permissions¶
The cloud API calls this check makes, read from the scanner's source:
| Cloud | API call | Permission | Access |
|---|---|---|---|
| Google Cloud | iam.projects.locations.workloadIdentityPools.providers.get |
iam.workloadIdentityPoolProviders.get |
read |
See Required permissions for every check on this platform.
Related¶
- Other checks for policy P-03: CSPACE-KEYBIND-01, CSPACE-KMS-01, CSPACE-KMS-02, GPUCC-BIND-01, GPUCC-DECRYPT-01, GPUCC-KEY-01, HSM-01, KBS-01, KMS-01, VAULT-01
Generated from untrust 1.3.0 (commit 7ef462d9a0c3).