
IT Hygiene: Getting Rid of Shared Accounts
Most small businesses have shared accounts somewhere. The front desk computer that logs in as "frontdesk." The parts counter login everyone knows. The admin password for the firewall written on a sticky note in the server closet. The office email account three people check. The accounting system login the bookkeeper and the controller both use.
Shared accounts usually start for convenience. They stick around because nobody owns the problem. This post explains why they matter, which frameworks address them, and how to remove them without slowing the business down.
Why shared accounts are a real problem
You lose accountability. When five people use one login, the logs show one user. If a record is changed, a refund is issued, or a file is copied, you cannot tell who did it. That matters for fraud investigations, for HR issues, and for any security incident.
You cannot remove access for one person. When someone leaves, the only way to cut off their access to a shared account is to change the password, which affects everyone else. In practice, the password often does not get changed, so former employees keep access. Our same-day offboarding guide covers the rest of that process.
MFA becomes awkward. Multi factor authentication is tied to a person's phone or token. Shared accounts either skip MFA or tie it to one person's phone, which creates a bottleneck and a workaround culture. Our MFA policy guide covers how to require it across the board.
Passwords spread. A shared password gets written down, texted, emailed, and saved in browsers on multiple machines. Each copy is another way it can leak.
What the frameworks say
- CIS Controls v8.1, Control 5 (Account Management) calls for an inventory of all accounts, unique passwords, disabling dormant accounts, and restricting admin privileges to dedicated admin accounts.
- HIPAA, 45 CFR 164.312(a)(2)(i) lists unique user identification as a required implementation specification: assign a unique name or number for identifying and tracking user identity. A shared login to an EHR or practice management system is hard to reconcile with that requirement.
- FTC Safeguards Rule, 16 CFR 314.4(c)(8) requires policies, procedures, and controls designed to monitor and log the activity of authorized users and detect unauthorized access or use. Logging activity by user is not meaningful when users share an account.
- NIST SP 800-171 Rev. 2 (the revision CMMC Level 2 assesses against), requirement 3.5.1, calls for identifying system users, and 3.3.2 requires that actions can be traced to individual users. For defense suppliers handling CUI, shared logins on in scope systems are a direct problem.
Finding them
Shared accounts hide in predictable places. Look at:
- Workstations. Any computer that logs in automatically or under a generic name, often at a front desk, a shop floor, a parts counter, or a nurses' station.
- Line of business applications. Practice management, DMS, ERP, and accounting systems often have generic users created during setup.
- Email. Shared mailboxes are fine. Shared mailbox logins, where people sign in with the mailbox's own password, are not.
- Network and infrastructure devices. Firewalls, switches, wireless controllers, printers, and cameras usually ship with a single admin account.
- Cloud services. Social media, shipping portals, supplier portals, bank portals, and marketing tools frequently have one login shared across a team.
- Vendor accounts. Support vendors sometimes use one account for all their technicians.
A practical method: export the user lists from your main systems and look for names that are not people. Then ask each department manager which logins their team shares. People are usually candid about this when it is framed as fixing a nuisance rather than catching rule breaking.
Replacing them
Each type of shared account has a standard fix.
Shared workstations. Give each person their own login. If speed is the concern, use fast user switching, badge tap login, or a short screen lock timeout with a quick sign in. Many clinical and retail environments solve this with proximity badges.
Applications. Create individual accounts for each user. Check licensing first, since some applications license per named user. If cost is truly prohibitive, document the exception and add compensating controls, such as logging at the workstation level so you can tie actions to a person.
Email. Convert shared logins to shared mailboxes that individuals access with their own accounts. In Microsoft 365, shared mailboxes do not need a separate license in most cases and do not need their own password.
Infrastructure devices. Where devices support it, connect administration to your directory so admins sign in with their own accounts. Where they do not, store the admin credential in a password manager with access logging, limit who can retrieve it, and change it when someone with access leaves.
Cloud services. Most business tools support multiple users. Use them. For services that truly allow only one login, store the credential in a shared vault in your password manager, turn on MFA tied to a role phone or a shared authenticator that is controlled, and log who retrieves it.
Vendors. Require named accounts for each technician, or at least a vendor portal that records which technician connected.
Handling the exceptions
Some shared accounts cannot be removed right away. A medical device might require a fixed login. A legacy application might support only one user. For those:
- Document the account, the reason, and the system owner.
- Limit where the account can be used, for example from one workstation only.
- Store the credential in a password manager rather than on paper.
- Add logging that shows who was at the workstation or who retrieved the password.
- Set a review date and revisit when the system is upgraded or replaced.
A documented exception with compensating controls is much stronger than an undocumented shared login that everyone knows.
Making it stick
Removing shared accounts is not a one time project. New ones appear whenever someone sets up a new tool in a hurry. Add these to your routine:
- A question on every new system request: does each user get their own account?
- A periodic review of user lists for generic names.
- A rule in your access control policy that shared accounts require approval.
This is basic hygiene, but it pays off quickly. It makes offboarding cleaner, makes MFA possible, and gives you real logs when you need them.
Shared admin accounts are often tied up with local admin rights, so our post on removing local admin rights is a good next read. For framework detail, see our HIPAA, FTC Safeguards, and NIST pages, or take the free compliance checklist. If you want help finding and replacing shared accounts in your environment, book your free risk review.