Least Privilege: Why Should Access Be Limited to What a Task Needs?

Least privilege means giving a person, account, program or agent only the access required for the task at hand. Someone asked to edit one document need not receive access to an entire cloud drive; an app allowed to read photos does not therefore need permission to delete contacts.

The idea is often mistaken for distrust. It is not a judgement about character, but a way of limiting consequences. Trustworthy people still click the wrong thing, and dependable software can contain defects. The broader the permission, the wider the damage from one mistake or exploit. Least privilege replaces the hope that nothing will go wrong with a structure in which an error cannot easily cross its boundary.

It is also more precise than simple restriction. A restriction says what cannot be done; least privilege must also identify what the task genuinely requires. Access so narrow that work becomes impossible is another design failure. Nor should permission remain fixed forever: temporary access should be withdrawn when the task ends and reconsidered when the task changes. The concept therefore connects security, responsibility and reversibility. Good authorisation enables action while keeping its limits clear.