Least privilege / access control
Also known as: least privilege, access control, role-based access, RBAC, privileged access
The principle of least privilege means giving every user, app, and device only the minimum access required to do its job -- nothing more.
Combined with good access control, it limits the damage a mistake, a malicious insider, or a hijacked account can cause, since a compromised login can only reach what it was narrowly permitted to.
Least privilege / access control, explained at three levels
At home
Least privilege means only giving people access to what they actually need for their work. Just as not every employee needs a key to every room, not every user needs access to every file or system. It limits what can go wrong.
At work
For a business, least privilege reduces risk: if an account is hacked or misused, the attacker can only reach what that account was allowed to. Giving everyone broad access is convenient but dangerous -- one compromised login could expose everything.
At home
Access control implements least privilege through permissions and roles -- grouping access by job function so people get an appropriate, consistent set of rights. Regular reviews catch 'privilege creep', where people accumulate access over time from old roles and projects they no longer need.
At work
Practical steps: use role-based access, avoid giving standard users admin rights, separate administrative accounts from everyday ones, review access regularly, and remove it promptly when roles change or people leave. Least privilege dramatically limits the blast radius of a compromised account or insider threat.
At home
Advanced practice adds just-in-time access (elevating privileges only when needed, then revoking), separation of duties (no single person controls a whole sensitive process), and privileged access management for admin accounts. Standing high-level access is minimized because it's the most valuable target for attackers.
At work
Mature access control combines RBAC/ABAC, privileged access management (vaulting and just-in-time elevation for admin accounts), separation of duties, periodic access recertification, and automated provisioning/deprovisioning tied to identity. It's central to zero trust: minimal standing privilege, verified per request, so a single compromise can't cascade across the environment.
Real-world examples
At home
Sophie had given her whole small team administrator access 'to keep things simple.' After a phishing incident, her MSP right-sized permissions so each person had only what their role needed -- meaning the next compromised account could reach far less than everything.
At work
Nadia's firm discovered staff had accumulated access to systems from old roles they no longer performed. Her MSP implemented role-based access, separated admin accounts from daily-use ones, and set up regular access reviews -- sharply reducing the damage any single compromised account could do.
Common confusions
- Giving everyone broad access is fine if we trust our staff — Least privilege isn't about distrust -- it limits damage from mistakes, phishing, and compromised accounts, which happen even to trusted, careful people. A hijacked over-privileged account is dangerous regardless of the user's intent.
- Everyday users need administrator rights to work efficiently — Most tasks don't require admin rights, and running as admin lets malware do far more damage. Separating admin from standard accounts is a key least-privilege practice.
- Once access is set correctly, it stays correct — People change roles and accumulate access over time (privilege creep). Regular reviews and prompt removal when roles change are needed to keep least privilege intact.
For analysts
Least privilege is one of the highest-impact ways to contain a breach: the less any account can reach, the less a compromise can harm. Start by removing unnecessary admin rights and reviewing access when roles change -- and make prompt deprovisioning part of offboarding.
History & origin
Least privilege is a foundational security principle articulated in early computer security research in the 1970s. For decades, convenience often won out and users accumulated excessive access. As breaches repeatedly showed how over-privileged accounts amplified damage -- one compromised admin unlocking everything -- least privilege moved to the center of modern security, and it's a core tenet of the zero trust model.