AC-17 Remote Access
Establish usage restrictions, configuration requirements, and authorize remote access prior to allowing.
6
artefacts
2
held by a system
1
at each review
moderate
to go live
Identity provider / directory
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Joiner mover leaver workflow evidence integrated with HR · Identity provider / directory
- Account provisioning and deprovisioning workflow tickets with manager approvals · Identity provider / directory
periodic reviewEvidence produced at each review
- Quarterly privileged access review attestations · Identity provider / directory
governing documentDocuments that govern the control
- Control implementation statement for AC-17 citing the system mission and inheritance from common controls · 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
Start with the 2 of 6 artefacts that already live in a system (Identity provider / directory); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Role definitions drift from documented matrix without change control
- Service accounts excluded from periodic recertification
- Stale accounts retained for terminated personnel beyond the 24 hour SLA
- Privileged accounts shared across administrators without individual accountability
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 sheetAC-14 Permitted Actions Without Identification or Authentication · AC-17(1) Monitoring and Control