8.2.7 Third-party access managed
Accounts used by third parties to access, support, or maintain system components via remote access are managed and monitored.
5
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
- Session monitoring logs and recordings · Identity provider / directory
- Approval tickets for each session · Identity provider / directory
periodic reviewEvidence produced at each review
- Quarterly review of third-party access · Identity provider / directory
governing documentDocuments that govern the control
- Inventory of third-party accounts and vendors · Policy repository / GRC workspace
- Procedure to enable only when needed and disable after use · Policy repository / GRC workspace
First move
Start with the 2 of 5 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
- Vendor accounts always enabled
- No session monitoring
- No approval per session
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 sheet8.2.6 Inactive user accounts are removed or disabled within 90 days of inactivity · 8.2.8 Session idle timeout