CIS Amazon Web Services Foundations Benchmark v1.2.0/Identity and Access Management/13 of 49
1.13Ensure MFA is enabled for the "root" account
Control family: Identity and Access Management
Control description
The root account is the most privileged user in an AWS account. MFA adds an extra layer of protection on top of a user name and password. With MFA enabled, when a user signs in to an AWS website, they will be prompted for their user name and password as well as for an authentication code from their AWS MFA device.
**Note:** When virtual MFA is used for root accounts, it is recommended that the device used is NOT a personal device, but rather a dedicated mobile device (tablet or phone) that is managed to be kept charged and secured independent of any individual personal devices. ("non-personal virtual MFA") This lessens the risks of losing access to the MFA due to device loss, device trade-in or if the individual owning the device is no longer employed at the company.
How to implement
ResponsibilityCustomerYou configure and operate this in your own cloud accounts.
The root user's password must never be enough on its own to get in. Registering an MFA device on the root user means a stolen password is useless without the device too. The device belongs to the organization, not to whoever set it up, and it is kept where the people allowed to use root can reach it and no one else can.
Before you start
The same on every cloud, before the steps in the tabs.
- Choose the MFA device for the root user: a security key or a dedicated, company-owned phone or tablet kept charged and locked away, never someone's personal phone.
- Record where it is kept and who may take it out, and register a second device so losing one doesn't lock the account.
Evidence
- The custody record for the root MFA devices
Not applicable. This benchmark covers AWS only.
On AWS the tasks register the MFA device from the root user's security credentials, then add the AWS Config rule that tests for it.
Task 1Register an MFA device on the root user
- Sign in to the AWS Management Console at console.aws.amazon.com as the root user.
- Choose your account name on the right of the navigation bar, then Security credentials.
- In the Multi-Factor Authentication (MFA) section, choose Assign MFA device.
- Type a Device name, choose Authenticator app for the dedicated device (or Passkey or security key), and choose Next.
- For an app, choose Show QR code and scan it with the dedicated device.
- Enter the first code in MFA code 1, wait for the code to change, enter the next one in MFA code 2, and choose Add MFA.
- Repeat for the second device, then sign out and back in to check that the device is asked for.
Task 2Keep it checked with the AWS Config rule root-account-mfa-enabled
- 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 root-account-mfa-enabled, 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.
Evidence
- The root user's Security credentials page, showing the registered MFA devices
- The root-account-mfa-enabled rule, showing compliant, and Security Hub CSPM control IAM.9 showing passed
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.