GCP Service Account Has Admin Role
A non-human identity holds administrative rights, and its key can be copied out of a repository or an image without anyone noticing.
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: Remove admin-level roles from service account.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- Service Accounts on Google Cloud
- The fix, by hand
- Open IAM and Admin → Service Accounts in GCP Console.
- Identify which admin roles are bound to this service account.
- Remove the admin role bindings from the IAM policy.
- Replace with narrowly scoped predefined roles or create a custom role.
- Follow the principle of least privilege. Grant only the permissions the workload requires.
- Review other service accounts for the same pattern.
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-130- 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.