Meaning
The Principle of Least Privilege states that a subject should be given only the permissions essential to perform its tasks. It reduces the attack surface by limiting what code or users can do if compromised. It is applied whenever a system assigns access rights, creates roles, or runs processes with elevated capabilities.
Primary Function
Access control
Communicative Purpose
Ensures that entities receive only the minimal permissions required, preventing unnecessary privilege escalation.
Pattern
design system → assign minimal required permissions → enforce least privilege
Função primária
Access control
Propósito comunicativo
Ensures that entities receive only the minimal permissions required, preventing unnecessary privilege escalation.
Situações de gatilho
Web application: assigning user roles during registration; Operating system: launching a service with reduced rights; Cloud infrastructure: provisioning IAM policies for microservices
Contextos
Enterprise applications, operating system services, cloud platforms, container orchestration, security frameworks
Padrão
design system → assign minimal required permissions → enforce least privilege
Colocados típicos
- role
- permission
- access
- policy
- privilege
- grant
- deny
Substituições comuns
- grant admin rights instead of specific permissions → over‑privilege risk
- use group memberships as a shortcut → may hide excessive rights
Erros comuns
Assigning broad admin roles to developers → leads to unnecessary access; Forgetting to revoke temporary privileges after task completion → leaves elevated rights lingering; Assuming default permissions are minimal without verification → results in hidden over‑privilege
Similar / contraste
Defense in depth – broader layered security vs. least privilege focuses on minimal rights; Need‑to‑know – information restriction vs. least privilege applies to any capability
Interferências
Coming from Windows: using 'Run as administrator' by default → forget to drop privileges in Linux where unprivileged users are the norm; Coming from JavaScript: relying on sandboxed iframes instead of explicit permission checks → may miss OS‑level privileges
Família do chunk
- defense in depth
- role‑based access control
- need‑to‑know
Nuance
Do not apply least privilege when performance-critical code requires frequent privilege changes, as switching contexts can be costly; Reducing privileges may introduce additional permission checks that slightly increase latency; In environments with dynamic permission requirements, over‑restricting can cause functional failures if needed rights are omitted
Efeito pragmático
Properly applying least privilege limits the impact of compromised accounts, reduces insider threat vectors, and simplifies compliance audits.
Dica de memória
Think of a keycard that opens only the doors you need, not the entire building.
Nota
Often combined with role‑based access control (RBAC) to manage groups of permissions efficiently.
Upgrade path
Implement role‑based access control (RBAC) with fine‑grained policies
Log in to save chunks.