EvidenceSheet

AC-3 Access Enforcement

Enforce approved authorizations for logical access in accordance with policy.

Source: FedRAMP Moderate (NIST SP 800-53 Rev 5 baseline), 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 FedRAMP Moderate (NIST SP 800-53 Rev 5 baseline) in the compliance library.

A FedRAMP baseline is a subset of NIST SP 800-53 Rev 5, enhancements included.

6
artefacts
1
held by a system
2
at each review
hard
to go live
Policy repository / GRC workspace
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

  • Account provisioning and deprovisioning workflow tickets with manager approvals · Identity provider / directory

periodic reviewEvidence produced at each review

  • Authorisation test results showing denied requests for users lacking the required role · Identity provider / directory
  • Quarterly privileged access review attestations · Identity provider / directory

governing documentDocuments that govern the control

  • SSP AC-3 statement describing the enforcement mechanism (IAM policies, RBAC in the application, database grants) for each system layer · Policy repository / GRC workspace
  • Access control policy approved by the information security officer · Policy repository / GRC workspace
  • Role-based access matrix mapped to job functions and data classifications · Policy repository / GRC workspace

First move

Mostly documents and reviews. Pull the 1 system-held artefact from your Identity provider / directory on a schedule; put the documents under version control with an owner and review date, and log each review 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(13) Disable Accounts for High-Risk Individuals · AC-4 Information Flow Enforcement