NIST SP 800-171 Rev. 3 3.5.3 — Multi-Factor Authentication

What this control requires

This control mandates the implementation of multi-factor authentication (MFA) for both privileged and non-privileged accounts. MFA requires the use of at least two distinct authentication factors, such as something the user knows (PIN), has (physical authenticator), or is (biometric). MFA can be applied at both the system and application levels to enhance security. This control supports the Multi-Factor Authentication capability within the Identification and Authentication (3.5) family.

In plain English

This control mandates the implementation of multi-factor authentication (MFA) for both privileged and non-privileged accounts. In practice, this means you can prove you access management-level controls on a defined cadence.

Why it matters

DoD contractors and their subcontractors must implement all 100 SP 800-171 requirements to keep CUI handling contracts. Gaps are scored against the SPRS scoring methodology; below a 110-point starting score, each unmet requirement deducts points and a below-threshold score can disqualify a bid.

This control is rated critical in the source catalogue. Treat gaps here as production incidents in the risk register, not housekeeping.

What an auditor looks for

A C3PAO conducting a CMMC Level 2 assessment uses NIST SP 800-171A objectives. They expect a System Security Plan (SSP), Plan of Action & Milestones (POA&M) for any gaps, and objective evidence (configurations, ticket records, training records) for every requirement.

Within Identification and Authentication, the assessor will trace your implementation back to the catalogue reference (Requirement 3.5.3) and look for objective evidence on the latest two assessment cycles.

How to implement

1. Write a short policy stating intent, scope and named owner.
2. Encode it as a platform guardrail — SCP, Azure Policy initiative, Organisation Policy, or repository policy.
3. Wire a monitoring signal that catches drift (CSPM rule, SIEM rule, scheduled query, Workspace alert) and ticket it.
4. Review on a documented cadence and capture the review in the risk register or compliance tracker.

Operational checklist

• Access. Document the trigger, the owner and the cadence.
• Least. Document the trigger, the owner and the cadence.
• System. Document the trigger, the owner and the cadence.
• Multi-Factor. Document the trigger, the owner and the cadence.
• Authentication. Document the trigger, the owner and the cadence.
• Scope: management, authentication, pin, physical authenticator, biometric, security.

Evidence to collect

• Identity Scan. IAM / IdP exports — Entra ID, Okta, IAM Identity Center, Workspace directory — showing accounts, roles, MFA state and last sign-in.

Identity analytics (Okta, SailPoint, Access Analyzer) demonstrates least-privilege. Focus: Multi-Factor Authentication.

How it maps to other frameworks

Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit.

• NIST SP 800-53 Rev. 5 IA-2(1) — Multi-Factor Authentication To Privileged Accounts
• ISO/IEC 27001:2022 A.5.2 — Information security roles and responsibilities
• SOC 2 (2017 TSC) CC6.2 — Access Provisioning
• CIS Controls v8 14.9 — Conduct Role-Specific Security Awareness and Skills Training
• BSI C5:2020 PSS-05 — Authentication Mechanisms

Related controls in NIST SP 800-171 Rev. 3

• Requirement 3.5.5 — Identifier Management
• Requirement 3.5.1 — User Identification and Authentication
• Requirement 3.5.4 — Replay-Resistant Authentication
• Requirement 3.5.7 — Password Management
• Requirement 3.9.1 — Personnel Screening
• Requirement 3.3.1 — Event Logging

References

• NIST Computer Security Resource Center — NIST SP 800-171 Rev. 3
• Catalogue identifier: Requirement 3.5.3

Topics: identity accessprivileged accessidentity managementaccess reviewmulti factor auth