<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Best practice - various different account types now in pCloud which required Discovery , Reconcilation , ephemeral account to works specially in Windows in Privilege Cloud Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/best-practice-various-different-account-types-now-in-pcloud/m-p/1295892#M34</link>
    <description>&lt;P&gt;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.&lt;/P&gt;</description>
    <pubDate>Thu, 23 Apr 2026 21:11:32 GMT</pubDate>
    <dc:creator>ba31</dc:creator>
    <dc:date>2026-04-23T21:11:32Z</dc:date>
    <item>
      <title>Best practice - various different account types now in pCloud which required Discovery , Reconcilation , ephemeral account to works specially in Windows</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/best-practice-various-different-account-types-now-in-pcloud/m-p/1295890#M32</link>
      <description>&lt;P&gt;Since the launch of CyberArk Privilege Cloud, multiple privilege accounts are required to support different platform capabilities. For example:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;SaaS Discovery requires a domain account with local administrator privileges on target Windows servers so it can preform discovery of accounts on target server.&lt;/LI&gt;&lt;LI&gt;Strong Accounts (SIA) require local administrator rights to create and clean up ephemeral local accounts and remove residual user profiles.&lt;/LI&gt;&lt;LI&gt;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.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This raises an important design question:&lt;/P&gt;&lt;P&gt;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 ?&lt;/P&gt;</description>
      <pubDate>Thu, 19 Mar 2026 19:32:41 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/best-practice-various-different-account-types-now-in-pcloud/m-p/1295890#M32</guid>
      <dc:creator>ba31</dc:creator>
      <dc:date>2026-03-19T19:32:41Z</dc:date>
    </item>
    <item>
      <title>Re: Best practice - various different account types now in pCloud which required Discovery , Reconcilation , ephemeral account to works specially in Windows</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/best-practice-various-different-account-types-now-in-pcloud/m-p/1295891#M33</link>
      <description>&lt;P&gt;Hey @ba31 ba31​&amp;nbsp;The Strong account best practices can be found here:&lt;/P&gt;&lt;P&gt;https://community.cyberark.com/s/article/Best-Practices-for-Securing-Windows-Domain-Strong-Accounts&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 01 Apr 2026 16:42:08 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/best-practice-various-different-account-types-now-in-pcloud/m-p/1295891#M33</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2026-04-01T16:42:08Z</dc:date>
    </item>
    <item>
      <title>Re: Best practice - various different account types now in pCloud which required Discovery , Reconcilation , ephemeral account to works specially in Windows</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/best-practice-various-different-account-types-now-in-pcloud/m-p/1295892#M34</link>
      <description>&lt;P&gt;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.&lt;/P&gt;</description>
      <pubDate>Thu, 23 Apr 2026 21:11:32 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/best-practice-various-different-account-types-now-in-pcloud/m-p/1295892#M34</guid>
      <dc:creator>ba31</dc:creator>
      <dc:date>2026-04-23T21:11:32Z</dc:date>
    </item>
  </channel>
</rss>

