A user access review is a periodic check, by someone who knows what access each person should have, that every account and permission in a system is still appropriate. For SOC 2 it supports criteria CC6.2 and CC6.3. Auditors look for a complete user list, an informed reviewer, documented decisions and proof that required changes were made.
Key takeaways
- Quarterly is the common frequency for in-scope production systems. Whatever you commit to, perform it on time.
- The user list must come from the system itself, with evidence of how it was generated.
- The reviewer should not be reviewing their own access.
- A review that finds nothing to remove, every time, invites questions.
Step-by-step procedure
- Define scope. Production infrastructure, source control, identity provider, databases, and applications holding customer data. Include service accounts and administrator roles.
- Generate the population. Export users and roles directly from each system. Keep the query or screenshot showing date, system and record count.
- Assign reviewers. The manager of each user or the system owner. An administrator’s access is reviewed by someone else.
- Review. For each account: is the person still employed, do they still need this role, is the privilege level right?
- Record decisions. Keep, modify or remove, with reviewer name and date.
- Remediate. Raise a ticket for each change and complete it within your stated timeframe.
- Sign off. The reviewer confirms completion. Store everything together.
What the auditor asks for
| Evidence | Why |
|---|---|
| System-generated user list with date and count | Completeness and accuracy of the population |
| Reviewer’s documented decisions | The review happened and was informed |
| Tickets for removals and changes | Findings were acted on |
| HR list of active staff for comparison | Terminated users were caught |
The first item is information produced by the entity. See tests of controls, IPE and IUC.
Common exceptions
- The review was performed late or skipped for one quarter.
- The list was an edited spreadsheet with no trace to the source system.
- Service or shared accounts were left out.
- Access flagged for removal was still active weeks later.
Frequently asked questions
Does single sign-on replace access reviews?
No. It centralizes the list, which makes the review easier, but permissions inside each application still need review.
Is an annual review enough?
For low-risk systems it can be. For production and administrative access, auditors and buyers expect more frequent review.
Can a GRC platform do this?
It can collect lists and record decisions. A person still has to make the decisions.
Sources & further reading
AICPA 2017 Trust Services Criteria, CC6.2 and CC6.3.
Related: SOC 2 controls list, Audit evidence management, SOC 2 readiness checklist, Types of controls: preventive, detective and corrective.
Work with a licensed CPA firm
Auditsuisse Assurance NA PC is a licensed US CPA firm enrolled in the AICPA Peer Review Program. See our published SOC 2 fees or book a scoping call.