Skip to main content

🛡️ AWS Account Root User Hardware MFA is not enabled.🟢⚪

Similar Policies​

Description​

Open File

Description​

The root user 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 user account be protected with a hardware MFA.

Rationale​

A hardware MFA has a smaller attack surface than a virtual MFA. For example, a hardware MFA does not suffer the attack surface introduced by the mobile smartphone on which a virtual MFA resides.

Note: Using hardware MFA for many, many AWS accounts may create a logistical device management issue. If this is the case, consider implementing this Level 2 recommendation selectively to the highest security AWS accounts and the Level 1 recommendation applied to the remaining accounts.

Audit​

Perform the following to determine if the root user account has a hardware MFA setup:

  1. Run the following command to determine if the root account has MFA setup:

... see more

Remediation​

Open File

Remediation​

Note: To manage MFA devices for the AWS root user account, you must use your root account credentials to sign in to AWS. You cannot manage MFA devices for the root account using other credentials. Perform the following to establish a hardware MFA for the root user account:

Perform the following to establish a hardware MFA for the root user account:

  1. Sign in to the AWS Management Console and open the IAM console at https://console.aws.amazon.com/iam/.
  2. Choose Dashboard , and under Security Status , expand Activate MFA on your root account.
  3. Choose Activate MFA.
  4. In the wizard, choose A hardware MFA device and then choose Next Step.
  5. In the Serial Number box, enter the serial number that is found on the back of the MFA device.
  6. In the Authentication Code 1 box, enter the six-digit number displayed by the MFA device. You might need to press the button on the front of the device to display the number.
  7. Wait 30 seconds while the device refreshes the code, and then enter the next six-digit number into the Authentication Code 2 box. You might need to press the button on the front of the device again to display the second number.

... see more

policy.yaml​

Open File

Linked Framework Sections​

SectionSub SectionsInternal RulesPoliciesFlagsCompliance
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [IAM.6] Hardware MFA should be enabled for the root user1no data
💼 AWS Well-Architected → 💼 SEC02-BP01 Use strong sign-in mechanisms3no data
💼 CIS AWS v1.2.0 → 💼 1.14 Ensure hardware MFA is enabled for the "root" account1no data
💼 CIS AWS v1.3.0 → 💼 1.6 Ensure hardware MFA is enabled for the "root user" account1no data
💼 CIS AWS v1.4.0 → 💼 1.6 Ensure hardware MFA is enabled for the 'root' user account1no data
💼 CIS AWS v1.5.0 → 💼 1.6 Ensure hardware MFA is enabled for the 'root' user account - Level 2 (Automated)1no data
💼 CIS AWS v2.0.0 → 💼 1.6 Ensure hardware MFA is enabled for the 'root' user account - Level 2 (Manual)1no data
💼 CIS AWS v3.0.0 → 💼 1.6 Ensure hardware MFA is enabled for the 'root' user account - Level 2 (Manual)1no data
💼 CIS AWS v4.0.0 → 💼 1.6 Ensure hardware MFA is enabled for the 'root' user account (Manual)1no data
💼 CIS AWS v4.0.1 → 💼 1.6 Ensure hardware MFA is enabled for the 'root' user account (Manual)1no data
💼 CIS AWS v5.0.0 → 💼 1.5 Ensure hardware MFA is enabled for the 'root' user account (Manual)1no data
💼 CIS AWS v6.0.0 → 💼 2.5 Ensure hardware MFA is enabled for the 'root' user account (Manual)1no data
💼 Cloudaware Framework → 💼 Multi-Factor Authentication (MFA) Implementation16no data
💼 FedRAMP High Security Controls → 💼 AC-2(1) Automated System Account Management (M)(H)18no data
💼 FedRAMP High Security Controls → 💼 IA-2(1) Multi-factor Authentication to Privileged Accounts (L)(M)(H)3no data
💼 FedRAMP High Security Controls → 💼 IA-2(2) Multi-factor Authentication to Non-privileged Accounts (L)(M)(H)3no data
💼 FedRAMP High Security Controls → 💼 IA-2(6) Access to Accounts —separate Device (M)(H)3no data
💼 FedRAMP High Security Controls → 💼 IA-2(8) Access to Accounts — Replay Resistant (L)(M)(H)3no data
💼 FedRAMP Low Security Controls → 💼 IA-2(1) Multi-factor Authentication to Privileged Accounts (L)(M)(H)3no data
💼 FedRAMP Low Security Controls → 💼 IA-2(2) Multi-factor Authentication to Non-privileged Accounts (L)(M)(H)3no data
💼 FedRAMP Low Security Controls → 💼 IA-2(8) Access to Accounts — Replay Resistant (L)(M)(H)3no data
💼 FedRAMP Moderate Security Controls → 💼 AC-2(1) Automated System Account Management (M)(H)18no data
💼 FedRAMP Moderate Security Controls → 💼 IA-2(1) Multi-factor Authentication to Privileged Accounts (L)(M)(H)3no data
💼 FedRAMP Moderate Security Controls → 💼 IA-2(2) Multi-factor Authentication to Non-privileged Accounts (L)(M)(H)3no data
💼 FedRAMP Moderate Security Controls → 💼 IA-2(6) Access to Accounts —separate Device (M)(H)3no data
💼 FedRAMP Moderate Security Controls → 💼 IA-2(8) Access to Accounts — Replay Resistant (L)(M)(H)3no data
💼 NIST SP 800-53 Revision 5 → 💼 AC-2(1) Account Management _ Automated System Account Management418no data
💼 NIST SP 800-53 Revision 5 → 💼 AC-3(15) Access Enforcement _ Discretionary and Mandatory Access Control13no data
💼 NIST SP 800-53 Revision 5 → 💼 IA-2(1) Identification and Authentication (organizational Users) _ Multi-factor Authentication to Privileged Accounts3no data
💼 NIST SP 800-53 Revision 5 → 💼 IA-2(2) Identification and Authentication (organizational Users) _ Multi-factor Authentication to Non-privileged Accounts3no data
💼 NIST SP 800-53 Revision 5 → 💼 IA-2(6) Identification and Authentication (organizational Users) _ Access to Accounts —separate Device3no data
💼 NIST SP 800-53 Revision 5 → 💼 IA-2(8) Identification and Authentication (organizational Users) _ Access to Accounts — Replay Resistant3no data
💼 PCI DSS v3.2.1 → 💼 8.3.1 Incorporate multi-factor authentication for all non-console access into the CDE for personnel with administrative access.3no data
💼 PCI DSS v4.0.1 → 💼 8.4.1 MFA is implemented for all non-console access into the CDE for personnel with administrative access.3no data
💼 PCI DSS v4.0.1 → 💼 8.4.2 MFA is implemented for all non-console access into the CDE.3no data
💼 PCI DSS v4.0 → 💼 8.4.1 MFA is implemented for all non-console access into the CDE for personnel with administrative access.13no data
💼 PCI DSS v4.0 → 💼 8.4.2 MFA is implemented for all access into the CDE.13no data