Compliancemanzill.com
CIS Amazon Web Services Foundations Benchmark v1.2.0

CIS Amazon Web Services Foundations Benchmark v1.2.0/Identity and Access Management/14 of 49

1.14Ensure hardware 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. For Level 2, it is recommended that the root account be protected with a hardware MFA.

How to implement

ResponsibilityCustomerYou configure and operate this in your own cloud accounts.

This Level 2 recommendation goes a step beyond 1.13: the root user's second factor should be a physical device, not an app on a phone that can be copied, backed up or infected. A FIDO security key or a hardware token is kept in a safe and used only when someone needs the root user.

Before you start

The same on every cloud, before the steps in the tabs.

  • Buy two hardware devices (FIDO security keys or hardware TOTP tokens) for each account whose root user keeps credentials.
  • Keep them in separate safes, record their serial numbers, and log every time one is taken out.

Evidence

  • The purchase record, serial numbers and custody log for each device

On AWS the tasks register the hardware device from the root user's security credentials, then add the AWS Config rule that tests for a hardware device.

Task 1Register a hardware device on the root user

  1. Sign in to the AWS Management Console at console.aws.amazon.com as the root user.
  2. Choose your account name on the right of the navigation bar, then Security credentials.
  3. Expand Multi-factor authentication (MFA) and choose Assign MFA device.
  4. Type a Device name, choose Hardware TOTP token (or Passkey or security key for a FIDO key) and choose Next.
  5. For a token, type the Serial number from its back, then two consecutive codes in MFA code 1 and MFA code 2; for a key, touch it when asked.
  6. Choose Add MFA, then register the second device the same way.
  7. Remove any virtual MFA device left on the root user, so only hardware devices remain.
  8. Check it: sign out and back in, and confirm the hardware device is asked for.

Task 2Keep it checked with the AWS Config rule root-account-hardware-mfa-enabled

  1. Open AWS Config in the Region where you record global resources such as IAM, and choose Rules > Add rule.
  2. On Specify rule type, search for root-account-hardware-mfa-enabled, select it and choose Next.
  3. On Configure rule, keep the name, then choose Next.
  4. On Review and create, check the settings and add the rule.
  5. Check it: once the rule has finished Evaluating..., the Rules page shows it as compliant.

Evidence

  • The root user's Security credentials page, listing only hardware devices
  • The root-account-hardware-mfa-enabled rule, showing compliant, and Security Hub CSPM control IAM.6 showing passed

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.