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

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

1.8Ensure that Separation of duties is enforced while assigning service account related roles to users

Control family: Identity and Access Management

Control description

It is recommended that the principle of 'Separation of Duties' is enforced while assigning service-account related roles to users.

How to implement

ResponsibilityCustomerYou configure and operate this in your own cloud accounts.

Someone who can both create service accounts (Service Account Admin) and act as them (Service Account User) can make a new account, give it power, and use it, all without anyone else involved. Splitting the two roles between different people means creating and using a service account always takes two.

Before you start

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

  • Name who administers service accounts and who deploys with them, and keep the two groups apart.

Evidence

  • The named groups for service account administration and use

On Google Cloud the tasks find principals holding both roles in IAM, remove one of them, and watch with Security Command Center.

Task 1Find principals holding both roles

  1. Sign in to the Google Cloud console at console.cloud.google.com and open IAM & Admin > IAM for the project, folder or organization.
  2. Choose the View by roles tab.
  3. Expand Service Account Admin and Service Account User and note any principal listed under both, directly or through a group.

Task 2Remove one of the two roles

  1. Choose View by principals, and for each principal found, choose Edit principal.
  2. Decide with the owner which role they need, and choose Delete role next to the other.
  3. Choose Save.
  4. Check it: no principal appears under both roles on View by roles.

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

  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 SERVICE_ACCOUNT_ROLE_SEPARATION with state ACTIVE, and select Apply.
  3. Open each finding, read the resource and the explanation it gives, and remove one of the roles from the principal it names.
  4. Check it: after the next Security Health Analytics scan, no active SERVICE_ACCOUNT_ROLE_SEPARATION finding remains.

Evidence

  • The View by roles tab, with no principal holding both roles
  • Security Command Center, with no active SERVICE_ACCOUNT_ROLE_SEPARATION 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.