Skip to content

Commit c170caa

Browse files
Improve role-based-access-control.md
Improved version of the definition with a better flow and clarity. Signed-off-by: Julia Furst Morgado <[email protected]>
1 parent 13e2039 commit c170caa

File tree

1 file changed

+10
-12
lines changed

1 file changed

+10
-12
lines changed

content/en/role-based-access-control.md

Lines changed: 10 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -7,22 +7,20 @@ tags: ["security", "", ""]
77

88
## What it is
99

10-
Role-Based Access Control (RBAC) is a method used to regulate access to systems and resources based on user roles within an organization.
11-
Each job function is associated with specific roles and permissions.
12-
For example, a member of the marketing team may be granted permission to view sales deals in the pipeline (*read* permission) but is restricted from making edits (*write* permission).
13-
Different permissions are assigned to roles in sales, marketing, and similar distinctions apply within engineering teams.
10+
Role-based access control (RBAC) is a security method of managing user access to systems, networks, or resources based on their role within a team or a larger organization.
11+
RBAC empowers IT administrators to identify the necessary level of access for all users with a particular job function and assign those users a role with a predefined set of permissions.
12+
Organizations utilize RBAC to provide their employees with varying levels of access tailored to their roles and responsibilities.
1413

1514
## Problem it addresses
1615

17-
Individually managing access permissions for multiple users across a variety of system resources and data can be a complex task.
18-
Each user typically requires access to a different set of specific resources.
19-
Let's consider an organization with 500 developers (users) and 300 resources with varying permission levels (read, write, and no access).
20-
The administrator must ensure that each user is granted the correct permissions for all 300 resources.
21-
RBAC simplifies this process by providing predefined access control based on role groups.
16+
RBAC addresses the challenge of controlling the resources team members and applications can access,
17+
as well as the actions they can perform, especially as the number of applications and team members increases.
18+
Administrators must ensure that each user has the correct permissions for the resources they need to access,
19+
a task that can become cumbersome and error-prone without a structured access control mechanism.
2220

2321

2422
## How it helps
2523

26-
RBAC offers precise control over user permissions within software systems.
27-
Depending on their roles, team members can modify a section, view it exclusively, or be completely restricted from accessing it.
28-
This granular permission allocation enables team members with distinct roles to collaborate on the same system while minimizing security risks.
24+
RBAC provides IT teams with the capability to easily manage permissions for all users in a group simultaneously or make swift adjustments to an individual user's access level by assigning or removing a role.
25+
This safeguards sensitive data and ensures that employees can only access information and perform actions necessary for their job responsibilities.
26+
Overall, RBAC enhances access management, bolsters security, and boosts operational efficiency within organizations.

0 commit comments

Comments
 (0)