CIS Amazon Web Services Foundations Benchmark v1.2.0/Identity and Access Management/12 of 49
1.12Ensure no root account access key exists
Control family: Identity and Access Management
Control description
The root account is the most privileged user in an AWS account. AWS Access Keys provide programmatic access to a given AWS account. It is recommended that all access keys associated with the root account be removed.
How to implement
ResponsibilityCustomerYou configure and operate this in your own cloud accounts.
An access key on the root user gives a program the power to do anything in the account, with nothing to limit it, and such keys tend to end up in scripts and old laptops. No task needs a root access key, so none should exist. In an AWS Organizations setup, member accounts can go further and have no root credentials at all.
Before you start
The same on every cloud, before the steps in the tabs.
- Confirm no process or script depends on a root access key, and record the owner of any key you find before it is deleted.
- Agree that root access keys are never created again and who checks it.
Evidence
- The record of root keys removed and the rule against creating new ones
Not applicable. This benchmark covers AWS only.
On AWS the tasks delete any root access key from the root user's security credentials, keep watching with the AWS Config rule, and, in an organization, remove root credentials from member accounts centrally.
Task 1Delete the root user's access keys
- Sign in to the AWS Management Console at console.aws.amazon.com as the root user, using the root email address and MFA.
- Choose your account name on the right of the navigation bar, then Security credentials.
- Under Access keys, note the last-used date of each key and find out what used it, so nothing breaks unexpectedly.
- For each key choose Actions > Deactivate, wait to be sure nothing depends on it, then choose Actions > Delete.
- Sign out of the root user.
- Check it: in a new credential report the root row shows access_key_1_active and access_key_2_active as false.
Task 2Keep it checked with the AWS Config rule iam-root-access-key-check
- Open AWS Config in the Region where you record global resources such as IAM, and choose Rules > Add rule.
- On Specify rule type, search for iam-root-access-key-check, select it and choose Next.
- On Configure rule, keep the name, then choose Next.
- On Review and create, check the settings and add the rule.
- Check it: once the rule has finished Evaluating..., the Rules page shows it as compliant.
Task 3Remove root credentials from member accounts centrally
- Sign in to the management account of your organization and open IAM.
- In the navigation pane, choose Root access management, then Enable (if it says the feature is disabled, turn on trusted access for IAM in AWS Organizations first).
- Under Capabilities to enable, select Root credentials management and Privileged root actions in member accounts, then choose Enable.
- Back in Root access management, select a member account and choose Take privileged action.
- Select Delete root credentials and confirm with Delete root credentials.
- Check it: the member account is listed without root credentials, so it has no root password, access key or MFA to protect.
Evidence
- The credential report, showing no active root access key
- The iam-root-access-key-check rule, showing compliant, and Security Hub CSPM control IAM.4 showing passed
- IAM > Root access management, showing member accounts without root credentials
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.