People change roles. Projects end. Vendors come and go. But access to email, shared files, payroll, customer records, and admin consoles can quietly accumulate. A short, repeatable review helps you catch accounts nobody owns and permissions that no longer fit the work.
The goal is not to make access difficult. It is to make sure each account has a real person or business purpose behind it, with only the permissions it needs. CISA recommends that application and data owners periodically review and reconcile accounts and privileges as part of identity governance. Here is a practical way to bring that idea into a small business.
Begin with systems that hold sensitive information or can change how the business runs: email, accounting and payroll, customer relationship management, file storage, line-of-business applications, remote access, backup consoles, and administrator portals. Include printers and document systems when they store scans, address books, or job history.
You do not need a perfect master inventory on day one. Pick one critical system and ask its owner for a current user and administrator list. Record the system, business owner, review date, and where access is managed.
For each account, identify the person who uses it and the manager who approves the access. Flag accounts tied to former employees, temporary staff, old vendors, test projects, or names no one recognizes. Check for duplicate accounts too; a person may have both an everyday account and a separate administrator account.
Shared logins deserve special attention. If a shared account is unavoidable, document why it exists, who may use it, who changes its password, and how activity can be traced. Where the system allows it, named accounts make review and investigation clearer.
Ask a simple question: “Does this person still need this access to do their current work?” Check role changes as well as departures. Someone who moved teams may have kept old permissions while receiving new ones. CISA notes that unmanaged role changes can leave people with privileges they no longer need.
Look beyond whether someone can sign in. Review what they can do: read, edit, export, approve payments, manage users, change security settings, or delete data. Pay particular attention to administrator roles, finance approvals, sensitive folders, and remote access.
Not every account belongs to an employee. Find application integrations, automation accounts, vendor logins, break-glass accounts, and devices that authenticate to other systems. Confirm who owns each one, what depends on it, and whether it is still needed. Avoid disabling an unfamiliar technical account until its purpose and dependencies are understood.
For each item, record one outcome: keep, change, disable, investigate, or assign an owner. Note who approved the decision and when it was completed. Remove access through the system’s normal process, then confirm the change took effect. If removing an account could interrupt a business process, coordinate a safe replacement before closing it.
A review only helps if it happens again. Choose a schedule based on the sensitivity of the system, the pace of staff changes, and any contractual or regulatory requirements. Review high-impact access more often, and run a focused check whenever someone changes roles, a vendor relationship ends, or an application is replaced.
If an account has no owner or clear business purpose, treat that as a question to resolve—not an invitation to guess. Keep the review small enough to finish, and work through one system at a time.
Technic’s cybersecurity team helps businesses review secure access, identity controls, credential exposure, and security documentation. Explore Technic cybersecurity and compliance services or contact our team to talk through your environment and priorities.