CSPACE-SECRET-01: Secret Manager access is federated through the attested pool¶
| Property | Value |
|---|---|
| Severity | high |
| Platform | GCP Confidential Space (AMD SEV-SNP) |
| Lifecycle stage | attest |
| Mode | Passive: read-only cloud API calls. |
What it checks¶
It passes when:
- All Secret Manager grants are federated through a Workload Identity pool.
Example failures:
- … secret-access grant(s) are not federated through a Workload Identity pool: …. The secret is retrievable without an attestation token.
- … secret-access grant(s) are not federated through a Workload Identity pool — the secret is retrievable without an attestation token.
How to fix¶
- Grant secretmanager.secretAccessor only to a principalSet:// member scoped to the Confidential Space workload identity pool, and remove allUsers/allAuthenticatedUsers and plain service-account grants.
After the fix, scan again: the check should report PASS.
When it is not assessed¶
SKIP:
- No --gcp-secret specified; skipping check.
ERROR:
- Could not read Secret Manager IAM policy: …
Scan inputs¶
The untrust scan options this check reads:
| Option | Description |
|---|---|
--gcp-secret |
Secret Manager secret to audit attestation-gated access on. |
Permissions¶
The cloud API calls this check makes, read from the scanner's source:
| Cloud | API call | Permission | Access |
|---|---|---|---|
| Google Cloud | secretmanager.projects.secrets.getIamPolicy |
secretmanager.secrets.getIamPolicy |
read |
See Required permissions for every check on this platform.
Generated from untrust 1.3.0 (commit 7ef462d9a0c3).