What to know
- Scope access by task, resource and duration.
- Separate reading from consequential changes where practical.
- Permissions need review after roles, tools or requirements change.
The meaning
Least privilege means limiting a person’s or process’s permissions to what its assigned work requires. NIST’s glossary describes this as a security principle applied to both users and systems acting for them. In practice, the question is not simply whether an account is an administrator. It is which records it can read, which actions it can perform and how long that authority remains useful. A narrow permission can still be excessive if it covers the wrong resource.
Read, draft and act are different needs
An editorial assistant preparing a research brief may need public sources and a draft location. It does not automatically need subscriber records, payment access or permission to publish. A staff editor may need publication rights without the ability to create new owners. Separating those responsibilities makes the effect of a mistake easier to limit. The organization should still explain how legitimate work is completed, so staff do not resort to shared unrestricted accounts simply to get past unclear restrictions.
Use a task-shaped example
Suppose a temporary automation reads article metadata to build an internal report. A useful grant would identify the publication, permitted fields and expiry. It would exclude unrelated message bodies and write operations. When the report is finished, access can be removed. This is an illustration, not a prescribed role for every system. The right boundary depends on the actual task and on whether the application can enforce the desired scope.
Keep the principle operational
Review access after a role change, a new integration or a revised purpose. Test denied behavior as well as a legitimate action, and keep a recovery path for accidental removal of necessary access. A policy document alone does not prove that deployed permissions match it. Conversely, repeated permission errors can reveal a badly defined task rather than a reason to grant everything. Least privilege is useful when it leaves an understandable, enforceable relationship between work and authority, with an accountable owner who can revise or revoke that authority.
References
- NIST least-privilege glossary (living reference; accessed 2026-10-16)
Editorial note: AI-assisted original educational definition reviewed 16 October 2026. Examples and reading questions are BijliCoin explanation, not a product recommendation, legal conclusion or guarantee. AI-generated conceptual illustration.
Sources & context
See our editorial policy or report a correction.
Related guides and definitions
- Review unfamiliar repositories without giving them your credentials
Use a staged review process for hiring tasks, plugins and agent-generated projects before any unknown code receives execution or network authority.
- Protect the account behind the wallet: authentication and recovery basics
Build a practical account-protection map covering unique passwords, stronger sign-in methods, sessions and the recovery path that can bypass them.
Join the conversation.
Loading reader discussion…
Sign in to like this article or add a comment. Comments are reviewed before appearing publicly.
Open the sign-in link in this same browser. Your display name is public; your email is private. Reader sign-in does not subscribe you to the newsletter. See our privacy notice.
Signed in as



