EvidenceSheet

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.

3
artefacts
1
held by a system
0
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

system holds itEvidence a system already holds

  • Enforcement configuration limiting external access · Cloud console / configuration management

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

  • Entitlement listing per external party · Policy repository / GRC workspace
  • Test evidence of an out-of-scope attempt being denied · 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

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

AC-2 Account Management · AC-4 Information Flow Enforcement