Principle of Least Privilege
Version 1.0.0 · Updated 2026-07-30
CORE DEFINITION
Each module (or user) in the system can only access the minimum information and resources necessary for its legitimate purpose. No more privileges are granted. Scaffolding role: loss containment and isolation. It applies not only to IT but also to management. Do not give an intern CEO-level database permissions. This is not only to prevent insider threats, but also to limit the damage to the smallest possible scope when an account is compromised (explosion-proof cabin).
SCAFFOLDING EFFECT
Reduce cognitive load
Loss containment and isolation. It applies not only to IT but also to management. Do not give an intern CEO-level database permissions. This is not only to prevent insider threats, but also to limit the damage to the smallest possible scope when an account is compromised (explosion-proof cabin).
Anchor fast decisions
Security design principle (Least Privilege): Each subject is granted only the minimum permissions necessary to complete its tasks. The mechanism is to limit the blast radius of a single point of compromise.
MINIMUM ACTION
In progress 0/3Practice this model in one real situation:
account_treeGenealogyexpand_more
menu_bookReferencesexpand_more
Source support: Explicit
- en.wikipedia.orghttps://en.wikipedia.org/wiki/Principle_of_least_privilegeverified
PRIVATE NOTES · Only visible to you
SAVED Q&A
ENTRY Q&A · Private saving available
Ask with a clear boundary
thinkingmodels answers from published entry context only.
Your question is sent to thinkingmodels. The answer uses public entry context only.
RELATED MODELS