CIS Amazon Web Services Foundations Benchmark v1.2.0/Identity and Access Management/1 of 49
1.1Avoid the use of the "root" account
Control family: Identity and Access Management
Control description
The "root" account has unrestricted access to all resources in the AWS account. It is highly recommended that the use of this account be avoided.
How to implement
ResponsibilityCustomerYou configure and operate this in your own cloud accounts.
The root user can do anything in the account, and its actions can't be limited by IAM policies, so day-to-day work should never run through it. Administrators get their own named identities with administrator permissions, the root credentials go into safekeeping for the handful of tasks that truly need them, and any root sign-in is noticed and explained.
Before you start
The same on every cloud, before the steps in the tabs.
- List the few tasks that need the root user (for example closing the account or changing its support plan) and decide who may perform them.
- Store the root password and MFA device under dual control, and record every time they are taken out and why.
Evidence
- The documented list of root-only tasks and the custody record for the root credentials
Not applicable. This benchmark covers AWS only.
On AWS the tasks give administrators their own access through IAM Identity Center, then use the credential report and CloudTrail to show the root user stays unused.
Task 1Give administrators their own sign-in instead of root
- Sign in to the AWS Management Console at console.aws.amazon.com with an administrator identity (not root) in the management account.
- Open IAM Identity Center and choose Permission sets > Create permission set.
- Choose Predefined permission set, pick AdministratorAccess, choose Next, set the session duration to a few hours and choose Create.
- Choose Groups > Create group, name it cloud-administrators and add the named administrators.
- Choose AWS accounts, select the accounts they manage, choose Assign users or groups, pick cloud-administrators, then the AdministratorAccess permission set, and choose Submit.
- Check it: each administrator signs in through the AWS access portal and can do their work without the root password.
Task 2Confirm the root user hasn't been used
- Open IAM and choose Credential report in the navigation pane.
- Choose Download Report and open the file in a spreadsheet.
- Find the row whose user is the root account and read password_last_used, access_key_1_last_used_date and access_key_2_last_used_date.
- For any date since the last review, match it to an entry in the custody record; anything unexplained is handled as a security incident.
Task 3Find each root action in CloudTrail
- Open CloudTrail > Event history.
- Set the lookup attribute to User name, enter root and pick the review period.
- Open each event to see what was done, from which source IP address and when.
- Check it: every event lines up with a recorded, approved use of the root credentials.
Evidence
- The credential report, showing the root user's last password and access key use
- CloudTrail > Event history filtered to the root user for the review period, matched to the custody record
- IAM Identity Center > AWS accounts, showing administrators assigned through a permission set
Not applicable. This benchmark covers AWS only.
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.