CIS Google Cloud Platform Foundation Benchmark v1.2.0/Identity and Access Management/5 of 83
1.5Ensure that Service Account has no Admin privileges
Control family: Identity and Access Management
Control description
A service account is a special Google account that belongs to an application or a VM, instead of to an individual end-user. The application uses the service account to call the service's Google API so that users aren't directly involved. It's recommended not to use admin access for ServiceAccount.
How to implement
ResponsibilityCustomerYou configure and operate this in your own cloud accounts.
A service account is used by software, and software can be tricked or compromised. If the account holds Owner, Editor or an admin role, whoever controls the workload controls the project. Service accounts get narrow, predefined or custom roles that match what the workload does, never basic or administrative roles.
Before you start
The same on every cloud, before the steps in the tabs.
- Agree that service accounts get narrow roles matched to their workload, never Owner, Editor or admin roles, and who reviews their grants.
- Review service account roles on a schedule, such as quarterly.
Evidence
- The service account standard and the review record
Not applicable. This benchmark covers Google Cloud only.
Not applicable. This benchmark covers Google Cloud only.
On Google Cloud the tasks remove administrative roles from service accounts in IAM, stop default service accounts getting Editor automatically, and watch with Security Command Center.
Task 1Remove administrative roles from service accounts
- Sign in to the Google Cloud console at console.cloud.google.com and open IAM & Admin > IAM.
- For each service account holding Owner, Editor or a role whose name includes Admin, choose Edit principal.
- Choose Delete role next to each administrative role, and add the narrow roles the workload needs instead.
- Choose Save.
- Check it: the IAM page shows no service account with Owner, Editor or an admin role.
Task 2Prevent it with the organization policy iam.automaticIamGrantsForDefaultServiceAccounts
- Open IAM & Admin > Organization policies with the organization (or the folder that holds your projects) selected in the project picker.
- Search for iam.automaticIamGrantsForDefaultServiceAccounts (Disable Automatic IAM Grants for Default Service Accounts) 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: the default service account of a newly created project has no Editor role.
Task 3Keep it checked with the Security Health Analytics finding ADMIN_SERVICE_ACCOUNT
- 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 ADMIN_SERVICE_ACCOUNT with state ACTIVE, and select Apply.
- Open each finding, read the resource and the explanation it gives, and remove the administrative role from the service account it names.
- Check it: after the next Security Health Analytics scan, no active ADMIN_SERVICE_ACCOUNT finding remains.
Evidence
- The IAM page of each project, with no service account holding Owner, Editor or an admin role
- The iam.automaticIamGrantsForDefaultServiceAccounts policy, enforced
- Security Command Center, with no active ADMIN_SERVICE_ACCOUNT 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.