Routine Google Cloud administration should not use the super-admin account
This check looks at whether day-to-day administration in Google Cloud is done with the super-admin account. The safe setting is to keep that account for rare, high-trust tasks and use narrower admin roles for everything else.
Why it matters
A super-admin session that is used for daily work is exposed far more often: more sign-ins, more browser sessions and more chances for a phished or stolen session to carry unlimited rights. Using narrower roles for routine work limits what a mistake or a compromised session can do, and it makes the audit trail clearer, because super-admin activity then stands out as unusual.
Google recommends reserving super administrator accounts for the few tasks that require them. See the Google Cloud super administrator best practices.
How to check it yourself
In the Google Admin console open Reporting > Audit and investigation and filter the admin log by the super-admin account's address. In Google Cloud console, open IAM & Admin > Audit Logs and review which principals perform routine changes. If the super-admin address appears in everyday project work, the check is not met.
A read-only command to see recent activity by one principal (replace the address with the account you want to review):
gcloud logging read \
'protoPayload.authenticationInfo.principalEmail="superadmin@example.com"' \
--organization=ORGANIZATION_ID --limit=50 \
--format="table(timestamp,protoPayload.methodName)"Reading logs needs a role that can view them, such as Logs Viewer, and changes nothing.
How to fix it
Give each administrator a named account with only the roles their job needs, for example a folder or project level admin role instead of super admin. Keep the super-admin account for break-glass tasks such as recovering access or changing organization-level ownership, and sign in with it only for those. Review the audit log again after a few weeks to confirm the habit has changed.
Example of granting a narrower role to a group (this changes IAM, so apply it yourself; ConfigCobra stays read-only):
gcloud organizations add-iam-policy-binding ORGANIZATION_ID \
--member="group:cloud-admins@example.com" \
--role="roles/resourcemanager.folderAdmin"What changes when you fix it
Administrators who currently do everything as super admin will find some actions refused until they hold the right role, so list the tasks each person does before you remove access and grant roles to match. Expect a short period of access requests. Workloads and end users are not affected. Afterwards, super-admin sign-ins become rare events that are easy to review. Write down which tasks justify using the super-admin account, so everyone applies the same rule and exceptions are deliberate rather than habitual.
Included in
| Benchmark | CIS ID | Profile |
|---|---|---|
| CIS Google Cloud Platform Foundation v5.0.0 | 1.1.2 | 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.