Compliancemanzill.com
CIS Google Cloud Platform Foundation Benchmark v1.2.0

CIS Google Cloud Platform Foundation Benchmark v1.2.0/Identity and Access Management/6 of 83

1.6Ensure that IAM users are not assigned the Service Account User or Service Account Token Creator roles at project level

Control family: Identity and Access Management

Control description

It is recommended to assign the `Service Account User (iam.serviceAccountUser)` and `Service Account Token Creator (iam.serviceAccountTokenCreator)` roles to a user for a specific service account rather than assigning the role to a user at project level.

How to implement

ResponsibilityCustomerYou configure and operate this in your own cloud accounts.

The Service Account User and Service Account Token Creator roles let a person act as a service account. Granted on the whole project, they let that person act as every service account in it, including future ones with more power. These roles are granted on the specific service account the person needs, not on the project.

Before you start

The same on every cloud, before the steps in the tabs.

  • List which people deploy with which service accounts, so the roles can be granted on those accounts only.
  • Add the rule to the access request process: these two roles are never granted on a whole project.

Evidence

  • The mapping of people to the service accounts they may use

On Google Cloud the tasks remove the project-level grants in IAM, grant the roles on individual service accounts instead, and watch with Security Command Center.

Task 1Remove the project-level grants

  1. Sign in to the Google Cloud console at console.cloud.google.com and open IAM & Admin > IAM for the project (and its folders and organization).
  2. Find principals holding Service Account User or Service Account Token Creator at this level, and note which service accounts each one really uses.
  3. Choose Edit principal, choose Delete role next to those roles and choose Save.
  4. Check it: neither role appears at project, folder or organization level.

Task 2Grant the roles on the service account instead

  1. Open IAM & Admin > Service accounts and choose the service account the person needs.
  2. Choose the Permissions tab (or Principals with access) and Grant access.
  3. Enter the person or group, choose Service Account User or Service Account Token Creator, and choose Save.
  4. Check it: the person can deploy with that service account but not with others.

Task 3Keep it checked with the Security Health Analytics finding OVER_PRIVILEGED_SERVICE_ACCOUNT_USER

  1. Open Security Command Center > Findings for the organization (Security Health Analytics runs on the Premium tier for most detectors).
  2. In the query editor, filter on category OVER_PRIVILEGED_SERVICE_ACCOUNT_USER with state ACTIVE, and select Apply.
  3. Open each finding, read the resource and the explanation it gives, and move the grant it names down to the service account.
  4. Check it: after the next Security Health Analytics scan, no active OVER_PRIVILEGED_SERVICE_ACCOUNT_USER finding remains.

Evidence

  • The project IAM page, with neither role granted at project level
  • The Permissions tab of each service account, listing who may use it
  • Security Command Center, with no active OVER_PRIVILEGED_SERVICE_ACCOUNT_USER 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.