CyberArk admin account

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

CyberArk admin account

L2 Linker

Hello All,

We have an admin account in our ISPSS environment. This account has full access to all the safes and is considered a break glass account meaning whenever our external IDP is down, we can use this _admin account (bypass MFA) to log in to CyberArk and retrieve an account secret. CyberArk recommends restricting the day-to-day operations on this account BUT we will have to use this account to move an account between safes, to create an application ID (assign the application ID to the target safes).

Is there a better way to handle these general admin operations while minimizing the use of the admin account? I'm leaning towards implementing a PSM web connection for this admin account so that authorized personnel can launch the PVWA session using this account, at least the activities will be monitored via PSM

 

Thanks!

5 REPLIES 5

L4 Transporter

If you are not the only admin there and/ or obey zero-trust policy, onboarding the admin account into the PAM and using it only via PSM is the best option.

But if you auto-rotate its password using CPM it will not be break-glass solution as you will need to log into PVWA with your user to retrieve the admin's password.

L2 Linker

@Korneliusz Lis​ sure, Thanks!. I'm trying to setup the PSM web app connector (PSMIdentitySecurity) for 'subdomain_admin' account. Are there any specific validations that need to be verified for this setup?

Isn't there a built-in connection component (and the platform) for that connection in your environment?

If not, it should be in the CA Marketplace.

L4 Transporter

Hi @Sudeshnu Santho Chandravamsam​ 

 

It seems that korneliusz.lis_CYBR provided an answer to your question. Could you kindly let us know if this solution helped?

If so, please mark the answer as 'Select as Best' to assist other community members.

 

Thank you, Liad

L0 Member

Use role-based admin accounts instead of relying on the _admin account by creating custom roles such as VaultAdmin, AppIDManager, or SafeAdmin with limited, scoped permissions. Assign these roles to named user accounts through CyberArk Identity (ISPSS) groups or CyberArk RBAC. These role-based accounts can handle safe creation, account moves, application ID management, and permissions assignment, ensuring better control, auditability, and adherence to the principle of least privilege.

  • 16 Views
  • 5 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!