What 3.13.5 means in practice

Anything the public can reach, such as a web server or a file transfer service, sits in its own subnetwork (often called a DMZ), physically or logically separated from internal networks, with rules that limit what can cross between them. In a cloud environment that usually means a separate subnet or virtual network for public endpoints, with rules that let only the needed traffic in.

SPRS points and the CMMC POA&M

CMMC Level 2 practice
SC.L2-3.13.5
SPRS points
5 points. When it is not met, the DoD Assessment Methodology subtracts 5 from the score of 110.
CMMC POA&M
Not allowed. It is worth 5 points, 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.

Sources: NIST SP 800-171 DoD Assessment Methodology, version 1.2.1 (June 24, 2020), Annex A; 32 CFR 170.21, Plan of Action and Milestones requirements.

What an assessor checks for 3.13.5

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

  1. 3.13.5[a] publicly accessible system components are identified.
  2. 3.13.5[b] subnetworks for publicly accessible system components are physically or logically separated from internal networks.

NIST SP 800-171A (June 2018), assessment objectives for 3.13.5

Evidence that shows 3.13.5 is met

  • A list of publicly accessible system components.
  • A network diagram showing the separate subnetwork that holds them.
  • Firewall or network rules between that subnetwork and the internal networks.

How PolicyCortex gathers the evidence

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

  • Azure: Virtual networks. Reads Azure virtual networks and checks that workloads are segmented into separate subnets.

Meet the requirement once. Keep the evidence current.

Published
Last updated
Unchanged since publication