---
title: "NIST 800-171 3.13.11 (SC.L2-3.13.11): FIPS Cryptography"
description: "NIST SP 800-171 3.13.11 FIPS Cryptography: 3 or 5 SPRS points, on a CMMC POA&M only if not FIPS validated. The text, what assessors check and the evidence."
url: https://policycortex.com/nist-800-171/system-and-communications-protection/3.13.11
sealed: 2026-11-11
amended: 2026-11-11
register: nist-800-171/system-and-communications-protection/3.13.11
records: 7
digest: sha3:1238729371b8bc020b89d7ceeb7b2aa3e6e31e034712f8d67ad167a7d7b74ee9
---

# NIST 800-171 3.13.11 (SC.L2-3.13.11): FIPS Cryptography

NIST 800-171 / System and Communications Protection / 3.13.11

"Employ FIPS-validated cryptography when used to protect the confidentiality of CUI." ([NIST SP 800-171 Rev. 2, requirement 3.13.11](https://doi.org/10.6028/NIST.SP.800-171r2))

CMMC Level 2 practice SC.L2-3.13.11.

## What 3.13.11 means in practice

When cryptography protects CUI, the module doing the work must be FIPS validated, meaning it has a certificate from NIST's Cryptographic Module Validation Program. Strong algorithms alone are not enough: confirm that the validated module is the one actually running, which often means turning on FIPS mode.

## SPRS points and the CMMC POA&M

- **CMMC Level 2 practice**: SC.L2-3.13.11
- **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**: Only when CUI is encrypted but not with FIPS-validated cryptography: scored Partial, it is worth 3 points, and 32 CFR 170.21(a)(2)(ii) makes that case the one exception to the 1-point rule. Without encryption it is worth 5 points and cannot go on a POA&M.
- **Scoring note**: Partial: CUI is encrypted, but not with a FIPS-validated module. It loses 3 points instead of 5. Isolated non-validated use covered by a plan of action counts as Met.

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

NIST SP 800-171A gives one determination statement for 3.13.11.

- Determine if FIPS-validated cryptography is employed to protect the confidentiality of CUI.

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

## Evidence that shows 3.13.11 is met

- A list of the places where cryptography protects CUI and the module used at each.
- The CMVP certificate numbers for those modules.
- Configuration showing FIPS mode turned on where a product needs it.

## How PolicyCortex gathers the evidence

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

- **Azure Policy: Assignments.** Checks that an Azure Policy assignment enforces FIPS-validated cryptography.

## Related pages

- **Calculator**: [SPRS score calculator: mark 3.13.11 and the other 109 requirements and see the score.](https://policycortex.com/sprs-score-calculator#family-SC)
- **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 16 System and Communications Protection requirements (3.13).](https://policycortex.com/nist-800-171/system-and-communications-protection)
- **Previous**: [3.13.10: Key Management](https://policycortex.com/nist-800-171/system-and-communications-protection/3.13.10)
- **Next**: [3.13.12: Collaborative Devices](https://policycortex.com/nist-800-171/system-and-communications-protection/3.13.12)
- **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 | 37b051de6c9f | 7e29e001a465 |
| REC 0001 | MEANING | f12c26649289 | 37b051de6c9f |
| REC 0002 | POINTS AND POA&M | 95423d1541ab | f12c26649289 |
| REC 0003 | ASSESSMENT OBJECTIVES | c039c56a3b98 | 95423d1541ab |
| REC 0004 | EVIDENCE | f6c39777a3f2 | c039c56a3b98 |
| REC 0005 | COLLECTORS | 010bff50fb4f | f6c39777a3f2 |
| REC 0006 | RELATED | 1238729371b8 | 010bff50fb4f |

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