Google Cloud should enforce guardrails through organization policies set at the organization level
This check looks at whether organization policy constraints are configured centrally, at the organization or folder level, instead of project by project. The safe setting is a set of enforced constraints on the organization resource that every project inherits.
Why it matters
Without central guardrails, every team decides on its own whether service account keys may be created, whether VMs may get public IPs or which regions are allowed. One forgotten project is enough to undo a rule you thought applied everywhere. Organization policies let administrators set a constraint once on the organization or a folder, and every project below inherits it unless an exception is granted on purpose.
Google documents the inheritance model and the catalogue of available constraints. Choosing a handful that match your risks, such as blocking service account key creation or restricting where resources may live, is a sensible starting point.
Sources: Introduction to the Organization Policy Service (Google Cloud) and Using constraints (Google Cloud).
How to check it yourself
Console: choose your organization in the project picker, then open IAM & Admin → Organization Policies. Constraints that carry a custom or enforced setting at the organization level are the ones that apply everywhere.
gcloud (read-only):
gcloud org-policies list --organization=ORGANIZATION_ID
gcloud org-policies describe iam.disableServiceAccountKeyCreation `
--organization=ORGANIZATION_ID --effectiveAn empty list from the first command means nothing is centrally enforced. The second shows what a project actually ends up with after inheritance. Both commands only read policy and need the Organization Policy Viewer role or similar.
How to fix it
Console: in Organization Policies choose the organization, open a constraint (for example Disable service account key creation), click Manage policy, set it to enforced and save. Start with a few constraints and widen over time.
Script: the commands below change the policy, so use a test folder first. ConfigCobra never applies them for you.
cat > policy.yaml <<'EOF'
name: organizations/ORGANIZATION_ID/policies/iam.disableServiceAccountKeyCreation
spec:
rules:
- enforce: true
EOF
gcloud org-policies set-policy policy.yamlGoogle's guide explains a dry-run mode that logs what a policy would block without blocking it; use that on constraints that could affect running workloads.
What changes when you fix it
Developers and project owners will find that some actions are now denied in every project, with an error that names the constraint. Typical examples: creating a key for a service account, creating a VM with an external IP, or creating a resource outside the allowed locations.
Existing resources usually keep running; a constraint mostly stops new or changed configurations. Still, a pipeline that creates keys or public addresses as part of its routine will start to fail, so find those first and give them an alternative, or a documented exception on a specific folder or project.
Administrators now own the policy: changes go through whoever holds the Organization Policy Administrator role, which should be a small group.
Included in
| Benchmark | CIS ID | Profile |
|---|---|---|
| CIS Google Cloud Platform Foundation v5.0.0 | 1.1.4 | Level 2 |
Go further
- Identity and Access Management21 controls in this section
- CIS Google Cloud Platform Foundation v5.0.093 controls
- CIS Google Cloud Platform Foundation checklistEvery control in one list, as CSV
- RemediationSee what a fix changes in your tenant before you apply it, then use the generated script
- Monitoring & DriftScheduled scans, drift detection and email alerts when a control regresses
Check this on your Google Cloud
ConfigCobra runs this check with every other control of the CIS Google Cloud Platform Foundation Benchmark, read-only.