GCP primitive Owner/Editor roles granted broadly
GCP's primitive roles — Owner, Editor, Viewer — predate IAM's predefined roles and are extremely broad. Owner and Editor let a principal change almost anything in a project.
Why it matters
A single Editor binding gives far more than most workloads need; if that identity is compromised, the blast radius is the whole project.
Owner can change IAM itself, so an attacker who reaches an Owner can grant themselves persistence and lock others out.
How to check for it
- gcloud projects get-iam-policy <project> --flatten="bindings[].members" --filter="bindings.role:roles/owner OR bindings.role:roles/editor".
- Review which users and service accounts hold roles/owner or roles/editor.
How to fix it
- Replace primitive roles with predefined or custom roles scoped to the exact permissions each identity needs.
- Reserve Owner for a very small set of humans, and never attach it to a service account used by a workload.
SkyShield checks this automatically
Connect your AWS, Cloudflare, GitHub, GitLab, Hetzner or DigitalOcean account read-only and SkyShield flags this across every account and region, with the fix in plain words — alongside the agent that watches your servers. Start free.
FAQ
- How do I find the least-privilege role to use instead?
- Use IAM Recommender and the policy analyzer — they suggest narrower roles based on the permissions the identity has actually used.