CIS Google Cloud Platform Foundation Benchmark v1.2.0/Identity and Access Management/2 of 83
1.2Ensure that multi-factor authentication is enabled for all non-service accounts
Control family: Identity and Access Management
Control description
Setup multi-factor authentication for Google Cloud Platform accounts.
How to implement
ResponsibilityCustomerYou configure and operate this in your own cloud accounts.
Every person who signs in to Google Cloud does so with a Google identity, so multi-factor authentication is switched on where those identities live: the Cloud Identity or Google Workspace Admin console. With 2-Step Verification enforced, a stolen password alone doesn't open the console. Service accounts don't sign in this way and aren't in scope.
Before you start
The same on every cloud, before the steps in the tabs.
- Decide which second factors are allowed (security keys or the Google prompt preferred, text messages avoided) and how a lost device is replaced.
- Give people a clear enrolment period and a help desk route before enforcement starts.
Evidence
- The MFA standard and the enrolment communication
Not applicable. This benchmark covers Google Cloud only.
Not applicable. This benchmark covers Google Cloud only.
On Google Cloud the tasks list who has access in IAM, enforce 2-Step Verification for them in the Admin console, and watch with Security Command Center.
Task 1List the people who can reach Google Cloud
- Sign in to the Google Cloud console at console.cloud.google.com and pick the organization in the project picker.
- Open IAM & Admin > IAM and note the users and groups with roles, here and on folders and projects.
- Note the organizational units in your Cloud Identity or Workspace account that those users belong to.
Task 2Enforce 2-Step Verification for those users
- Sign in to the Admin console at admin.google.com as a super administrator.
- Open Security > Authentication > 2-step verification.
- Select the organizational unit at the top of the tree so the setting covers everyone, or each unit that holds cloud users.
- Select Allow users to turn on 2-Step Verification, set Enforcement to On (or On from a date that gives people time to enrol) and choose a short New user enrollment period.
- Under Methods, choose Any except verification codes via text, phone call or stronger.
- Choose Save.
- Check it: in Directory > Users, add the 2-step verification enforcement column and confirm it shows enforced for every cloud user.
Task 3Keep it checked with the Security Health Analytics finding MFA_NOT_ENFORCED
- 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 MFA_NOT_ENFORCED with state ACTIVE, and select Apply.
- Open each finding, read the resource and the explanation it gives, and enforce 2-Step Verification for the users it lists.
- Check it: after the next Security Health Analytics scan, no active MFA_NOT_ENFORCED finding remains.
Evidence
- The Admin console 2-step verification settings, showing enforcement on for the units that hold cloud users
- The user list with 2-step verification enrolment and enforcement
- Security Command Center, with no active MFA_NOT_ENFORCED 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.