Assets for RBAC/ABAC?

[derekoha]

We currently use Entra ID groups to define what applications users have access to, and usually try to use their job title (e.g. Project Manager) to create dynamic groups that enable access to enterprise applications.

We want a more granular level of ABAC, without having to change their job title.

I was thinking that, in Assets, we could create the concept of "Role", and then map these to people that have that role (e.g. Agile Project Manager). That "Role" could then be used to populate Entra ID groups with the list of people mapped to it.

Is this a good use of Assets, and a good way to achieve ABAC?

[Marc -Devoteam-]

Hi @derekoha 

Welcome to the community

This is not the way to use assets, assets is a CMDB or ITAM.

This information can't be used for application based access, as its part of the application.

Or am I misunderstanding you, can you clarify maybe be providing a mockup of your idea?