Cybersecurity glossary
What is Least Privilege?
Learn what the principle of least privilege means, how excess permissions enable breaches, practical ways to shrink standing access, and how JIT and reviews keep privileges minimal.
Definition
Least privilege is a security principle that grants each user, process, or system only the minimum permissions required to perform an authorized task—for the minimum necessary time—reducing the impact of mistakes and compromised credentials.
Why excess permission is the default failure mode
Access expands quietly: a shared admin group here, a temporary cloud role there, an OAuth grant “just in case.” Least privilege pushes the opposite direction—only what is required, only while required.
It is not a product you buy. It is a design constraint you apply to every identity and token.
What least privilege looks like in practice
Human users
Standard accounts for daily work; elevate only for admin tasks.
Service accounts
One workload, one identity, narrow API scopes and network paths.
Cloud roles
Resource-scoped policies instead of account-wide AdministratorAccess.
OAuth grants
Read-only scopes when write access is unnecessary.
Containers & hosts
Non-root processes, dropped capabilities, limited volumes.
Data access
Row/tenant filters so operators see only assigned records.
From standing rights to minimal rights
Discover who can do what
Inventory roles, group memberships, keys, and OAuth grants.
Identify unused and excessive access
Find privileges never exercised and dual-purpose admin accounts.
Refactor into baselines + elevation
Create minimal default roles; move admin into JIT or PAM flows.
Enforce at every decision point
APIs, cloud policies, and databases deny by default.
Review continuously
Certify access, expire grants, and shrink scopes that grow back.
Privilege models compared
| Model | Default posture | Risk if neglected |
|---|---|---|
| Standing admin | Always elevated | Immediate takeover impact |
| Role-based least privilege | Job-function roles | Role creep over time |
| JIT least privilege | Elevate briefly | Weak approvals / long TTLs |
| Attribute / policy based | Context-aware allow | Complex policy bugs |
Implementation checklist
- Deny by default in application authorization and cloud IAM.
- Separate daily-driver accounts from privileged admin identities.
- Prefer just-in-time elevation over permanent admin group membership.
- Issue distinct machine identities per service with tiny scopes.
- Expire temporary access automatically; never rely on humans to remember.
- Run access reviews for sensitive roles and third-party OAuth apps.
- Monitor unused privileges and remove them on a schedule.
- Apply least privilege to break-glass accounts: rare use, heavy monitoring.
The practical takeaway
Least privilege shrinks what a compromised identity can do. It is the difference between a stolen laptop reading one project and a stolen laptop owning the company.
Make minimal access the default, elevate briefly when needed, and keep reviewing—because privilege always tries to grow back.
Related security terms
Just-in-Time Access (JIT)
Operational pattern that enforces least privilege over time.
Privileged Access Management (PAM)
Controls for administering elevated access under least privilege.
Authorization
Mechanism that enforces privilege decisions at runtime.
OAuth Scope
Delegated permission labels that should follow least privilege.
Identity and Access Management (IAM)
Program that implements least privilege across identities.
Frequently asked questions
What is least privilege in simple terms?
Give people and programs only the access they need to do their job—nothing extra—and remove it when they no longer need it.
Why does least privilege matter during a breach?
Stolen credentials or malware inherit whatever rights the victim has. Smaller privileges mean smaller blast radius.
Is least privilege only for administrators?
No. It applies to everyday users, service accounts, CI pipelines, OAuth grants, containers, and cloud roles.
How is least privilege different from zero trust?
Zero trust is a broader architecture of continuous verification. Least privilege is a core policy outcome zero trust aims to enforce.
What causes privilege creep?
Temporary access that never expires, copied ‘same as’ role requests, shared admin groups, and missing access reviews.
How do you implement least privilege practically?
Start with deny-by-default, use role/attribute policies, prefer JIT elevation, split duties, review entitlements, and monitor unused permissions.
Does least privilege hurt productivity?
Poorly tooled, yes. With self-service requests, fast approvals, and JIT, teams often move faster because access is clearer and safer.
References
Explore authoritative guidance and frameworks related to least privilege.
Explore every security definition
Return to the glossary to search by term, alias, starting letter, or security category.