What evidence do auditors commonly ask for on SC.L2-3.13.5 Public-Access System Separation?

Network diagram showing the separated subnetwork for public components; Firewall or routing configuration enforcing the separation; Inventory of publicly accessible components.

What is the most common gap auditors find on SC.L2-3.13.5?

Public facing servers residing on internal networks

CMMC 2.0 · System and Communications Protection

`SC.L2-3.13.5` Public-Access System Separation

Place publicly accessible system components on subnetworks that are physically or logically separated from internal networks.

Source: CMMC 2.0, SC.L2-3.13.5. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open CMMC 2.0 in the compliance library.

artefacts

held by a system

at each review

moderate

to go live

Cloud console / configuration management

where the evidence lives

teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

Firewall or routing configuration enforcing the separation · Cloud console / configuration management

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

Network diagram showing the separated subnetwork for public components · Policy repository / GRC workspace
Inventory of publicly accessible components · Policy repository / GRC workspace

First move

Start with the 1 of 3 artefacts that already live in a system (Cloud console / configuration management); keep the periodic reviews but log each one as a dated record with a named reviewer.

Common gaps auditors find

Public facing servers residing on internal networks
Separation exists but permissive rules allow broad internal access
New public services deployed outside the segmented zone

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

SC.L2-3.13.4 Shared Resource Control · SC.L2-3.13.6 Network Communication by Exception