Most access problems are not caused by malicious employees. They are caused by good employees who changed roles, left the company, or kept a login because nobody asked for it back. An access review is the control that catches those leftovers before an auditor, a customer or an attacker does.
This checklist is designed for a business without a dedicated identity team. Each group names an owner, the evidence to keep and the verification step that proves the review happened. Run a full review quarterly, with a lighter monthly check for joiners, movers and leavers.
1. Scope and system inventory
Owner: IT or the operations lead.
- List every system that holds company or customer data: email, file storage, CRM, accounting, HR, payment, ecommerce, cloud, databases and remote access.
- Record the system owner, the authentication method, the admin contact and whether single sign-on is supported.
- Mark systems that hold payment data, personal data or privileged administrative access.
- Confirm which systems are covered by the review and which are out of scope with a reason.
Evidence: a system register with owners and dates.
2. Joiner, mover and leaver process
Owner: HR with IT.
- HR notifies IT before the start date, not after.
- New access is requested by the manager and approved against the role profile.
- Role changes trigger a review of existing access, not only new access.
- Leavers are disabled on the last working day, with email forwarding and data handover defined.
- A named person confirms completion and records the time.
Evidence: tickets for each joiner, mover and leaver, with the approval and the completion timestamp.
3. Privileged access
Owner: IT security or the most senior technical lead.
- List all administrative accounts for cloud, servers, databases, network devices and financial systems.
- Confirm that administrators use separate accounts for daily work and admin tasks.
- Require multi-factor authentication for administrative access.
- Remove standing admin rights where a time-bound or approval-based elevation is possible.
- Review vendor and contractor admin accounts separately.
Evidence: an admin account list, the approver, the date and the MFA status for each account.
4. Quarterly user access review
Owner: each system owner, coordinated by IT.
- Export the current user list with roles and last login date.
- Ask each manager to confirm, change or revoke access for their team.
- Do not accept a blanket "all fine" response. Require a decision per user or per role group.
- Record the reviewer, the date and the decision.
- Remove access that is no longer required within a defined service level.
Evidence: the exported list, the reviewer's decisions and the revocation tickets.
5. Data and file share permissions
Owner: data owners, supported by IT.
- Review access to finance, HR, customer and legal folders.
- Remove "everyone" and "all staff" permissions from sensitive locations.
- Check that shared links expire and that external sharing is restricted by default.
- Confirm that departed staff no longer appear in group memberships.
Evidence: a permissions report and a list of changes made.
6. Vendor and third-party access
Owner: procurement with IT.
- List every vendor with a login to a company system.
- Confirm the business reason, the contract owner and the expiry or review date.
- Use named accounts, not shared vendor accounts, where the system allows it.
- Disable access when the contract ends, not when someone remembers.
Evidence: the vendor access register and the review decision.
7. Service and shared accounts
Owner: IT.
- Inventory service accounts used by integrations, scheduled jobs and devices.
- Document the owner, purpose and rotation schedule for each credential.
- Remove interactive login rights from service accounts where possible.
- Check for shared passwords stored in spreadsheets, chat messages or code repositories.
Evidence: a service account register with owners and rotation dates.
8. Authentication controls
Owner: IT.
- Confirm MFA on email, remote access, cloud consoles and financial systems.
- Enable single sign-on where supported to reduce orphaned accounts.
- Review password and session policies, including lockout and timeout.
- Check that former staff cannot reset a password through a personal email or phone number.
Evidence: a configuration screenshot and the date checked.
9. Revocation and verification
Owner: IT.
- Test one leaver scenario end to end: disable the account, revoke sessions, remove group memberships and confirm access fails.
- Sample five active users and trace their access back to an approved request.
- Sample five leavers from the last quarter and confirm none can still authenticate.
- Record the test result, including failures and the fix.
Evidence: a test log with the accounts checked and the outcome.
10. Reporting and follow-up
Owner: management.
- Report the number of accounts reviewed, revoked and still pending.
- Report exceptions with an owner and a due date.
- Track overdue revocations and repeat findings.
- Review the process itself once a year and simplify any step that consistently gets skipped.
Verification checklist
- Every system in scope has a named owner.
- Every active account maps to a current employee or approved vendor.
- Every admin account is approved and protected by MFA.
- Every leaver from the last quarter is disabled.
- Every review has a reviewer, a date and a decision.
- Every exception has an owner and a due date.
Common mistakes
- Reviewing an old spreadsheet instead of a live export.
- Asking managers to approve everything in one email.
- Leaving shared accounts because "the team needs it".
- Disabling the account but forgetting active sessions and API tokens.
- Reviewing application access but not file shares or cloud roles.
- Treating the review as an annual audit rather than an operational control.
Metrics to track
- Percentage of leavers disabled within the agreed service level.
- Number of orphaned accounts found per review.
- Percentage of admin accounts with MFA.
- Average days to revoke access after a review decision.
- Number of repeat exceptions across two reviews.
- Percentage of systems covered by the review.
Where this fits in our work
If you need a review that produces evidence rather than a signed spreadsheet, start with Managed Technology & Cybersecurity. The pricing page explains how we scope identity and access work. For the supplier side, read how third-party security risk changes as you grow.
Sources
- NIST SP 800-53 Rev. 5, Security and Privacy Controls for Information Systems and Organizations, accessed 17 November 2026.
- NIST SP 800-63B, Digital Identity Guidelines, accessed 17 November 2026.
- CIS Critical Security Controls, accessed 17 November 2026.
- ISO/IEC 27001, Information Security Management Systems, accessed 17 November 2026.
Responses (0)
No comments yet. Add the first one below.
Leave a response
Your email address will not be published. Required fields are marked *.