An access review audit checklist helps you confirm that users have only the permissions they need, privileged accounts receive additional scrutiny, and every decision can be supported with clear evidence. Use this guide for quarterly certifications, employee changes, offboarding reviews, and SOC 2 or ISO 27001 audit preparation.
Overview
An access review is a controlled examination of identities, accounts, roles, and permissions across the systems your organization relies on. The objective is not simply to export a list of users. A useful review connects each account to a person or approved service, confirms that access is appropriate for the person’s current responsibilities, identifies excessive or inactive permissions, and records what happened afterward.
The scope should include your identity provider, production and development environments, cloud consoles, source-code repositories, ticketing and collaboration tools, databases, financial systems, customer-support platforms, and any application that stores confidential or regulated information. Include non-human identities such as service accounts, API keys, automation accounts, and emergency or break-glass accounts where they can access in-scope systems.
Define the review period, system owner, reviewer, approval deadline, evidence location, and remediation owner before collecting data. A repeatable access certification process is easier to operate and easier to explain to an auditor than an informal request for managers to “check permissions.” For broader audit preparation, pair this process with the cybersecurity compliance checklist for small businesses and the control-testing schedule in the SaaS compliance control testing calendar.
Checklist by scenario
Quarterly employee access review
- Set the population. Export active employees, contractors, temporary workers, and relevant accounts from the identity provider or human resources system. Reconcile the list with application-specific user directories.
- Map ownership. Record each application, access group, role, data classification, system owner, and reviewer. A reviewer should understand the user’s job responsibilities or obtain confirmation from someone who does.
- Review each permission. Check whether access is still required, whether the role is appropriate, and whether the user has conflicting or excessive privileges. Pay particular attention to administrator, billing, export, deletion, deployment, and security-management rights.
- Capture a decision. Require an explicit outcome such as approved, modified, removed, or exception requested. Avoid treating a blank response as approval.
- Remediate promptly. Assign an owner and due date for removals or changes. Preserve the original finding and the completed change record.
- Close the cycle. Have the system owner or designated control owner review completion, unresolved exceptions, and overdue actions. Store the final certification with the supporting exports.
New hire, transfer, and offboarding review
- Confirm that new access is based on an approved role or request rather than copied from an unrelated employee.
- For transfers, compare the old and new roles. Remove permissions that belonged only to the former position, and document any temporary overlap.
- For departures, verify the termination time, disablement of the identity-provider account, revocation of sessions and tokens, removal from groups, and recovery or rotation of assigned credentials where applicable.
- Check direct application accounts, shared accounts, service ownership, repository access, cloud keys, VPN access, and physical or administrative access where these are in scope.
- Retain the request, approval, implementation record, and validation that access was actually removed.
Privileged access review
A privileged access review should be more focused than a general user review because administrator permissions can affect security controls, production data, deployments, and audit records. Use this workflow:
- Identify every privileged account, including standing administrators, delegated roles, emergency accounts, and vendor accounts.
- Record the business or operational reason for each privilege and identify the accountable owner.
- Confirm that named accounts are used where feasible and that shared administrative credentials are controlled, justified, and monitored.
- Check whether elevated access is time-limited, approved before use, protected by strong authentication, and separated from ordinary day-to-day accounts.
- Review recent privileged activity or a representative activity record when available. Investigate unexplained use, dormant privileges, and access outside the approved purpose.
- Remove unnecessary privileges, rotate credentials when required, and document any accepted exception with an expiry or review date.
Application-by-application evidence table
| Evidence item | What to capture | Why it matters |
|---|---|---|
| System inventory | Application name, environment, owner, and review period | Defines the scope and responsibility |
| User export | User ID, status, role, groups, and last activity where available | Shows the population evaluated |
| Review record | Reviewer, date, decision, and comments | Shows that access was evaluated rather than merely exported |
| Approval evidence | Manager or system-owner approval and any supporting request | Connects access to a business need |
| Remediation record | Removed or changed permission, implementer, timestamp, and validation | Demonstrates that findings were addressed |
| Exception record | Reason, risk owner, compensating control, expiry, and next review | Prevents temporary exceptions from becoming permanent |
What to double-check
Before closing an access review, compare the review population against more than one source. Identity-provider data may not include local application accounts, legacy users, database users, or vendor identities. Reconcile the application directory with HR or workforce records, asset and application inventories, and cloud or infrastructure account lists.
Check that evidence is complete and readable. An auditor may reasonably expect to see the population reviewed, the person who performed the review, the decision for each relevant account, and proof that identified changes were completed. A screenshot without a date, system context, or identifiable user may be difficult to interpret. Prefer exports, reports, tickets, or system logs that preserve timestamps and ownership.
Review retention against your internal policy, contractual commitments, and the requirements applicable to your organization. Do not keep sensitive access exports indefinitely by default. Restrict access to evidence because user lists, role assignments, and administrative activity can reveal security-sensitive information.
Check exceptions carefully. An exception should explain why access remains, who accepted the risk, what compensating measures apply, when the exception expires, and what event will trigger an earlier review. If the exception has no owner or end date, it is an unresolved access-control issue rather than a controlled deviation.
Finally, distinguish an access review from a vulnerability scan or a general security assessment. The review answers who can access what and whether that access is justified. Other control activities may be needed to test authentication settings, logging, secure configuration, or system vulnerabilities.
Common mistakes
- Reviewing only the identity provider. Local accounts, service accounts, and direct application permissions can be missed.
- Using “no response” as approval. Require an affirmative certification or escalate incomplete reviews.
- Checking membership without checking effective access. Nested groups, inherited roles, and environment-specific permissions can change what a user can actually do.
- Ignoring privileged and emergency accounts. These accounts need an identified owner, a documented purpose, and additional review attention.
- Fixing access without retaining proof. A change may be correct but difficult to demonstrate if the original finding, implementation record, and validation are missing.
- Leaving temporary access open. Add an expiration date or an automated removal path when access is granted for an incident, project, or support session.
- Overloading one reviewer. Separate the person requesting access, the person approving it, and the person implementing changes where practical. If separation is not feasible, document the compensating review.
When to revisit
Run the full review on the cadence defined by your policies and risk assessment, commonly at least quarterly for important systems and more frequently for sensitive or highly privileged environments. Revisit the scope immediately after an acquisition, reorganization, major application rollout, identity-provider migration, cloud-environment change, or material change to access-control procedures.
Use shorter targeted reviews after team changes, high-risk incidents, emergency access, or a significant role change. Add access review tasks to onboarding and offboarding workflows rather than relying only on the next scheduled cycle.
Before an audit, perform a dry run: select a sample of applications, trace users from the source population through reviewer decisions to remediation evidence, and list any missing timestamps, approvals, owners, or exception dates. Update this checklist when your tools add or remove identity-governance capabilities, when retention practices change, or when your SOC 2, ISO 27001, contractual, or internal control scope changes. A practical next step is to create one evidence folder per review period, assign a system owner for every application, and schedule the next certification before closing the current one.