Role-Based Access Control (RBAC) Explained: How it works and when to use it

Role-Based Access Control (RBAC) is a popular model for access control in large organizations. The reason for this is that it scales well and is a good fit for the access control needs of many large organizations. RBAC is not the only access control model out there, but it is a very popular one.
In this video we walk through the main concepts of RBAC, which are capabilities, permissions, roles, and users. We also discuss the relationships between these concepts, for example the fact that users can play multiple roles.
Last but not least, we point out some alternatives such as Access Control Lists (ACL) and Attribute-Based Access Control (ABAC).

0:00 Role-Based Access Control (RBAC) Introduction
0:41 RBAC Model: Capability
0:57 RBAC Model: Permission
1:45 RBAC Model: Role
2:25 RBAC Model: User
3:38 RBAC Relationships: User
3:47 RBAC Relationships: Role
4:18 RBAC Relationships: Permission
5:00 RBAC Relationships: Capability
5:49 Enterprise-level Access Control

[aamirraza]

Very helpful video, May God bless you with love, care and mercy.

[srinivasann]

RBAC explained very precise and easily understandable.

[RITCHIECOREY]

Excellently laid out presentation! Very approachable and immediately helpful in unraveling my confusion about where exactly does RBAC fit into the overall access model :-)

[lifestyle_with_raj]

Thanks erik, this video is helpful, Short but well explained!

[Just_too_busy]

thank's a lot!. i Found in your video all the main answers i've needed

[CSouza-xmrp]

Clear explanations, amazing video! Thanks!

[dsulvadarius]

I liked your video halfway through watching it. Good work.

[someutubchannel]

Great topic,
Could you do a video with 'real life' examples & how they would be implemented in a SQL database?

[niioizin]

thanks for the explanation. It helps immensely.

[ezenwajoy]

Thank you so much Mr. Erick for this seamless explanation on RBAC. My question is, is RBAC a software or a programme. what is it exactly? Thank you.

[charlescampista]

Thank's bro! It has helped me a lot!

[mmkmur]

Excellent .. Slide online link is broken. Could you please share the updated link or a copy? Thanks

[jayanthpatki]

I'd assume that one role could be shared by multiple users. So that makes it a many-many relationship. Same applies to the next two relations.

[AWaterKnight]

Is there a difference between capabilities and resources here? Because in capability lists, a capability denotes a pair of object and access right.

In the multi mapping between permissions and capabilities, it becomes blurry, because a permission could be atomic. The permission could also be viewed as for the individual resource/capability, in the example, one permission could govern one system, the other system could be a separate permission.

[tomatte]

looks like a many to many relation ship
user - role
role - permission