CIS Google Cloud Platform Foundation Benchmark v1.2.0/Identity and Access Management/3 of 83
1.3Ensure that Security Key Enforcement is enabled for all admin accounts
Control family: Identity and Access Management
Control description
Setup Security Key Enforcement for Google Cloud Platform admin accounts.
How to implement
ResponsibilityCustomerYou configure and operate this in your own cloud accounts.
Administrators of the organization can change anything, so their accounts need a factor that phishing can't steal. Security keys prove themselves only to the real Google sign-in page, unlike codes that can be typed into a fake one. Requiring security keys for administrator accounts closes that gap.
Before you start
The same on every cloud, before the steps in the tabs.
- Buy two FIDO security keys for each administrator, one for daily use and one kept safe as a spare.
- Agree how a lost key is reported and replaced.
Evidence
- The list of administrators, their enrolled security keys and the lost-key procedure
Not applicable. This benchmark covers Google Cloud only.
Not applicable. This benchmark covers Google Cloud only.
On Google Cloud the tasks put administrator accounts into their own organizational unit and require security keys for it in the Admin console.
Task 1Find the administrator accounts
- 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 who holds Organization Administrator, Owner, Folder Admin, Security Admin and other administrative roles.
- In the Admin console at admin.google.com, open Account > Admin roles and note who holds Super Admin and other admin roles.
- Move all these accounts into an organizational unit such as cloud-admins under Directory > Users > Change organizational unit.
Task 2Require security keys for administrators
- In the Admin console, open Security > Authentication > 2-step verification.
- Select the cloud-admins organizational unit.
- Set Enforcement to On, and under Methods choose Only security key.
- Set Security codes so codes can't be used in place of the key, unless your recovery process needs them.
- Choose Save, and make sure each administrator has enrolled two keys first.
- Check it: an administrator who tries to sign in without the key is refused.
Evidence
- The cloud-admins organizational unit and its members
- The 2-step verification settings for that unit, showing only security keys allowed
- The list of enrolled security keys per administrator
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.