---
title: "NIST 800-171 3.5.3 (IA.L2-3.5.3): Multifactor Authentication"
description: "NIST SP 800-171 3.5.3 Multifactor Authentication: 3 or 5 SPRS points, not allowed on a CMMC POA&M. The text, what assessors check and the evidence."
url: https://policycortex.com/nist-800-171/identification-and-authentication/3.5.3
sealed: 2026-11-11
amended: 2026-11-11
register: nist-800-171/identification-and-authentication/3.5.3
records: 7
digest: sha3:bf7b4a7406322749ba50489778f91243ea37ef01a69fa1f2d6b43eb9580a6ed1
---

# NIST 800-171 3.5.3 (IA.L2-3.5.3): Multifactor Authentication

NIST 800-171 / Identification and Authentication / 3.5.3

"Use multifactor authentication for local and network access to privileged accounts and for network access to non-privileged accounts." ([NIST SP 800-171 Rev. 2, requirement 3.5.3](https://doi.org/10.6028/NIST.SP.800-171r2))

CMMC Level 2 practice IA.L2-3.5.3.

## What 3.5.3 means in practice

Privileged accounts need multifactor authentication for every sign-in, including at the console, and everyone needs it for network sign-ins. Assessors start from the list of privileged accounts and then look for the gaps: local administrator logons, legacy protocols that skip the second factor, and accounts left out of the multifactor policy.

## SPRS points and the CMMC POA&M

- **CMMC Level 2 practice**: IA.L2-3.5.3
- **SPRS points**: 5 points, or 3 with partial credit. Not met subtracts 5 from the score of 110; partially met subtracts 3.
- **CMMC POA&M**: Not allowed. It is worth 5 points, or 3 with partial credit, and 32 CFR 170.21(a)(2)(ii) admits only requirements worth 1 point, with one exception: 3.13.11 when encryption is used but not FIPS validated.
- **Scoring note**: Partial: multifactor authentication covers remote and privileged users but not general users. It loses 3 points instead of 5.

Sources: [NIST SP 800-171 DoD Assessment Methodology, version 1.2.1 (June 24, 2020), Annex A](https://www.acq.osd.mil/asda/dpc/cp/cyber/docs/safeguarding/NIST-SP-800-171-Assessment-Methodology-Version-1.2.1-6.24.2020.pdf); [32 CFR 170.21, Plan of Action and Milestones requirements](https://www.ecfr.gov/current/title-32/section-170.21).

## What an assessor checks for 3.5.3

NIST SP 800-171A gives 4 determination statements for 3.5.3, each found satisfied or other than satisfied. Determine if:

- 3.5.3[a] privileged accounts are identified.
- 3.5.3[b] multifactor authentication is implemented for local access to privileged accounts.
- 3.5.3[c] multifactor authentication is implemented for network access to privileged accounts.
- 3.5.3[d] multifactor authentication is implemented for network access to non-privileged accounts.

[NIST SP 800-171A (June 2018), assessment objectives for 3.5.3](https://doi.org/10.6028/NIST.SP.800-171A)

## Evidence that shows 3.5.3 is met

- The list of privileged accounts.
- Identity provider policies requiring multifactor authentication for all users and all applications, with any exclusions explained.
- How administrators' local logons to servers require a second factor.
- Sign-in logs showing multifactor authentication satisfied.

## How PolicyCortex gathers the evidence

PolicyCortex reads this evidence with the collectors below, read only, and grades 3.5.3 from it. Each line says what the product checks.

- **Microsoft Entra ID: Conditional Access.** Checks that Conditional Access requires multifactor authentication of every administrator role and of everyone who signs in to Azure management, and of all users on all cloud applications.
- **Okta: Policies · Directory.** Checks that Okta requires a second factor at every sign-in and that every user and every administrator has one enrolled.
- **AWS: IAM.** Checks that IAM console users and the root account have an MFA device.

## Related pages

- **Calculator**: [SPRS score calculator: mark 3.5.3 and the other 109 requirements and see the score.](https://policycortex.com/sprs-score-calculator#family-IA)
- **Sample package**: [Sample package: an SSP, a POA&M and an evidence chain the product generated from demonstration data.](https://policycortex.com/sample-package)
- **Family**: [All 11 Identification and Authentication requirements (3.5).](https://policycortex.com/nist-800-171/identification-and-authentication)
- **Previous**: [3.5.2: Authentication](https://policycortex.com/nist-800-171/identification-and-authentication/3.5.2)
- **Next**: [3.5.4: Replay Resistance](https://policycortex.com/nist-800-171/identification-and-authentication/3.5.4)
- **All requirements**: [All 110 NIST SP 800-171 requirements, by family.](https://policycortex.com/nist-800-171)

Meet the requirement once. Keep the evidence current. [Request Access](https://app.policycortex.com/auth?mode=request-access) · [Book a call](https://policycortex.com/book)

## Register colophon

| Seq | Label | SHA3-256 | Prev |
|---|---|---|---|
| REC 0000 | REQUIREMENT | fc468877299e | 950d7c02dee2 |
| REC 0001 | MEANING | 2bd7ac227b0e | fc468877299e |
| REC 0002 | POINTS AND POA&M | 7f83e4d7af46 | 2bd7ac227b0e |
| REC 0003 | ASSESSMENT OBJECTIVES | 6ce8fe7b2960 | 7f83e4d7af46 |
| REC 0004 | EVIDENCE | 601d01492647 | 6ce8fe7b2960 |
| REC 0005 | COLLECTORS | fd63929f4d1a | 601d01492647 |
| REC 0006 | RELATED | bf7b4a740632 | fd63929f4d1a |

Head sha3:bf7b4a7406322749ba50489778f91243ea37ef01a69fa1f2d6b43eb9580a6ed1. Each digest is SHA3-256 over the previous digest, the register key, the record label, and the record copy; a second party can recompute it from this document.