CIS Google Cloud Platform Foundation Benchmark v1.2.0/Identity and Access Management/4 of 83
1.4Ensure that there are only GCP-managed service account keys for each service account
Control family: Identity and Access Management
Control description
User managed service accounts should not have user-managed keys.
How to implement
ResponsibilityCustomerYou configure and operate this in your own cloud accounts.
A service account key is a long-lived private key file. Once downloaded it can be copied anywhere, used from anywhere and rarely gets rotated, which makes it one of the most common causes of cloud breaches. Google-managed keys, used behind the scenes by attached service accounts and Workload Identity Federation, never leave Google. User-managed keys are removed and new ones are blocked.
Before you start
The same on every cloud, before the steps in the tabs.
- List the workloads that use downloaded service account keys today, and plan how each moves to an attached service account or Workload Identity Federation.
- Agree who may approve an exception, and for how long.
Evidence
- The key inventory, the migration plan and the exception register
Not applicable. This benchmark covers Google Cloud only.
Not applicable. This benchmark covers Google Cloud only.
On Google Cloud the tasks delete user-managed keys from service accounts in IAM, block new ones with an organization policy, and watch with Security Command Center.
Task 1Delete user-managed keys
- Sign in to the Google Cloud console at console.cloud.google.com and open IAM & Admin > Service accounts.
- Open a service account and choose the Keys tab.
- For each key, find out what uses it, and move that workload to an attached service account or Workload Identity Federation.
- When nothing uses the key, disable it, wait to be sure nothing breaks, then delete it.
- Check it: the Keys tab lists no user-managed keys.
Task 2Prevent it with the organization policy iam.disableServiceAccountKeyCreation
- Open IAM & Admin > Organization policies with the organization (or the folder that holds your projects) selected in the project picker.
- Search for iam.disableServiceAccountKeyCreation (Disable service account key creation) and open it.
- Choose Manage policy, select Override parent's policy, choose Add a rule and set Enforcement to On.
- Choose Set policy.
- Check it: choosing Add key > Create new key on a service account is refused.
Task 3Keep it checked with the Security Health Analytics finding USER_MANAGED_SERVICE_ACCOUNT_KEY
- Open Security Command Center > Findings for the organization (Security Health Analytics runs on the Premium tier for most detectors).
- In the query editor, filter on category USER_MANAGED_SERVICE_ACCOUNT_KEY with state ACTIVE, and select Apply.
- Open each finding, read the resource and the explanation it gives, and delete the key it names once nothing uses it.
- Check it: after the next Security Health Analytics scan, no active USER_MANAGED_SERVICE_ACCOUNT_KEY finding remains.
Evidence
- The Keys tab of each service account, with no user-managed keys
- The iam.disableServiceAccountKeyCreation policy, enforced
- Security Command Center, with no active USER_MANAGED_SERVICE_ACCOUNT_KEY finding
Console steps as of 5 November 2026. Not every step has been confirmed in a live console yet, and menus and labels can move between releases, so look for the nearest match if one has changed.