top of page
  • Youtube
  • Facebook
  • X
  • LinkedIn

Privileged Admin Accounts: Who Should Have the Keys

Double Technologies
1 hour ago
5 min read

Every business has a few accounts that can do almost anything: create new users, reset passwords, change email rules, install software, turn off security tools or delete data. Those are your privileged admin accounts, and they are the master keys to the building. In a lot of small offices across Lubbock and the South Plains, those keys get handed out the way a spare door key does. The owner has one, the office manager has one, and so does a former vendor nobody has talked to in years.

That is a real problem. When an attacker gets hold of a normal user's password, the damage is usually limited to what that person can reach. When they get an admin account, they can reach everything. This post walks through who should actually have admin rights, how to separate those rights from everyday work and what a West Texas office can check this week.

What counts as a privileged admin account

A privileged account is any login that can change how your systems work or see data beyond one person's job. Common examples in a small or mid-sized business include:

  • Microsoft 365 or Google Workspace Global Administrator accounts

  • Local administrator rights on Windows laptops and desktops

  • Domain admin accounts on an office server

  • Admin logins for your firewall, Wi-Fi, backup system and line-of-business software (practice management, accounting, dispatch or ag software)

  • Vendor or IT provider accounts that can remotely manage your machines

If you are not sure how many of these exist, that is your first finding.

Why admin accounts are a favorite target

In a joint advisory on the most common cybersecurity misconfigurations, CISA and the NSA listed "improper separation of user/administrator privilege" as number two on their top ten list. They called out three patterns: accounts with more privileges than they need, service accounts with elevated permissions, and people using admin accounts for everyday tasks. Their recommendation is to reduce, restrict, audit and monitor administrative accounts and privileges.

The everyday-use problem is the one we see most in small offices. If the owner of an insurance agency in Brownfield checks email and browses the web while signed in as a Global Administrator, one bad link or one phished password hands an attacker the whole tenant. CISA and the NSA specifically recommend restricting privileged accounts from general tasks such as accessing email and browsing the internet.

The principle: least privilege

The federal standard for this is called least privilege. NIST SP 800-53, the federal security control catalog, defines it in control AC-6 as allowing only the access users need to accomplish their assigned tasks. Related parts of that control call for using non-privileged accounts for non-security work, restricting privileged accounts to specific people and logging the use of privileged functions.

In plain terms: people get the access their job needs, nothing more, and admin power is kept for the moments that actually require it.

Who should have the keys

There is no single right number for every business, but here is a practical way to think about it for a 10 to 75 person office in Lubbock, Amarillo, Abilene or Midland-Odessa.

Give full admin rights to as few people as possible

Microsoft recommends assigning the Global Administrator role to fewer than five people in an organization, and keeping the total number of privileged role assignments under ten. For most small businesses, the right answer is well below that: usually one named person on your side and your IT provider, using separate, protected admin accounts.

Use smaller roles for smaller jobs

Your office manager may need to reset passwords or add a new hire to a shared mailbox. That does not require Global Administrator. Microsoft 365 has many built-in roles, such as roles limited to user management or a single service like Exchange. Microsoft's guidance is to grant a specific set of permissions, over a specific scope, for a specific period of time, and to avoid broad roles just because they are convenient.

Separate admin accounts from daily accounts

Anyone who needs admin rights should have two accounts: a normal account for email, Teams and web browsing, and a separate admin account used only for admin work. The admin account should not have a mailbox people send to, and it should not be used to browse the web.

Remove local admin rights from everyday users

On Windows PCs, most staff do not need to be local administrators. Taking that right away means that when someone opens a malicious attachment, the malware has a much harder time installing itself or switching off security tools.

Lock down the accounts that do need admin rights

Once you know who has the keys, protect those keys harder than anything else:

  • Require MFA on every admin account. Microsoft recommends multifactor authentication for all administrator accounts. If you have not rolled it out yet, our post on MFA for Microsoft 365 covers where to start.

  • Use just-in-time access where your licensing allows it. Microsoft Entra Privileged Identity Management (PIM) lets someone be eligible for an admin role and turn it on for a limited time, with the access removed automatically afterward. Microsoft notes PIM requires Microsoft Entra ID P2 or Microsoft Entra ID Governance licensing, so not every small business has it, but it is worth asking about.

  • Set up two emergency access accounts. Microsoft recommends two or more cloud-only "break glass" accounts with the Global Administrator role, used only when normal admin accounts cannot be used, such as when an admin leaves or MFA devices are unavailable. They should use strong phishing-resistant sign-in such as a passkey, be stored securely, have alerts on every sign-in and be tested regularly.

  • Keep vendor access in check. If an outside vendor has admin rights to your systems, know exactly which accounts they use, make sure those accounts have MFA and remove them when the work is done.

Review who has access on a schedule

Admin rights tend to pile up. Microsoft recommends recurring access reviews so administrators who no longer need a role lose it, and CISA and the NSA recommend routinely auditing user accounts and removing inactive or unnecessary ones.

For a small business, that can be simple:

  1. Pull a list of everyone with admin roles in Microsoft 365 and on your server, firewall and key software.

  2. Ask, for each one, "does this person still need this, and do they need all of it?"

  3. Remove or downgrade anything that is not needed.

  4. Disable accounts for former employees and former vendors the day they leave.

  5. Write down who holds admin rights and repeat the review at least every quarter.

A clinic in Levelland, a CPA firm in Lubbock or a cotton co-op office in Lamesa can usually do this review in an afternoon.

A quick admin account checklist

  • Fewer people with full admin rights than you have fingers on one hand

  • Separate admin and everyday accounts for anyone who needs admin rights

  • MFA on every admin account, with no exceptions

  • Staff are not local administrators on their own PCs

  • Two tested emergency access accounts for Microsoft 365

  • Admin sign-ins logged and someone actually looks at them

  • Former employees and vendors removed promptly

  • A written list of who holds the keys, reviewed every quarter

How Double Technologies helps

Double Technologies helps businesses in Lubbock and across West Texas, from Amarillo to Midland-Odessa, clean up and protect their admin accounts. As part of our Microsoft 365 management and cybersecurity services, we inventory who has admin rights, set up separate admin accounts, turn on MFA, remove local admin rights where they are not needed and document who holds the keys. Our team brings 30 years of combined experience, and we can work remotely or come to you.

Not sure how many people can change everything in your Microsoft 365 tenant? Call Double Technologies at (806) 319-8521 or Schedule an IT Assessment and we will take a look.

Comments


bottom of page