GCP IAM Primitive Role in Use
Basic roles grant broad access across every service in the project, far beyond what any single job needs.
Free to start. No card. The playground just needs your work email.
Google Cloud
Found, explained, handed over.
Where the estate departs from your policies, frameworks and tagging rules.
Detect
ZopNight checks this automatically across Google Cloud, with read-only access to the account.
Explain
Every finding says exactly what to change: Replace primitive IAM role binding.
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
- IAM and Admin → IAM → filter Role = Owner / Editor / Viewer.
- For each principal, sample 30-day Cloud Logging activity (filter principalEmail).
- Map the observed methods to predefined roles (use the role-recommender API or the IAM Recommender panel).
- Add the narrower bindings → confirm workflows still work → remove the primitive binding.
- Block future primitive-role bindings via an Organization Policy constraint (iam.allowedPolicyMemberDomains plus a deny rule).
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-1250- Full reference
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.