Alternative for Object Level Access Control?

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

Alternative for Object Level Access Control?

L4 Transporter

Hello Everyone! We looked in the documentation of Privileged Cloud (PC) and we are not able to find any thing regarding object level access control. Is there any way to use this setting in PC or is there any alternative for this?

 

Any help is much appreciate it, thank you!

1 accepted solution

Accepted Solutions

L6 Presenter

It isn't an easy answer, but the alternative for OLAC is simply to create more safes. Depending on how many accounts and how many different permissions are defined in an OLAC safe will really define the scope of the problem.

 

For example, if you had a single OLAC safe that held 500 domain admin accounts assigned to individuals, then you would need to create 500 Safes - one for each individual who has a domain admin account. That would then allow you to define permissions on each safe so only the individual user has permissions over the account.

 

The situation is often less clear than that, so the solution is to analyze what is inside your OLAC safes and ultimately decide how many individual safes need to be created to replace it. If you have not been performing good hygiene on the OLAC safe, then this may be difficult to assess (e.g. identifying groups of accounts that have the same permissions may be more difficult).

 

If you were to migrate to Privilege Cloud, OLAC is not supported and you would likely be performing the process above during your pre-migration phase.

View solution in original post

1 REPLY 1

L6 Presenter

It isn't an easy answer, but the alternative for OLAC is simply to create more safes. Depending on how many accounts and how many different permissions are defined in an OLAC safe will really define the scope of the problem.

 

For example, if you had a single OLAC safe that held 500 domain admin accounts assigned to individuals, then you would need to create 500 Safes - one for each individual who has a domain admin account. That would then allow you to define permissions on each safe so only the individual user has permissions over the account.

 

The situation is often less clear than that, so the solution is to analyze what is inside your OLAC safes and ultimately decide how many individual safes need to be created to replace it. If you have not been performing good hygiene on the OLAC safe, then this may be difficult to assess (e.g. identifying groups of accounts that have the same permissions may be more difficult).

 

If you were to migrate to Privilege Cloud, OLAC is not supported and you would likely be performing the process above during your pre-migration phase.

  • 1 accepted solution
  • 371 Views
  • 1 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!