EvidenceSheet

SC-7 Boundary Protection

Controls and monitors the boundaries where supplier, integrator and provider connections meet the organization.

Source: NIST SP 800-161 Rev 1 (supply chain), SC-7. 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-161 Rev 1 (supply chain) in the compliance library.

4
artefacts
2
held by a system
1
at each review
easy
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 rule sets for those connections · Endpoint management (MDM / EDR)
  • Monitoring evidence · SIEM / log platform

periodic reviewEvidence produced at each review

  • Review of the connection inventory · Policy repository / GRC workspace

governing documentDocuments that govern the control

  • Identification of supply chain boundaries and connections · Document repository

First move

Automate the pull from your Endpoint management (MDM / EDR). Device compliance report from the MDM (encryption, EDR agent, OS version) on a daily pull.

Common gaps auditors find

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-5 Denial-of-Service Protection · SC-8 Transmission Confidentiality and Integrity