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

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

1.1Ensure that corporate login credentials are used

Control family: Identity and Access Management

Control description

Use corporate login credentials instead of personal accounts, such as Gmail accounts.

How to implement

ResponsibilityCustomerYou configure and operate this in your own cloud accounts.

Access to Google Cloud should go only to accounts the organization controls: identities in its own Cloud Identity or Google Workspace domain. Personal accounts such as consumer Gmail addresses sit outside your password, MFA and offboarding rules, so access granted to them can't be taken back when someone leaves.

Before you start

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

  • Decide which identities may hold roles in Google Cloud: users and groups from your Cloud Identity or Workspace domain, and service accounts.
  • Agree how outside people (contractors, partners) get access: a managed account in your domain, never a personal address.

Evidence

  • The identity standard for Google Cloud access

On Google Cloud the tasks remove outside identities from IAM, restrict IAM to your own domain with an organization policy, and watch with Security Command Center.

Task 1Remove personal accounts from IAM

  1. Sign in to the Google Cloud console at console.cloud.google.com and pick the organization, then each folder and project in turn.
  2. Open IAM & Admin > IAM.
  3. Look for principals whose address is outside your domain, such as gmail.com addresses.
  4. Give the person a corporate account with the same access if they still need it.
  5. Select the checkbox next to each outside principal and choose Remove.
  6. Check it: the IAM page lists only identities from your domain, groups and service accounts.

Task 2Prevent it with the organization policy iam.allowedPolicyMemberDomains

  1. Open IAM & Admin > Organization policies with the organization (or the folder that holds your projects) selected in the project picker.
  2. Search for iam.allowedPolicyMemberDomains (Domain restricted sharing) and open it.
  3. Choose Manage policy, select Override parent's policy, choose Add a rule and under Policy values choose Custom, set Policy type to Allow and add your Cloud Identity or Workspace customer ID.
  4. Choose Set policy.
  5. Check it: granting a role to a gmail.com address in any project is refused.

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

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

Evidence

  • The IAM pages of the organization, folders and projects, with no outside identities
  • The iam.allowedPolicyMemberDomains policy, allowing only your customer ID
  • Security Command Center, with no active NON_ORG_IAM_MEMBER 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.