GCP Service Account Has User-Managed Keys
A downloadable key file exists, and it is the credential most often committed to a repository or baked into an image.
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: Migrate service account to Workload Identity.
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
- Identify where the user-managed key is used (GKE workload, Cloud Run, on-prem).
- For GKE workloads: enable Workload Identity on the cluster and configure the Kubernetes service account binding.
- For Cloud Run: the service already supports automatic service account identity. No key needed.
- For external workloads: configure Workload Identity Federation with the external IdP.
- After migrating, delete the user-managed key from the service account.
- Audit source code repositories for committed key files.
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-131- 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.