Hi @Denny Varghese, imho the graph shows the possibility of more granular control when using ABAC - on top of existing RBAC you can specify detailed access control by comparing characteristics of the object to attributes of the operator requesting access to the object. This can be done independently of Access Group, but can use it as well. Here is an example of allowing certain AG to access data only for their respective company, but the Access When rule could check for their Department, Skill or any other property associated with OperatorID page. Hope this helps
I understand how we can use the access group with ABAC. My question is specifically on the CSSA mission where it compare RBAC and ABAC with attached image which not making any sense to me atleast.
If possible could you please read the topic ‘Attribute-based access control (ABAC) security model’ under access control mission and let us know.
@Denny Varghese Hi, you can use the Suggest an edit button below the article and ask the question directly to the content team. I was not the author and just tried reverse engineering this graph