Least privilege is a simple idea with a complicated implementation. In theory, users
should have only the access they need. In practice, defining need requires
understanding workflows, failure modes, and operational responsibility.
In Linux and platform environments, excessive privilege is often justified as a
reliability measure. Administrators are given broad access just in case. Automation
accounts are over-permissioned to avoid fragile pipelines.
The intention is stability, but the side effect is uncontrolled access expansion.
True least privilege is not achieved by aggressively removing permissions. It is
achieved by designing systems so that limited access still allows work to be done
efficiently and safely.
That usually involves clearer role boundaries, better tooling for privilege
escalation, and improved logging and review.
When least privilege is treated as an abstract principle, it fails. When it is treated
as an engineering problem, it becomes achievable.