Role-Based Access Control (RBAC)

With role-based access control (RBAC), it is a user’s function that determines their privileges. Permissions may include access, read, write, share, and decide.

Roles can be assigned by authority or level in the organization, responsibilities, and/or skill competencies. With a role hierarchy, one type of role may include the attributes of many other individual roles.

Simplify user provisioning and management

Apply privileges that conform to a person’s role vs. establishing and managing user permissions individually.

Increase IT efficiencies

Realize systematic and repeatable user permissioning. Apply permission changes for many users at once by altering role privileges.

Facilitate user onboarding

Add and manage users easily and effectively based on their role.

Reduce risk

Avoid provisioning user privileges individually to reduce the potential for error. Easily audit user permissions and address any issues.

Realize least privileged access

Assign users the fewest number of permissions necessary to perform their role.

Enable API-based role provisioning

Implement user roles across APIs.

Attribute-based access control, or ABAC, exponentially increases your permissioning options with the addition of specific attributes, such as user location or time of day.

While infinitely more flexible than RBAC, this flexibility also adds complexity that can increase risk if not implemented and managed properly. One of our cybersecurity experts would be happy to discuss whether RBAC or ABAC is the better fit for your requirements.