The super-admin account should not belong to one named person
This check looks at who holds the super-admin account for your Google Cloud organization. The safe setting is a dedicated account that is not one person's everyday mailbox, so access survives staff changes.
Why it matters
The super administrator account sits above every other permission in a Google Cloud organization. It can recover access, change who owns the organization and reset other admins. If that account is the personal address of one employee, the organization depends on that person: when they leave, change role or lose their phone, nobody else can recover the organization, and their personal sign-in habits become the weak point for the most powerful account you have.
Google's own guidance for super administrator accounts is to keep them few, use them only for the tasks that need them, and not tie them to an individual's regular identity. See the Google Cloud super administrator best practices.
How to check it yourself
In the Google Admin console go to Account > Admin roles, open Super Admin and read the list of assigned admins. Look at each address: is it a named person's daily mailbox, or a dedicated account owned by the company?
From the command line you can read, without changing anything, which identities hold the Organization Administrator role (the role most closely tied to super-admin use). Run it on a test organization first:
gcloud organizations get-iam-policy ORGANIZATION_ID \
--flatten="bindings" \
--filter="bindings.role:roles/resourcemanager.organizationAdmin" \
--format="table(bindings.members)"This lists IAM members only. The super-admin list itself is read in the Admin console.
How to fix it
Create a dedicated super-admin account that is not a person's daily mailbox, for example a role-style address controlled by the company. Protect it with a hardware security key, store the recovery details in your company's secure vault and name at least one backup custodian. Then remove super-admin from individuals who do not need it, and give them narrower roles for daily work.
For the IAM side, grant the Organization Administrator role to a group instead of to people, so membership is managed in one place (this command changes IAM, so run it yourself, deliberately; ConfigCobra never changes your environment):
gcloud organizations add-iam-policy-binding ORGANIZATION_ID \
--member="group:org-admins@example.com" \
--role="roles/resourcemanager.organizationAdmin"What changes when you fix it
The people who used to sign in as super admin with their own address will need to use their normal admin roles, or ask the account's custodians for the dedicated account when a super-admin task comes up. Nothing changes for workloads, projects or end users. Plan the hand-over first: confirm the new account can sign in and that the custodians know the recovery steps before you remove the old assignment, so you never leave the organization without a working super admin.
Included in
| Benchmark | CIS ID | Profile |
|---|---|---|
| CIS Google Cloud Platform Foundation v5.0.0 | 1.1.1 | Level 1 |
Go further
- Identity and Access Management21 controls in this section
- CIS Google Cloud Platform Foundation v5.0.093 controls
- CIS Google Cloud Platform Foundation checklistEvery control in one list, as CSV
- RemediationSee what a fix changes in your tenant before you apply it, then use the generated script
- Monitoring & DriftScheduled scans, drift detection and email alerts when a control regresses
Check this on your Google Cloud
ConfigCobra runs this check with every other control of the CIS Google Cloud Platform Foundation Benchmark, read-only.