NIST 800-171 3.5.3Use multifactor authentication for local and network access to privileged accounts and for network access to non-privileged accounts
Overview
This control requires organizations to use multifactor authentication for local and network access to privileged accounts and for network access to non-privileged accounts. It is part of the Identification and Authentication family and is required for CMMC Level 2 certification. Defense contractors handling CUI must implement this control to protect sensitive information and demonstrate compliance during assessments.
Assessment Objectives
- 1Determine if the organization has defined policies and procedures to use multifactor authentication for local and network access to privileged accounts and for network access to non-privileged accounts
- 2Determine if the organization implements mechanisms to use multifactor authentication for local and network access to privileged accounts and for network access to non-privileged accounts
- 3Verify that the implementation is consistent with organizational policies and NIST 800-171 requirements
Implementation Guidance
Implement this control by establishing documented policies and procedures, deploying appropriate technical controls, and maintaining evidence of ongoing compliance. Regularly review and test the implementation to ensure effectiveness and address any gaps identified during assessments.
Common Audit Gaps
Related DFARS Clauses
Frequently Asked Questions
What is NIST 800-171 control 3.5.3?
NIST 800-171 control 3.5.3 requires organizations to use multifactor authentication for local and network access to privileged accounts and for network access to non-privileged accounts. This control is part of the Identification and Authentication family and is required for CMMC Level 2 certification.
How do you implement NIST 800-171 3.5.3?
To implement control 3.5.3, establish documented policies, deploy technical controls to use multifactor authentication for local and network access to privileged accoun, and maintain evidence of compliance. Regular testing and monitoring are essential.
What evidence is needed for NIST 800-171 3.5.3?
Evidence for control 3.5.3 typically includes written policies and procedures, system configuration documentation, audit logs showing enforcement, and records of periodic reviews. Assessors will look for both documentation and technical implementation.
Related Controls
3.5.2|Authenticate (or verify) the identities of users, processes, or devices, as a prerequisite to allowing access to organizational systems
Identification and Authentication
3.5.4|Employ replay-resistant authentication mechanisms for network access to privileged and non-privileged accounts
Identification and Authentication
3.1.1|Limit system access to authorized users, processes acting on behalf of authorized users, and devices
Access Control
More in Identification and Authentication
Related Guides
Check your compliance for NIST 800-171 3.5.3
Cabrillo Club automates evidence collection and audit readiness across all 110 NIST 800-171 controls.
Join Free