DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Zones

Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks

Low-Code Development: Leverage low and no code to streamline your workflow so that you can focus on higher priorities.

DZone Security Research: Tell us your top security strategies in 2024, influence our research, and enter for a chance to win $!

Launch your software development career: Dive head first into the SDLC and learn how to build high-quality software and teams.

Open Source Migration Practices and Patterns: Explore key traits of migrating open-source software and its impact on software development.

Related

  • Effortless Credential Management in Azure: The Power of Managed Identities
  • From Novice to Expert: Building Robust Security With Kubernetes RBAC
  • Best Practices To Secure Stateless REST Applications
  • Securing the Keys to the Kingdom: Exploring the Depths of Privileged Access Management (PAM)

Trending

  • Partitioning Hot and Cold Data Tier in Apache Kafka Cluster for Optimal Performance
  • Difference Between App Development and IaC CI/CD Pipelines
  • Explainable AI: Seven Tools and Techniques for Model Interpretability
  • From JSON to FlatBuffers: Enhancing Performance in Data Serialization
  1. DZone
  2. Software Design and Architecture
  3. Integration
  4. Fundamentals of an Enterprise Role-Based Access Control (RBAC) System

Fundamentals of an Enterprise Role-Based Access Control (RBAC) System

Learn how to use RBAC to restrict access to your enterprise systems, and keep your corporate data safe from cyberattacks.

By 
Justin Baker user avatar
Justin Baker
·
Jun. 10, 17 · Tutorial
Like (4)
Save
Tweet
Share
6.0K Views

Join the DZone community and get the full member experience.

Join For Free

Role-Based Access Control (RBAC) is an approach to restricting system access to users based on defined roles. Many companies have built internal systems like these, but usually in a very archaic and haphazard way.

There are a few primary semantics to a role and a set of attributes, operators, and actions that define a role. 

Image title

Defining a Role

A role should have five semantic components:

  • Name - a human readable and business-friendly way to identify a role.

  • Description - the role's purpose, clearly defined.

  • Tags - important for managing multiple roles and creating roles to manage to roles.

  • Assignments - assigning roles to individuals or groups of individuals.

  • Policies - specific rules and permission sets assigned to a role.

Defining a Policy

A policy has one primary component:

  • Array of Statements - a policy can have many statements. You should be able to save policies and re-use them across multiple roles. In other words, a policy is a collection of specific permission rules.

Defining a Statement

A statement has three components:

  • Resource - the targetted feature, environment, or operation.

  • Effect - typically "Allow" or "Deny".

  • Action - a resource can have many actions, like deleteUser, addUser, modifyUser.  These actions should have human-readable names, like "Delete a User" for "deleteUser." This is essential when you get into more complex actions, like "Modify Image Upload" for "imgUploadMod."

  {
    "effect": "deny",
    "resources": [
      "prod/primaryDB/*"
    ],
    "actions": [
      "deleteDB"
    ]
  }


Mapping Roles

You should be able to assign multiple roles to an individual user. Ideally, you would have a clear user interface that allows you to build these roles and attach them to individual users or groups of users.

Avoiding Technical Debt

It is very common amongst large companies to accrue hundreds or thousands of roles over time. Having an intuitive GUI lets you manage this debt, keep your roles up-to-date, and keep your system secure.

Role-based access control

Published at DZone with permission of Justin Baker, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Related

  • Effortless Credential Management in Azure: The Power of Managed Identities
  • From Novice to Expert: Building Robust Security With Kubernetes RBAC
  • Best Practices To Secure Stateless REST Applications
  • Securing the Keys to the Kingdom: Exploring the Depths of Privileged Access Management (PAM)

Partner Resources


Comments

ABOUT US

  • About DZone
  • Send feedback
  • Community research
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 100
  • Nashville, TN 37211
  • support@dzone.com

Let's be friends: