CSPACE-IAM-INHERIT-01: No sensitive role is granted to a public principal at a folder/org ancestor¶
| Property | Value |
|---|---|
| Severity | high |
| Platform | GCP Confidential Space (AMD SEV-SNP) |
| Lifecycle stage | deploy |
| Mode | Passive: read-only cloud API calls. |
What it checks¶
It passes when:
- No public principal holds a sensitive role at a folder/org ancestor.
Example failures:
- … public grant(s) of a sensitive role inherited from an ancestor: …. These reach the workload's keys/identity without appearing in any resource policy.
- … public grant(s) of a sensitive role inherited from an ancestor — they reach the workload's keys/identity.
How to fix¶
- Remove allUsers/allAuthenticatedUsers grants of sensitive roles at the folder/org level; scope access to specific attested principals.
After the fix, scan again: the check should report PASS.
When it is not assessed¶
SKIP:
- Need --gcp-project; skipping check.
ERROR:
- Could not read ancestor IAM: …
Scan inputs¶
The untrust scan options this check reads:
| Option | Description |
|---|---|
--gcp-project |
GCP project ID. |
Permissions¶
The cloud API calls this check makes, read from the scanner's source:
| Cloud | API call | Permission | Access |
|---|---|---|---|
| Google Cloud | cloudresourcemanager.folders.get |
resourcemanager.folders.get |
read |
| Google Cloud | cloudresourcemanager.projects.get |
resourcemanager.projects.get |
read |
See Required permissions for every check on this platform.
Generated from untrust 1.3.0 (commit 7ef462d9a0c3).