Privilege Level
How much direct access to core resources a piece of software is trusted with.
Glossary
Least Privilege
The principle of granting each piece of software only the access it truly needs.
In one line
The principle of granting each piece of software only the access it truly needs.
Also calledminimal access
Least privilege is a quiet discipline: give nothing more access than its task requires. If a translator only needs to speak for one component, it has no business reaching into anything else, and a careful system makes sure it cannot.
Following this principle limits how much can go wrong. A mistake stays small because the software was never handed the means to cause a larger one. Damage is naturally confined to the narrow area the software was allowed to touch.
The principle applies whether a fault is accidental or deliberate. Code that is given little reach can do little harm, so even if something goes badly wrong, the consequences are kept within tight bounds rather than spreading freely.
Applying least privilege takes thought, because it means understanding exactly what each piece of software needs and granting no more. It is a little more work upfront, but it pays off as a steadier, safer system that contains its own mistakes by design.
In practice
In practice, least privilege is like giving a house guest a key to the front door but not to every room. They can do what they came to do without being able to wander everywhere. Software is treated the same way: just enough access for the task, and nothing beyond it.
