---
title: "NIST 800-171 3.13.3 (SC.L2-3.13.3): Management Separation"
description: "NIST SP 800-171 3.13.3 Management Separation: 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.3
sealed: 2026-11-11
amended: 2026-11-11
register: nist-800-171/system-and-communications-protection/3.13.3
records: 7
digest: sha3:c65e1baff544a924087eb28954d43395ba60eacb66de4617254c86d9ac35790f
---

# NIST 800-171 3.13.3 (SC.L2-3.13.3): Management Separation

NIST 800-171 / System and Communications Protection / 3.13.3

"Separate user functionality from system management functionality." ([NIST SP 800-171 Rev. 2, requirement 3.13.3](https://doi.org/10.6028/NIST.SP.800-171r2))

CMMC Level 2 practice SC.L2-3.13.3.

## What 3.13.3 means in practice

Keep the functions ordinary users work with apart from the functions used to manage the system. Administration typically happens through separate interfaces, accounts, networks or hosts, so a compromised user session does not lead straight to management access.

## SPRS points and the CMMC POA&M

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

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

- 3.13.3[a] user functionality is identified.
- 3.13.3[b] system management functionality is identified.
- 3.13.3[c] user functionality is separated from system management functionality.

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

## Evidence that shows 3.13.3 is met

- A description of how user functions and management functions are separated.
- Network or host configuration placing management interfaces on separate networks or hosts.
- Firewall rules restricting management ports to administrative networks.

## How PolicyCortex gathers the evidence

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

- **Azure: Network security groups.** Checks that network security group rules keep management ports (RDP and SSH) closed to the internet.

## Related pages

- **Calculator**: [SPRS score calculator: mark 3.13.3 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.2: Security Engineering](https://policycortex.com/nist-800-171/system-and-communications-protection/3.13.2)
- **Next**: [3.13.4: Shared Resources](https://policycortex.com/nist-800-171/system-and-communications-protection/3.13.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 | f3d23d3126bd | f007d6d3ee9f |
| REC 0001 | MEANING | d25a3f7bff70 | f3d23d3126bd |
| REC 0002 | POINTS AND POA&M | 2abf821915cf | d25a3f7bff70 |
| REC 0003 | ASSESSMENT OBJECTIVES | 5e32fc336acc | 2abf821915cf |
| REC 0004 | EVIDENCE | d6bfcfe2bc08 | 5e32fc336acc |
| REC 0005 | COLLECTORS | 9a1a7e0038f4 | d6bfcfe2bc08 |
| REC 0006 | RELATED | c65e1baff544 | 9a1a7e0038f4 |

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