NIST 800-53 REV 5 • IDENTIFICATION AND AUTHENTICATION

IA-2(1)Multi-factor Authentication to Privileged Accounts

Implement multi-factor authentication for access to privileged accounts.

CMMC Practice Mapping

NIST 800-171 Mapping

Related Controls

Supplemental Guidance

Multi-factor authentication requires the use of two or more different factors to achieve authentication. The authentication factors are defined as follows: something you know (e.g., a personal identification number [PIN]), something you have (e.g., a physical authenticator such as a cryptographic private key), or something you are (e.g., a biometric). Multi-factor authentication solutions that feature physical authenticators include hardware authenticators that provide time-based or challenge-response outputs and smart cards such as the U.S. Government Personal Identity Verification (PIV) card or the Department of Defense (DoD) Common Access Card (CAC). In addition to authenticating users at the system level (i.e., at logon), organizations may employ authentication mechanisms at the application level, at their discretion, to provide increased security. Regardless of the type of access (i.e., local, network, remote), privileged accounts are authenticated using multi-factor options appropriate for the level of risk. Organizations can add additional security measures, such as additional or more rigorous authentication mechanisms, for specific types of access.

Practitioner Notes

This enhancement requires multi-factor authentication (MFA) for privileged accounts — admin accounts must use more than just a password to log in.

Example 1: Enable Azure AD Conditional Access policies that require MFA (Microsoft Authenticator app) for all Global Admin, Security Admin, and other privileged roles.

Example 2: Configure your CyberArk or Azure PIM to require MFA every time an administrator activates a privileged role, even from trusted network locations.