What evidence do auditors commonly ask for on SC.L2-3.13.1 Boundary Protection?

Network architecture identifying external and key internal boundaries; Boundary device configuration such as firewall and gateway rulesets; Monitoring evidence at those boundaries.

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

External boundary protected while internal boundaries are flat

CMMC 2.0 · System and Communications Protection

`SC.L2-3.13.1` Boundary Protection

Monitor, control and protect communications at the external boundary of the system and at key internal boundaries.

Source: CMMC 2.0, SC.L2-3.13.1. 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

Endpoint management (MDM / EDR)

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

Boundary device configuration such as firewall and gateway rulesets · Endpoint management (MDM / EDR)

periodic reviewEvidence produced at each review

Monitoring evidence at those boundaries · SIEM / log platform

governing documentDocuments that govern the control

Network architecture identifying external and key internal boundaries · Policy repository / GRC workspace

First move

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

Common gaps auditors find

External boundary protected while internal boundaries are flat
Boundary devices configured but traffic not monitored
Cloud and remote boundaries omitted from the architecture

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

RA.L2-3.11.3 Vulnerability Remediation · SC.L2-3.13.2 Security Engineering