liveBook · Manning

Role-based access control

As explained in Fundamentals of Cybersecurity

Role-based access control is an access control model in which permissions are assigned to organizational roles and users receive access through their assigned roles.

Role-based access control (RBAC) assigns permissions to organizational roles instead of individual users. Users receive access through role membership, so administrators can match permissions to job functions and manage access consistently. section 10.2.3 section 10.2

RBAC helps organizations manage access at scale while supporting least privilege. A role should provide the resources and actions needed for a responsibility, not every permission a person might otherwise accumulate. section 10.2 section 10.2.3

RBAC across departments

An organization might assign HR access to employee records, IT access to configurations and troubleshooting tools, and Finance access to accounting and budgeting systems. Each group is denied unrelated systems, aligning access with departmental duties. section 10.2.3

Manage RBAC with these practical considerations:

  • Define roles around job functions and configure each role with the permissions required for its responsibilities. section 10.2.3
  • Review role assignments when responsibilities change; failing to remove old permissions causes privilege creep. section 10.2.3
  • Monitor access activity because excessive privileges can enable misuse, accidental exposure, or unauthorized access. section 10.0 section 10.5
Figure 10.1 Summary of access control models arranged by decision authority

Compare RBAC with discretionary and mandatory access control by examining who makes access decisions and how permissions are enforced. section 10.2

How Fundamentals of Cybersecurity covers it

How deep it goes
Explains role assignment, departmental permissions, least privilege, privilege creep, and monitoring, but stops short of implementation procedures.
Examples
Uses HR, IT, and Finance roles to demonstrate separated permissions and uses role changes to illustrate privilege creep.
What it assumes
Assumes basic awareness of users, permissions, and digital resources while introducing logical access control models through workplace examples.
What you can do after
Apply it by assigning users to job-based roles, limiting permissions, reviewing changes, and monitoring access for misuse.
How it connects
Connects RBAC with logical access control, authorization, least privilege, privilege creep, identity management, DAC, MAC, ABAC, and PBAC.

Also explained in

Compare how 17 books explain role-based access control →

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.