Role Based Access Control Flashcards
What is RBAC
- It is a method for controlling access based on roles assigned to users and it is most commonly used within organisations
- Organisations can decide which user gets what role, and then each of them gets their own privileges.
What is a role
Roles are a collection of pre-defined privileges or permissions bound to a resource.
It follows that a users assigned role determines the permissions that the individual is granted.
RBAC Benefits
- Improving operational efficiency
- Enhancing Compliance
- Giving Administrators Increased Visibility
- Reducing costs
- Decreasing Risk of breaches and data leaks
Applying RBAC steps
1 Understanding business needs
2 Planning the scope of implementation
3 Defining Roles
4 Implementations
RBAC Issues
- Role Explosion
- Security risk tolerance
- Scalability and Dynamism
- Expensive and difficult implemenation
RBAC alternatives
- Access control list
- Attribute based access control
Understanding business needs
- A comprehensive analysis should be conducted to examine job functions
- Regulatory or audit requirements should be considered and current security posture of the organisation assessed.
Planning the scope of implementation
- The requirements should be identified and implementation planned to align with organisational needs.
- Scope should be narrowed to focus on systems or applications that store sensitive data
Defining roles
- Roles are defined once needs analysis has been performed and how individuals perform their tasks is understood.
Implementation
- Rolling out the RBAC within systems.
- Best done in stages to avoid disruption to business.
Access control list (ACL)
- It is a table listing permissions attached to computing resources.
- Tells OS what users can access an object.
RBAC vs ACL
RBAC is more effective on a large organisational level, but ACL is better at an individual level and for low-level data.
Attribute Based Access Control (ABAC)
- It evaluates a set of rules and policies to manage access rights for specific attributes.
- Applies Boolean logic to grant and deny access to users based on a complex evaluation of the users attributes
RBAC vs ABAC
- RBAC relies on pre-defined roles, ABAC is more dynamic and uses regulation-based access control
- ABAC executes a more complex search and requires more power an time, only used when RBAC is insufficient.
e.g RBAC gives access to all managers but ABAC policy will only grant access to managers in the financial department.
Role Explosion
- This occurs when the difference in roles becomes too detailed.
- Difficult to manage and costly to manage as new roles require more monitoring
- This creates more issues: a user has too many roles assigned to them