03.13.01 Boundary Protection
Monitor and control communications at external boundaries and key internal boundaries of the system; implement subnetworks for publicly accessible components separated from internal networks; connect to external networks only through managed interfaces.
Source: NIST SP 800-171 Rev 3, 03.13.01. 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 NIST SP 800-171 Rev 3 in the compliance library.
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 config · Cloud console / configuration management
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- DMZ design · Document repository
- Managed interface inventory · Policy repository / GRC workspace
- IDS/IPS placement · Document repository
First move
Common gaps auditors find
- public services on internal networks
- no egress filtering
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 sheet03.12.05 Information Exchange · 03.13.04 Information in Shared System Resources