CIS Amazon Web Services Foundations Benchmark v1.2.0/Identity and Access Management/2 of 49
1.2Ensure multi-factor authentication (MFA) is enabled for all IAM users that have a console password
Control family: Identity and Access Management
Control description
Multi-Factor Authentication (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. It is recommended that MFA be enabled for all accounts that have a console password.
How to implement
ResponsibilityCustomerYou configure and operate this in your own cloud accounts.
Any IAM user that can sign in to the console with a password also needs a second factor, so a leaked or guessed password alone can't open the account. Users created for programs only, with no console password, aren't in scope. Where people can move to IAM Identity Center, the IAM user can often be removed altogether.
Before you start
The same on every cloud, before the steps in the tabs.
- Decide which MFA methods are allowed for console users (security keys or passkeys preferred, especially for administrators) and how a lost device is replaced.
- Make MFA part of onboarding, so a new console user registers a device before being given any permissions.
Evidence
- The MFA standard and the onboarding checklist that includes it
Not applicable. This benchmark covers AWS only.
On AWS the tasks find the console users without MFA from the credential report, give each one an MFA device, and add the AWS Config rule that keeps watching for new gaps.
Task 1Find console users without MFA
- Sign in to the AWS Management Console at console.aws.amazon.com and open IAM.
- Choose Credential report and then Download Report.
- Filter the rows where password_enabled is true and mfa_active is false.
- Note each of those users and who owns them; that list is the work for the next task.
Task 2Assign an MFA device to each console user
- In IAM, choose Users and open a user from the list.
- Choose the Security credentials tab and, under Multi-factor authentication (MFA), choose Assign MFA device.
- Enter a Device name and pick Passkey or security key, Authenticator app or Hardware TOTP token, then choose Next.
- Complete the registration with the user present (touch the key, or enter two consecutive codes from the app).
- Repeat for every user on the list.
- Check it: download a new credential report and confirm mfa_active is true wherever password_enabled is true.
Task 3Keep it checked with the AWS Config rule mfa-enabled-for-iam-console-access
- 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 mfa-enabled-for-iam-console-access, select it and choose Next.
- On Configure rule, keep the name and leave the evaluation settings as they are, 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; open the rule to see any resource that fails.
Evidence
- The credential report, with mfa_active true for every user whose password_enabled is true
- The mfa-enabled-for-iam-console-access rule in AWS Config, showing all users compliant
- Security Hub CSPM control IAM.5 in the CIS AWS Foundations Benchmark v1.2.0 standard, 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.