Least Privilege: Give People Only the Access They Need

By Information Security Asia · Updated November 21, 2026 · 4 min read

Short answer: least privilege means every person, app and device gets only the access it needs to do its job, and nothing more, for only as long as it needs it. For a small business, the most valuable steps are: remove local administrator rights from everyday computer accounts, give each person their own login instead of shared accounts, limit who can access finance and customer data, use separate admin accounts for IT tasks, and remove access promptly when people change roles or leave.

The idea is old, but it has become central to modern security frameworks such as NIST’s guidance and “zero trust” architectures. The reason is simple: attackers who steal one account inherit everything that account can reach. Limiting access limits the damage.

Least Privilege: Give People Only the Access They Need

Why least privilege matters

  • Contains phishing: if a receptionist’s account is phished, the attacker should not reach payroll or the customer database.
  • Slows ransomware: malware running without admin rights struggles to disable security tools, install itself deeply or spread across the network.
  • Reduces mistakes: fewer people can accidentally delete shared folders or change critical settings.
  • Helps compliance: regulations and cyber insurance questionnaires increasingly ask about admin rights and access reviews.
  • Limits insider risk: departing or disgruntled employees can do less harm.

Where to apply it first

Area Common problem Least-privilege fix
Computers Everyone is a local administrator Standard user accounts; admin only when needed
Email and cloud (Microsoft 365, Google Workspace) Several global admins, admins used for daily email Two or three dedicated admin accounts with strong MFA
Shared drives “Everyone” can edit everything Folders by team or role
Finance and banking Shared logins to the bank portal Individual logins, approval workflows, payment limits
Website and hosting Every contractor has admin Lowest role needed; remove after the project
Third-party apps Apps granted full mailbox or drive access Review and remove unneeded permissions

Step 1: Inventory who has access to what

List your key systems: email, file storage, accounting, banking, CRM, website, social media and password manager. For each, write down who has access and at what level. Most small businesses discover former staff, old contractors and far too many administrators.

Step 2: Remove everyday admin rights on computers

Create a separate administrator account on each Windows PC or Mac for installations and settings, and give staff standard accounts for daily work. On Windows, Microsoft recommends standard accounts for daily use. If removing admin rights disrupts work, look at what software people install and provide an approved way to request it.

Step 3: Separate admin accounts in cloud services

  • Use dedicated admin accounts (for example admin.jane@) that are not used for daily email or browsing.
  • Keep the number of global or super administrators small, typically two for redundancy.
  • Protect admin accounts with phishing-resistant MFA such as passkeys or security keys. See setting up a hardware security key.
  • Use built-in limited roles (billing admin, user admin, helpdesk) instead of full admin where possible.

Step 4: Eliminate shared accounts

Shared logins make it impossible to know who did what and difficult to remove someone’s access. Give everyone individual accounts. Where a shared account is unavoidable, such as a social media profile, store its credentials in a business password manager with sharing controls and change the password when someone leaves. See sharing passwords safely.

Step 5: Use time-limited and just-in-time access

Contractors and temporary projects should have access that expires. Some platforms support just-in-time elevation, where admin rights are granted for a few hours on request. Even without special tools, put an end date in your calendar to remove access.

Least Privilege: Give People Only the Access They Need

Step 6: Build joiner, mover and leaver processes

  • Joiners: start with a standard role template for their job.
  • Movers: remove old access when someone changes roles, instead of just adding new access.
  • Leavers: disable accounts on the last day, transfer file ownership, revoke app sessions, collect devices and change shared passwords.

Step 7: Review access regularly

Every quarter, review admin lists, shared folder permissions and connected third-party apps. It takes an hour for most small businesses and catches access creep before it becomes a problem.

Frequently asked questions

Will removing admin rights annoy staff?

Briefly, sometimes. Provide a quick way to request software and most friction disappears. The security benefit is large.

Is least privilege the same as zero trust?

Least privilege is one key principle of zero trust. Zero trust also includes verifying every access request and assuming the network may already be compromised.

Should the business owner have admin rights?

The owner should have access to admin accounts for recovery, but use a standard account day to day, like everyone else.

What about service accounts and API keys?

Apply the same rule: give integrations only the scopes they need, and rotate keys when staff with access leave.

Related: incident response plan for small businesses, ransomware preparation checklist.

Sources

Keep reading