AC-3 Access Enforcement
Enforces the boundary between what a supplier or integrator is authorized to reach and the rest of the environment, rather than trusting the relationship.
Source: NIST SP 800-161 Rev 1 (supply chain), AC-3. 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.
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
- Enforcement configuration limiting external access · Cloud console / configuration management
periodic reviewEvidence produced at each review
- Test evidence of an out-of-scope attempt being denied · Policy repository / GRC workspace
governing documentDocuments that govern the control
- Entitlement listing per external party · Policy repository / GRC workspace
First move
Common gaps auditors find
- supplier access granted at network level rather than to named resources
- enforcement never tested
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