Glossary
Least privilege
Least privilege is the practice of granting each account, service or process only the permissions it needs for its task, and nothing more.
Updated 2 Sept 2026
In detail
The principle predates modern security architecture and applies at every layer: operating system users, database roles, cloud IAM policies, CMS roles and API tokens. Its practical form is usually role-based access plus time-bounded elevation, because permanent administrator rights are the single biggest multiplier on the impact of a stolen credential.
Why it matters
Least privilege does not prevent compromise; it caps the blast radius. A content editor account that cannot install plugins cannot be used to plant a backdoor, and a scoped deploy token that cannot read secrets is worth far less to an attacker. It also makes anomalous activity easier to spot, since routine work no longer runs as an administrator.
Examples
- Giving CMS authors an editor role rather than administrator, so plugin installation is unavailable.
- A deployment token scoped to one repository and one action instead of an organisation-wide personal access token.
- A database user with read access to reporting views only, used by the analytics job.