Comparison
Permission boundaryvsPrinciple of least privilege
Permission boundary
teams can create their own roles, and none of the roles they create can exceed the ceiling you set.
A policy that caps the maximum permissions an identity can ever have, regardless of what is granted to it. It is what makes delegating permission management safe, because it separates 'who may grant' from 'what may be granted'. Without one, giving a team the ability to create roles is equivalent to giving them administrator access, via one extra step.
Full entry →Principle of least privilege
you give the service a database user that can only read the two tables it needs, rather than the one that can drop everything.
Granting only the permissions needed for the task, for as long as they are needed. It does not prevent compromise; it bounds what a compromise reaches. The common violations are boring and universal: an admin credential in CI, a service account with wildcard permissions, a token that never expires.
Full entry →