| name | IA-2(2)_multi-factor-authentication-to-non-privileged-accounts |
| description | Implement multi-factor authentication for access to non-privileged accounts. |
| category | authentication |
| version | 5.2.0 |
| author | cyberstrike-official |
| tags | ["nist","sp800-53","rev5","ia-2-2","ia","enhancement"] |
| tech_stack | ["aws","azure","active-directory","linux","windows"] |
| cwe_ids | ["CWE-287"] |
| chains_with | ["AC-5"] |
| prerequisites | ["IA-2"] |
| severity_boost | {"AC-5":"Chain with AC-5 for comprehensive security coverage"} |
IA-2(2) Multi-factor Authentication to Non-privileged Accounts
Enhancement of: IA-2
High-Level Description
Family: Identification and Authentication (IA)
Framework: NIST SP 800-53 Rev 5
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 card or the DoD Common Access Card. In addition to authenticating users at the system level, organizations may also employ authentication mechanisms at the application level, at their discretion, to provide increased information security. Regardless of the type of access (i.e., local, network, remote), non-privileged accounts are authenticated using multi-factor options appropriate for the level of risk. Organizations can provide additional security measures, such as additional or more rigorous authentication mechanisms, for specific types of access.
What to Check
How to Test
Step 1: Review Documentation
Examine the System Security Plan (SSP) and related artifacts for IA-2(2) implementation details. Verify the organization has documented how this control is satisfied.
Step 2: Validate Implementation
# For cloud environments, use cloud-audit-mcp tools
# For on-premises, review system configurations directly
# Example: Check if account management policies exist
grep -r "account.management\|access.control" /etc/security/ 2>/dev/null
Step 3: Test Operating Effectiveness
Verify the control is actively functioning, not just documented. Check logs, configurations, and operational evidence.
Tools
