- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
03-12-2025 06:41 AM
We are a little over a year into our CyberArk journey and are trying to mature some of our practices. One area we struggle with is safe organization/permissions.
We are an agile shop and at times users need access to different accounts within CyberArk, so we end up having to create new safes and move accounts into them to avoid granting over-permissions.
A thought that has come to mind is creating a safe for each account to grant us the ability to control access on a per-account (or safe) basis without having to move the account to a new safe each time. This also stops the account ID from changing, which we leverage regularly with automation.
Has anyone else had experience going down this 1 to 1 (account to safe) ratio path? And if so, was it a nightmare?
Appreciate any thoughts or suggestions that others have.
03-12-2025 09:18 AM
It really sounds like a significant operational overhead to map accounts -> safes 1:1. It sounds something akin to OLAC which I would NEVER recommend because of the operational overhead.
I'm not really sure what the issue is with over-permissions here, but from what you are describing it may be that once a user is granted access to a safe then they have both Use and Show permissions, thus effectively granting them full access to the target systems.
A couple of approaches might assist that are fairly common patterns. At a very high level really
03-12-2025 09:18 AM
It really sounds like a significant operational overhead to map accounts -> safes 1:1. It sounds something akin to OLAC which I would NEVER recommend because of the operational overhead.
I'm not really sure what the issue is with over-permissions here, but from what you are describing it may be that once a user is granted access to a safe then they have both Use and Show permissions, thus effectively granting them full access to the target systems.
A couple of approaches might assist that are fairly common patterns. At a very high level really
03-12-2025 03:09 PM
Appreciate the reply, as well as the approaches to consider.
The over-permissioning comes into play when adding a new user to an existing safe. For example:
Safe 01 - holds:
Account 01
Account 02
Account 03
If a new user needs access to only Account 02, I would need to move it to it's own safe, to avoid granting access to Account 01 and Account 03 as well.
03-13-2025 12:11 AM
Object Level Access Control
The Privileged Access Security solution provides granular access control for passwords and files that are stored in the Vault. Object level access enables you to control who can retrieve and use specific passwords and files in the Safe, regardless of Safe level member authorizations. For example, an external vendor or technician can be given retrieve or use authorizations for a specific password which he will be able to use without being aware of any other passwords or files in the Safe. (supported in Self hosted CyberArk)
The above option is not recommended as @Jon Musker mentioned.
But this is not supported in PCloud CyberArk.
For your scenarios, you can opt for safe creation per team wise and load their accounts in the same safe with Dual control enabled in case account has admin level access
03-13-2025 02:31 AM
I would look at privileged access in terms of categorising the types of access (effectively risk levels), and also the controls that we have. Then draw up a matrix of which controls are required for which types of access. Then the safe structure and policies will follow from your matrix.
Example:
Types of access
Types of control
etc
03-16-2025 06:33 PM
@T R With all the suggestions and good recommendations provided here, I would also like to suggest trying a workflow. In that case, you can list the accounts in the user's account list, but only the required user will get access with approval.
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!

