---
title: "NIST 800-171 3.13.10 (SC.L2-3.13.10): Key Management"
description: "NIST SP 800-171 3.13.10 Key Management: 1 SPRS point, allowed on a CMMC POA&M. The text, what assessors check and the evidence."
url: https://policycortex.com/nist-800-171/system-and-communications-protection/3.13.10
sealed: 2026-11-11
amended: 2026-11-11
register: nist-800-171/system-and-communications-protection/3.13.10
records: 7
digest: sha3:6ab24119dc6dd928fce0658766356a8672b350760b6ce95fa6f87d19f65d66bb
---

# NIST 800-171 3.13.10 (SC.L2-3.13.10): Key Management

NIST 800-171 / System and Communications Protection / 3.13.10

"Establish and manage cryptographic keys for cryptography employed in organizational systems." ([NIST SP 800-171 Rev. 2, requirement 3.13.10](https://doi.org/10.6028/NIST.SP.800-171r2))

CMMC Level 2 practice SC.L2-3.13.10.

## What 3.13.10 means in practice

Wherever cryptography is used, its keys are created, stored, distributed, rotated and destroyed under control: who can use them, where they are kept and how long they live. A key vault or hardware security module, and a written key management procedure, are the usual evidence.

## SPRS points and the CMMC POA&M

- **CMMC Level 2 practice**: SC.L2-3.13.10
- **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.13.10

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

- 3.13.10[a] cryptographic keys are established whenever cryptography is employed.
- 3.13.10[b] cryptographic keys are managed whenever cryptography is employed.

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

## Evidence that shows 3.13.10 is met

- The key management procedure, covering creation, rotation and destruction.
- Key vault configuration: access permissions, deletion protection and rotation policies.
- Records of key rotation and certificate renewal.

## How PolicyCortex gathers the evidence

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

- **Azure Key Vault: Key vaults; Azure: Role assignments.** Reads each Azure Key Vault and the role assignments that reach it, and checks that soft delete and purge protection are on and that access to keys follows least privilege through Azure RBAC.
- **Azure Policy: Compliance state.** Reads Azure Policy's verdicts on Key Vault keys and secrets: rotation policies configured and expiration dates set.

## Related pages

- **Calculator**: [SPRS score calculator: mark 3.13.10 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.9: Connection Termination](https://policycortex.com/nist-800-171/system-and-communications-protection/3.13.9)
- **Next**: [3.13.11: FIPS Cryptography](https://policycortex.com/nist-800-171/system-and-communications-protection/3.13.11)
- **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 | cde163f5ab11 | 539452336738 |
| REC 0001 | MEANING | d844be0cadf3 | cde163f5ab11 |
| REC 0002 | POINTS AND POA&M | 09823412613d | d844be0cadf3 |
| REC 0003 | ASSESSMENT OBJECTIVES | 32b8bd3b8612 | 09823412613d |
| REC 0004 | EVIDENCE | 454eef90149c | 32b8bd3b8612 |
| REC 0005 | COLLECTORS | 55f3274e4af8 | 454eef90149c |
| REC 0006 | RELATED | 6ab24119dc6d | 55f3274e4af8 |

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