liveBook · Manning

Principle of least privilege

As explained in Fundamentals of Cybersecurity

Least privilege is an access-control principle that grants each person, account, process, or system only the minimum permissions necessary for authorized tasks.

The principle of least privilege gives users only the permissions they need to perform their tasks. People should be able to do their jobs, but unnecessary access creates opportunities for unauthorized activity and accidental misuse. section 8.7.1 section 8.0

When an old permission stays

An employee receives access to salary information while working in HR. After moving to a finance project-management role, they receive access to financial reports but keep the salary access. Those old permissions are no longer needed. Accumulating permissions this way is called privilege creep. section 8.7.1

Least privilege guides everyday access decisions and ongoing reviews. Check whether elevated permissions are still necessary, and revoke outdated ones. Some administrators need continuing elevated access for maintenance, but that need should still be reviewed. section 10.4.4

Related access-control principles answer different questions:

  • Least privilege: What is the minimum permission needed to perform this task? section 8.11
  • Need to know: Does the person need this information for their job? section 8.11
  • Separation of duties: Should different people perform different parts of an operation? section 8.11

The principle also limits what a compromised account or process can do. Least-privilege policies can restrict who may use powerful system tools or make sensitive changes. Alongside other defenses, this helps reduce the impact of a successful exploit and address insider threats. section 12.2.5 section 12.2.4

How Fundamentals of Cybersecurity covers it

How deep it goes
Defines minimum necessary access, illustrates privilege creep, and recommends reviewing and revoking outdated permissions without detailing a full implementation procedure.
Examples
Uses an HR-to-finance role change that leaves salary access in place and restrictions on powerful system tools.
What it assumes
Introduces subjects, objects, identification, authentication, and authorization as foundations for understanding access decisions.
What you can do after
Operate/configure it by reviewing elevated permissions, revoking outdated access, and restricting sensitive actions to accounts that need them.
How it connects
Connects least privilege to access control, need to know, separation of duties, privilege creep, and privileged access management.

Also explained in

Compare how 22 books explain principle of least privilege →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Fundamentals of Cybersecurity. The section links point to the parts of the book it draws on.