Best practice - various different account types now in pCloud which required Discovery , Reconcilation , ephemeral account to works specially in Windows

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

Best practice - various different account types now in pCloud which required Discovery , Reconcilation , ephemeral account to works specially in Windows

L4 Transporter

Since the launch of CyberArk Privilege Cloud, multiple privilege accounts are required to support different platform capabilities. For example:

  • SaaS Discovery requires a domain account with local administrator privileges on target Windows servers so it can preform discovery of accounts on target server.
  • Strong Accounts (SIA) require local administrator rights to create and clean up ephemeral local accounts and remove residual user profiles.
  • In environments still using local administrators instead of domain‑based admin groups, an additional domain account is required to reconcile and manage local administrator membership.

 

As a result, the Privilege Cloud solution introduces multiple privilege account and operational accounts, many of which require administrator‑level access on the same target servers.

 

This raises an important design question:

Does CyberArk recommend a best‑practice model or decision matrix that defines when service account duties can be safely combined (for example, combining SIA Strong Accounts with reconcile accounts), and when they must remain strictly separated on Windows targets such as reconcile account with discovery account ?

2 REPLIES 2

L5 Sessionator

Hey @ba31 ba31​ The Strong account best practices can be found here:

https://community.cyberark.com/s/article/Best-Practices-for-Securing-Windows-Domain-Strong-Accounts

 

The documents provided focus primarily on Strong Account Practices; however, my question relates to the overall CyberArk Privileged Cloud solution. This is because a complete implementation must address multiple types of privileged accounts that needed to implement, each requiring appropriate onboarding and control within the solution.The examples referenced earlier should be taken into account when defining how customers are expected to follow and adopt CyberArk best practices as part of the overall Privileged Cloud solution.

  • 50 Views
  • 2 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!