A quarterly SOC 2 user access review helps a SaaS company confirm that people, service accounts, and cloud permissions still match business needs. This guide provides a repeatable access recertification procedure, a practical checklist for joiner-mover-leaver events, prompts for reviewing privileged and service accounts, an exception-approval template, and an evidence structure that is easier to maintain throughout the audit period.
Overview
A SOC 2 access review is a documented check that user and system access remains authorized, appropriate, and consistent with the organization’s security policies. The review commonly covers the identity provider, production systems, cloud consoles, source-code repositories, ticketing platforms, customer-support tools, databases, and other systems that can affect the security or availability of the service.
The objective is not simply to export a list of users. A useful review connects each account to an owner, role, business need, access level, and review decision. Reviewers should be able to answer four questions:
- Who has access to the system?
- What permissions does each person or account have?
- Why is that access still required?
- What action was taken when access was unnecessary, excessive, or unclear?
Assign a process owner before the review begins. The owner coordinates exports, distributes review tasks, tracks decisions, follows up on exceptions, and assembles the evidence package. System owners and people managers should make access decisions for their areas, while security or compliance personnel should check that the procedure was completed consistently.
This procedure should fit into the broader control environment. For example, a cloud access review should align with the responsibilities documented in your cloud compliance shared responsibility matrix, while control owners can connect the results to a SOC 2 controls mapping matrix.
What to track
Use one review register for the quarter, with separate views for each system or application. At minimum, record the following fields:
- System or platform name
- Account or identity identifier
- Account type: employee, contractor, vendor, service account, or emergency account
- Department, team, or account owner
- Role, group, or permission set
- Privileged access indicator
- Last authentication or activity date, where available
- Business justification for access
- Reviewer and review date
- Decision: retain, reduce, suspend, remove, or investigate
- Remediation ticket or change reference
- Exception approval and expiry date, if applicable
Compare roles against actual permissions rather than relying on job titles alone. A simple comparison can expose excessive access:
| Review area | Expected check | Evidence to retain |
|---|---|---|
| Standard user access | Does the person still need the assigned application and group membership? | Export, reviewer decision, and access-change record |
| Privileged access | Is administrator or production access necessary, limited, and separately approved? | Permission detail, manager or system-owner approval, and activity review |
| Cloud roles | Do roles permit only the resources and actions required for the person’s duties? | Role export, policy detail, and remediation ticket |
| Repository access | Are write, merge, deployment, and secret-management permissions restricted to appropriate users? | Repository settings export and reviewer sign-off |
| Service accounts | Is each account owned, documented, monitored, and limited to a defined workload? | Inventory record, owner confirmation, and credential or key review |
Joiner, mover, and leaver checks
Quarterly recertification should not replace event-driven access management. Reconcile the review register against HR or workforce records and check:
- Joiners: access was approved for the role, uses the correct groups, and did not inherit unnecessary permissions.
- Movers: old role-based access was removed when responsibilities changed, especially after a move into engineering, operations, finance, or management.
- Leavers: accounts were disabled promptly according to the company’s procedure, sessions and tokens were handled appropriately, and shared credentials were rotated where necessary.
Keep the quarterly review and the individual joiner-mover-leaver records together enough to show that access changes are both preventive and responsive. A related SOC 2 audit evidence collection calendar can help assign recurring evidence tasks and owners.
Cadence and checkpoints
Run the core review quarterly, or more frequently when your risk assessment, customer commitments, or internal policy requires it. Use a fixed schedule so the review does not depend on the audit date.
- Prepare: confirm systems in scope, reviewers, due dates, and the period covered. Freeze the source exports or record when each export was generated.
- Collect: obtain user, group, role, privileged-access, service-account, and activity data from each in-scope platform.
- Reconcile: compare identities with current workforce and vendor records. Investigate duplicate, dormant, unknown, or ownerless accounts.
- Review: have managers or system owners approve, reduce, remove, or investigate each access assignment.
- Remediate: create tracked changes for removals, role reductions, account disablement, and credential rotation. Record completion dates.
- Close: resolve open questions, approve exceptions, and assemble a read-only evidence package.
Set intermediate checkpoints rather than giving reviewers one deadline. For example, complete data collection in week one, owner review in week two, remediation in week three, and evidence quality control in week four. The exact timing can vary; consistent ownership and traceability matter more than a particular calendar.
Service-account review prompts
Service accounts can be overlooked because they are not tied to a person. For each one, confirm its owner, purpose, associated application or workload, permissions, authentication method, credential rotation responsibility, monitoring, and decommissioning condition. Ask whether a managed identity, short-lived credential, or narrower role could replace a persistent secret. If an account must retain elevated permissions, document why and set a review or expiry date.
How to interpret changes
Not every change indicates a control failure. A growing user population, new cloud environment, acquisition, reorganization, or product launch may legitimately change the access profile. The important question is whether the process detected the change and whether access remained proportionate to the risk.
Look for patterns across quarters:
- Repeated late reviews may indicate unclear ownership or an impractical workflow.
- Frequent emergency exceptions may indicate that standard roles do not match operational needs.
- Many dormant or ownerless accounts may point to weak offboarding or inventory processes.
- Repeated privilege reductions in one team may justify role redesign or tighter provisioning rules.
- Unresolved service-account ownership should be treated as an inventory and accountability gap.
Use a consistent exception record when access cannot be reduced immediately. The record should state: the account and system, access requested or retained, business reason, risk and compensating controls, approver, date approved, remediation owner, target completion date, and expiry or next-review date. Example wording: “Production administrator access retained for incident response during the migration window. Access is limited to named personnel, activity is logged, and the system owner will review removal by the stated date.” Avoid indefinite exceptions without a named owner and follow-up date.
Evidence should show the full chain from source data to conclusion. A practical evidence package contains the procedure version, in-scope system list, dated exports, reviewer assignments, completed decisions, exception records, remediation tickets, completion proof, and a final sign-off. Store source files in a controlled location and preserve the dates and version details needed to explain what was reviewed.
When to revisit
Revisit the procedure every quarter as part of the scheduled access review. Do not wait for the next quarter when a material change occurs. Start an additional review after a major reorganization, acquisition, production-platform migration, identity-provider change, privileged-access incident, significant vendor change, or discovery of an unknown account.
Before each annual audit cycle, compare the procedure with the control descriptions, system inventory, customer commitments, and evidence requests currently in use. Confirm that platform exports still contain the fields your reviewers need and that screenshots or console paths have not become obsolete. Update role definitions, exception language, ownership assignments, and evidence-retention instructions when the operating model changes.
At the end of each quarter, record three brief lessons: what was late, what was unclear, and what should be automated or removed from the next review. Then schedule the next review, assign owners, and preserve the completed evidence package. This turns access recertification from an annual audit exercise into a dependable cloud security and vendor assurance control.
For related recurring compliance work, use the security policy lifecycle guide to manage procedure updates and the vendor security questionnaire playbook when third parties request evidence of your access controls.