Skip to main content
Compliance · Medium severity

GCP IAM Project-Level Role Binding

The grant applies to every resource in the project rather than the one it was needed for, so access is far wider than anyone intended.

Free to start. No card. The playground just needs your work email.

Google Cloudprovider
Mediumseverity
Compliancewhere it shows up
Manualfix, steps written out

Google Cloud

Found, explained, handed over.

Where the estate departs from your policies, frameworks and tagging rules.

01

Detect

ZopNight checks this automatically across Google Cloud, with read-only access to the account.

02

Explain

Every finding says exactly what to change: Scope IAM role to resource level.

03

Fix

The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.

Applies to
Any resource in the account
The fix, by hand
  1. List project-level role bindings that affect ‹name›: gcloud projects get-iam-policy ‹project› --format=json | jq '.bindings[]'.
  2. For each broad binding (roles/editor, roles/owner, roles/viewer at project scope), identify which principals actually need access to which resources.
  3. Re-bind at the resource level instead: gcloud ‹service› add-iam-policy-binding ‹name› --member=user:foo@example.com --role=roles/‹specific›.
  4. Remove the project-level binding: gcloud projects remove-iam-policy-binding ‹project› --member=... --role=roles/editor.
  5. Use IAM Recommender (Cloud Console → IAM and Admin → IAM → Recommendations column) to find right-sized roles automatically.
  6. Set Org Policy constraints/iam.automaticIamGrantsForDefaultServiceAccounts = enforced to stop new broad bindings.

These are the steps the finding carries in the product.

Category
Compliance. Configuration drift from best practice: public access, missing MFA, unencrypted storage, deprecated runtimes.
Where it appears
The Compliance tab of Recommendations, with every affected resource listed.
Rule ID
RC-1251
Full reference

GCP IAM Project-Level Role Binding

Related checks

See the compliance findings in your account.

Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.

Prefer to talk it through first? Book 20 minutes with the team.

  • $30M+annualised cloud spend under management
  • 550K+resources tracked since launch
  • 20-60%off the bill in the first month
  • SOC 2Type II report, plus ISO 27001

Figures published on zop.dev.

Multi-cloud automation· Production-ready in 30 min· SOC 2 · ISO 27001· 20–60% off the bill, first month· 4 platforms · 1 console· Multi-cloud automation· Production-ready in 30 min· SOC 2 · ISO 27001· 20–60% off the bill, first month· 4 platforms · 1 console·