Least Privilege
What is the smallest useful permission set?
Reference notes by Min · Reviewed October 11, 2026
Definition
Least privilege limits an actor’s access to what its assigned work requires.
Least privilege is an operating constraint on capability, scope and duration. Apply it to both the credential and the tool interface. A narrow credential is less useful if the agent can use another unrestricted integration to reach the same system.
What it covers
- Capability
- Which operations are exposed.
- Scope
- Which records and environments are reachable.
- Duration
- How long the grant remains useful.
Review the complete access path, including child agents, scheduled work and intermediate services. Prefer bounded operations whose parameters make the intended scope visible, rather than a broad administrative interface with instructions to behave carefully.
In practice
Practical design patterns by Min.
- Separate read, draft and publish capabilities.
- Use task-scoped access with a bounded lifetime.
- Review unused grants and avoid blanket administrator access.
Start from the minimum operations needed for one task, then add access only when the requirement is documented. Remove temporary pilot access when the task or experiment ends.
Measure unused permissions and denied attempts. Use that evidence to refine grants, while distinguishing a missing legitimate permission from an attempt to exceed the task.
Working example
A supplier comparison
An assistant compares approved suppliers.
- Allow reading the approved supplier list.
- Exclude payment and order-placement tools.
- Expire access when the comparison finishes.
Why the controls matter
A drafting assistant can produce a proposed email without unrestricted mailbox sending. If delivery is later needed, make it a separate operation with a recipient-bound approval and a limited grant.
Common pitfalls
- Granting a general shell when one narrow tool is enough.
- Leaving temporary access in place indefinitely.
A read-only label is incomplete if the workflow can trigger writes indirectly through another service. Follow actual effects and alternative access paths.
Questions for operational review
Use these questions to decide what evidence your team needs. They are editorial prompts, not a compliance checklist.
- What access is unused?
- How long does a grant last?
- Can another tool bypass the intended limit?
Articles linking here
References
Primary documents reviewed for this entry. Examples and implementation patterns are editorial synthesis.
- NIST CSRC: Least privilege ↗Accessed October 11, 2026