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

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

1.11Ensure that Separation of duties is enforced while assigning KMS 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 KMS related roles to users.

How to implement

ResponsibilityCustomerYou configure and operate this in your own cloud accounts.

Whoever manages keys (Cloud KMS Admin) shouldn't also be able to use them to encrypt and decrypt data (the CryptoKey Encrypter/Decrypter roles), or one person could both change a key's rules and read what it protects. Owners of a project hold both powers, so projects that hold keys have no human Owner.

Before you start

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

  • Name who administers keys and which workloads and people use them, and keep the two apart.
  • Keep keys in projects of their own, separate from the data they protect.

Evidence

  • The named groups for key administration and key use, and the key project list

On Google Cloud the tasks separate the key roles in IAM, remove Owner from projects that hold keys, and watch with Security Command Center.

Task 1Separate key administration from key use

  1. Sign in to the Google Cloud console at console.cloud.google.com and open IAM & Admin > IAM for the project that holds the keys.
  2. Choose View by roles, expand Cloud KMS Admin and the Cloud KMS CryptoKey Encrypter/Decrypter, Encrypter and Decrypter roles.
  3. For any principal under both an admin role and a use role, choose Edit principal on View by principals, remove one with Delete role and choose Save.
  4. Check it: no principal appears under both kinds of role.

Task 2Remove Owner from projects that hold keys

  1. On the IAM page of the key project, find each principal with the Owner role.
  2. Choose Edit principal, choose Delete next to Owner, and give narrower roles if needed.
  3. Choose Save.
  4. Check it: the key project has no Owner left, apart from break-glass access you have recorded.

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

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

Evidence

  • The View by roles tab of each key project, with administration and use held by different people
  • Security Command Center, with no active KMS_PROJECT_HAS_OWNER 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.