What is the principle of least privilege?

Why does it matter?

Access that is not needed is access an attacker can use. If a stolen credential can only read one table, the harm is small. If it can change everything, one mistake or one breach can take down the whole system.

What are examples?

A database account for a reporting tool that can only read. A deployment pipeline that can update one service and not the whole cloud account. A support agent who can see tickets but not payment details. A container that runs without administrator rights.

How do you apply it?

Start with no access and add what is required. Group permissions into roles that match real jobs, avoid shared accounts, and give high-power access only for a limited time and with approval. Prefer short-lived credentials to permanent keys.

How do you keep it from eroding?

Access tends to grow and rarely shrinks. Review who has what on a schedule, remove access when people change roles or leave, and check for unused permissions. Log use of powerful accounts.

How does it relate to zero trust?

It is one of its core ideas. A zero trust design assumes any account could be compromised, so each one’s reach is kept small. See what is zero trust.

IICTP is an independent technical credentialing body.