A quarterly access review is more than a list of users and permissions. It is a repeatable control for confirming that access remains appropriate, privileged rights are justified, leavers are removed, and the organization can show who reviewed each decision. This checklist provides a practical workflow for reviewing employees, contractors, administrators, dormant accounts, service accounts, and segregation-of-duties conflicts across cloud and enterprise environments.
Overview
A quarterly user access review asks a basic question: does every account still have the access it needs, and only the access it needs? The answer should be based on current employment or contract status, job responsibilities, assigned applications, group membership, privilege level, and business ownership of the resource.
The review should produce more than a completed spreadsheet. For each access decision, retain evidence showing the account reviewed, the permissions in scope, the reviewer or approver, the decision made, the date, and the resulting remediation. This record supports cybersecurity compliance and can contribute to audit readiness for programs such as SOC 2, ISO 27001, NIST-aligned governance, and internal security policies. Exact control expectations vary, so map the process to the organization’s adopted framework and documented risk requirements.
Define the review boundary before exporting data. It may include the identity provider, cloud consoles, production systems, code repositories, ticketing tools, databases, finance applications, customer-support platforms, and security tools. If an application is outside centralized identity governance, assign an owner and collect equivalent evidence from that system.
Minimum evidence for each review
- A dated account and permission export from each in-scope system.
- The name or role of the person responsible for certifying access.
- The review decision: approve, modify, revoke, investigate, or document an exception.
- A reason for elevated, unusual, or retained access.
- Tickets, change records, or system logs showing that removals and changes were completed.
- A final sign-off and a record of unresolved items with owners and due dates.
Keep the evidence in a controlled location with appropriate retention and access restrictions. The cybersecurity evidence retention policy guide can help align retention decisions with the wider audit program.
What to track
Use a consistent inventory and a role-owner matrix so reviewers assess access against a known baseline rather than making isolated judgments. The following access review checklist covers the areas most likely to create operational or audit gaps.
1. Employees and contractors
- Match each account to a current worker record, department, manager, and employment or contract status.
- Confirm that the user’s role still justifies assigned applications, groups, data stores, and environments.
- Review recent transfers, promotions, reorganizations, and extended leave for stale permissions.
- Check contractors for an accountable internal sponsor, contract end date, and approved scope.
- Confirm that temporary access has an expiration date rather than relying on manual removal.
2. Privileged administrators
Run a separate privileged access review instead of burying administrator accounts in the general user list. Identify global administrators, cloud account owners, production operators, security administrators, database administrators, and users with the ability to create identities or change logging and security controls.
- Record the specific privileged role, system, and business justification.
- Confirm that administrative access is assigned to named individuals where practical, not shared accounts.
- Check whether just-in-time, approval-based, or time-limited elevation is available and being used.
- Review emergency or break-glass accounts for secure storage, limited use, monitoring, and periodic testing.
- Verify that administrator activity is logged and that access does not bypass required authentication controls.
For cloud environments, distinguish control-plane roles from permissions within individual subscriptions, projects, accounts, clusters, and workloads. The cloud shared responsibility comparison provides useful context when assigning ownership for identity and access controls.
3. Service accounts, workload identities, and automation
Service accounts are frequently overlooked because they are not tied to a human manager. For each account or workload identity, record its owner, purpose, connected system, permissions, authentication method, last-use information where available, and planned review date.
- Remove unused accounts and permissions that are no longer required by the application.
- Replace broad roles with narrowly scoped permissions where the workload supports it.
- Confirm that secrets, keys, and tokens are managed through an approved mechanism and rotated according to policy.
- Check for credentials embedded in code, deployment files, scripts, or shared documentation.
- Set an owner and renewal or expiration process for every non-human identity.
4. Dormant, orphaned, and duplicate accounts
Compare identity-provider data with application inventories, HR or contractor records, and recent authentication activity. Flag accounts that have not been used within the organization’s defined period, accounts without an owner, duplicate identities, and accounts associated with departed workers. Do not delete an account solely because it is inactive if it supports a retention, legal, or operational requirement; suspend it, document the reason, and assign an owner when appropriate.
5. Segregation of duties
Test combinations of access that could allow one person to initiate, approve, execute, and conceal a sensitive transaction. Examples may include creating a supplier and approving payment, deploying code and approving its production release, or administering an identity platform while reviewing its own access. Maintain a defined conflict list, record legitimate exceptions, and require an independent approver for compensating controls.
Reusable role-owner matrix
Maintain a simple matrix with these columns: system or resource, role or group, permission level, business owner, technical owner, eligible users, review frequency, evidence location, and exception requirement. This structure makes ownership gaps visible and helps separate application approval from technical remediation.
Cadence and checkpoints
Quarterly is a useful baseline for many business systems, but it should not be the only access checkpoint. Set review frequency according to privilege, data sensitivity, regulatory obligations, change volume, and operational risk. Privileged access, production access, sensitive personal data, and high-impact systems may require more frequent or event-driven review. The organization’s documented policy should define the final schedule.
Step-by-step quarterly workflow
- Set the scope. List systems, environments, roles, groups, accounts, and owners included in the cycle. Note exclusions and their rationale.
- Freeze the evidence set. Export access data with timestamps and preserve the query or report configuration so the population can be reproduced.
- Reconcile identities. Compare the export with worker records, contractor records, application inventories, and termination reports.
- Route decisions. Send access to the appropriate manager, application owner, data owner, or privileged-access owner. Do not assume one reviewer understands every permission.
- Investigate exceptions. Require a reason, risk owner, compensating control, expiration date, and independent approval for access that falls outside the standard role.
- Remediate. Remove unnecessary access, disable accounts, reduce roles, rotate credentials where needed, and resolve ownership gaps.
- Verify closure. Recheck the system after changes. Evidence should show the requested action and the completed result, not just an intention to remediate.
- Sign off and report. Summarize reviewed accounts, approvals, removals, unresolved items, exceptions, and overdue actions for security and compliance stakeholders.
Use event-driven checkpoints after termination, internal transfer, acquisition, major reorganization, identity-provider migration, material application change, or a security incident. A compliance calendar can help connect these events with recurring reviews; see the cybersecurity compliance calendar template.
How to interpret changes
The value of a recurring access review comes from the patterns it reveals, not only from the number of approvals. Track trends such as the percentage of accounts with a named owner, privileged roles without recent use, dormant accounts, overdue removals, unresolved exceptions, service accounts without expiration dates, and systems that cannot produce reliable access evidence.
A growing number of access changes may reflect legitimate hiring, restructuring, or a new application. It may also indicate role design problems, manual provisioning, or excessive use of group membership. Investigate the cause before treating the number as a performance measure. High approval rates are not necessarily positive if reviewers approve access without examining the permission detail.
Prioritize findings by potential impact and ease of exploitation. An unowned global administrator account generally deserves faster treatment than a stale low-risk read-only permission. Escalate repeated exceptions, missing system owners, and failures to complete termination reconciliation because they indicate process weaknesses rather than isolated access errors.
When a review identifies unauthorized or unexpectedly broad access, preserve relevant logs and follow the organization’s incident and investigation procedures. If personal data may be involved, use the applicable breach assessment process; the GDPR data breach notification decision tree offers a separate decision aid for that scenario.
When to revisit
Schedule the next quarterly access review before the current cycle closes. At minimum, revisit the checklist every quarter, after an identity-platform or cloud migration, when applications are added to the environment, after an acquisition or reorganization, and before a planned security audit. Also update it when the organization changes its access policy, role model, evidence-retention rules, or adopted compliance framework.
Before each cycle, confirm that terminology still matches the identity provider and cloud platforms in use. Review whether new workload identity types, administrative roles, authentication methods, or automation features have created additional review populations. Test that reports still include disabled, federated, external, emergency, and non-human accounts.
For a practical next step, assign an owner today and create a review record with these fields: scope, evidence date, reviewer, decision, remediation ticket, exception expiry, verification date, and final sign-off. Start with privileged access and termination reconciliation if resources are limited, then expand coverage to applications, service accounts, and segregation-of-duties checks. A consistent quarterly process produces stronger evidence and a clearer security baseline than an occasional review performed only when an audit is approaching.