---
title: "NIST 800-171 3.5.7 (IA.L2-3.5.7): Password Complexity"
description: "NIST SP 800-171 3.5.7 Password Complexity: 1 SPRS point, 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.7
sealed: 2026-11-11
amended: 2026-11-11
register: nist-800-171/identification-and-authentication/3.5.7
records: 7
digest: sha3:dbafec170e5daf2c62ef9477a705368302b083aee5879021d40971bf7960c6ea
---

# NIST 800-171 3.5.7 (IA.L2-3.5.7): Password Complexity

NIST 800-171 / Identification and Authentication / 3.5.7

"Enforce a minimum password complexity and change of characters when new passwords are created." ([NIST SP 800-171 Rev. 2, requirement 3.5.7](https://doi.org/10.6028/NIST.SP.800-171r2))

CMMC Level 2 practice IA.L2-3.5.7.

## What 3.5.7 means in practice

Passwords meet a defined minimum length and complexity, and a new password differs from the old one by a defined number of characters. Write the rules down and set them wherever passwords are created: the identity provider, local accounts, and applications with their own logins.

## SPRS points and the CMMC POA&M

- **CMMC Level 2 practice**: IA.L2-3.5.7
- **SPRS points**: 1 point. When it is not met, the DoD Assessment Methodology subtracts 1 from the score of 110.
- **CMMC POA&M**: Allowed. It is worth 1 point, and 32 CFR 170.21(a)(2)(ii) admits requirements worth 1 point. Conditional status also needs a score of at least 88, and the item must be closed within 180 days.

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.7

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

- 3.5.7[a] password complexity requirements are defined.
- 3.5.7[b] password change of character requirements are defined.
- 3.5.7[c] minimum password complexity requirements as defined are enforced when new passwords are created.
- 3.5.7[d] minimum password change of character requirements as defined are enforced when new passwords are created.

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

## Evidence that shows 3.5.7 is met

- The written password rules: length, complexity and number of changed characters.
- Identity provider and directory password policy settings.
- Password settings for local accounts and for applications with their own credentials.

## How PolicyCortex gathers the evidence

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

- **Okta: Policies.** Checks that every active Okta password policy requires at least 14 characters, with lowercase, uppercase, number and symbol characters.
- **AWS: IAM.** Checks the AWS account password policy against a baseline that starts at 14 characters.

## Related pages

- **Calculator**: [SPRS score calculator: mark 3.5.7 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.6: Inactive Accounts](https://policycortex.com/nist-800-171/identification-and-authentication/3.5.6)
- **Next**: [3.5.8: Password Reuse](https://policycortex.com/nist-800-171/identification-and-authentication/3.5.8)
- **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 | 205ee4b4aaa5 | 41b97a464198 |
| REC 0001 | MEANING | 2082b6198a59 | 205ee4b4aaa5 |
| REC 0002 | POINTS AND POA&M | 24ea35c19298 | 2082b6198a59 |
| REC 0003 | ASSESSMENT OBJECTIVES | 4bda7d2bad35 | 24ea35c19298 |
| REC 0004 | EVIDENCE | 77539fd328bc | 4bda7d2bad35 |
| REC 0005 | COLLECTORS | 512444e07a87 | 77539fd328bc |
| REC 0006 | RELATED | dbafec170e5d | 512444e07a87 |

Head sha3:dbafec170e5daf2c62ef9477a705368302b083aee5879021d40971bf7960c6ea. 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.
