<?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: Safe naming conventions for personal privilege accounts help in Privilege Cloud Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/safe-naming-conventions-for-personal-privilege-accounts-help/m-p/1354751#M3227</link>
    <description>&lt;P&gt;Sadly Platforms To Manage isn't exposed in PCloud to end users either by configuration in pvwa or rest as far as I know. &lt;/P&gt;&lt;P&gt;It's an omission that I hope they resolve shortly as it is very handy in use cases like this.&lt;/P&gt;&lt;P&gt;I believe support can modify it, but not sure if they want to... &lt;/P&gt;</description>
    <pubDate>Tue, 11 Mar 2025 09:07:44 GMT</pubDate>
    <dc:creator>Mal</dc:creator>
    <dc:date>2025-03-11T09:07:44Z</dc:date>
    <item>
      <title>Safe naming conventions for personal privilege accounts help</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/safe-naming-conventions-for-personal-privilege-accounts-help/m-p/1354747#M3223</link>
      <description>&lt;P&gt;Was hoping I could get some inspiration/help for reformatting our safe naming policy for personal privileged accounts. Right now, its very barebones&lt;/P&gt;&lt;P&gt;EG DOMAINACRONYM-FIRST-LAST&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Our enterprise environment is such that we have ~14 different domains with varying levels of trust. So we have a lot of people who have multiple PP safes, as one is needed per domain in its own trust. I dont see any way around that since the CPM is tied to the safe. And the domains wont ever be centralized &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I want to future proof as we mature the product by adding a prefix that denotes it as PP , and perhaps dept name?&lt;/P&gt;&lt;P&gt;eg DOMAINACRONYM-PPA-DEPT-FIRST-LAST&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Pushing against the character limit. i could also add the account type&lt;/P&gt;&lt;P&gt;WIN-DOMAINACRONYM-PPA-DEPT-FIRST-LAST&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;that would cover accounts outside of the windows OS environment. EG Azure/Entra, but leaving little space for people's actual names. &lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thoughts?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 10 Mar 2025 19:30:36 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/safe-naming-conventions-for-personal-privilege-accounts-help/m-p/1354747#M3223</guid>
      <dc:creator>SFazio</dc:creator>
      <dc:date>2025-03-10T19:30:36Z</dc:date>
    </item>
    <item>
      <title>Re: Safe naming conventions for personal privilege accounts help</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/safe-naming-conventions-for-personal-privilege-accounts-help/m-p/1354748#M3224</link>
      <description>&lt;P&gt;Have you thought about using employee id or similar unique identifier in the organisation and the domain identifier? &lt;/P&gt;&lt;P&gt;Using departments is tricky as people do move around. &lt;/P&gt;&lt;P&gt;Many people share the same first and last names too. &lt;/P&gt;&lt;P&gt;​&lt;/P&gt;</description>
      <pubDate>Mon, 10 Mar 2025 19:58:00 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/safe-naming-conventions-for-personal-privilege-accounts-help/m-p/1354748#M3224</guid>
      <dc:creator>Mal</dc:creator>
      <dc:date>2025-03-10T19:58:00Z</dc:date>
    </item>
    <item>
      <title>Re: Safe naming conventions for personal privilege accounts help</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/safe-naming-conventions-for-personal-privilege-accounts-help/m-p/1354749#M3225</link>
      <description>&lt;P&gt;Hi @Schon Fazio​&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I agree with your approach track to define Personal Privileged Account safe naming convention to be scalable and future-proof, especially given your multi-domain setup. The challenge is balancing clarity, uniqueness, and brevity&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I would think one of the following naming convention might be useful.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;DOMAIN-PPA-ACCTYPE-USER&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;DOMAIN-PPA-DEPT-ACCTYPE-USER&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;DOMAIN-PPA-DPT-AT-USER&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope it helps !&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 10 Mar 2025 21:50:38 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/safe-naming-conventions-for-personal-privilege-accounts-help/m-p/1354749#M3225</guid>
      <dc:creator>M.Vora780263</dc:creator>
      <dc:date>2025-03-10T21:50:38Z</dc:date>
    </item>
    <item>
      <title>Re: Safe naming conventions for personal privilege accounts help</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/safe-naming-conventions-for-personal-privilege-accounts-help/m-p/1354750#M3226</link>
      <description>&lt;P&gt;This is the answer. People will move departments and departments will change names. Keep it simple and stick to something like an employee ID in the safe name.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regarding the safe per domain for CPM management, I would see if &lt;A alt="https://community.cyberark.com/s/article/What-is-PlatformsToManage-CPM-Parameter-and-how-to-configure-it" href="https://community.cyberark.com/s/article/What-is-PlatformsToManage-CPM-Parameter-and-how-to-configure-it" target="_blank"&gt;PlatformsToManage&lt;/A&gt; could help you consolidate the safes. Yes, it is for PAM self-hosted but being that the Priv Cloud and PAM self-hosted CPMs are (for the time being) still pretty similar, this could be a setting that you could convince support to help you define, maybe with some encouragement from your account manager/customer success manager.&lt;/P&gt;</description>
      <pubDate>Tue, 11 Mar 2025 06:49:43 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/safe-naming-conventions-for-personal-privilege-accounts-help/m-p/1354750#M3226</guid>
      <dc:creator>T.Schindler381412</dc:creator>
      <dc:date>2025-03-11T06:49:43Z</dc:date>
    </item>
    <item>
      <title>Re: Safe naming conventions for personal privilege accounts help</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/safe-naming-conventions-for-personal-privilege-accounts-help/m-p/1354751#M3227</link>
      <description>&lt;P&gt;Sadly Platforms To Manage isn't exposed in PCloud to end users either by configuration in pvwa or rest as far as I know. &lt;/P&gt;&lt;P&gt;It's an omission that I hope they resolve shortly as it is very handy in use cases like this.&lt;/P&gt;&lt;P&gt;I believe support can modify it, but not sure if they want to... &lt;/P&gt;</description>
      <pubDate>Tue, 11 Mar 2025 09:07:44 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/safe-naming-conventions-for-personal-privilege-accounts-help/m-p/1354751#M3227</guid>
      <dc:creator>Mal</dc:creator>
      <dc:date>2025-03-11T09:07:44Z</dc:date>
    </item>
    <item>
      <title>Re: Safe naming conventions for personal privilege accounts help</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/safe-naming-conventions-for-personal-privilege-accounts-help/m-p/1354752#M3228</link>
      <description>&lt;P&gt;I was on the fence about the department. this is good enough reason to axe it&lt;/P&gt;&lt;P&gt;something like an employee ID from our HR system would be interesting.  &lt;/P&gt;</description>
      <pubDate>Tue, 11 Mar 2025 13:14:07 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/safe-naming-conventions-for-personal-privilege-accounts-help/m-p/1354752#M3228</guid>
      <dc:creator>SFazio</dc:creator>
      <dc:date>2025-03-11T13:14:07Z</dc:date>
    </item>
    <item>
      <title>Re: Safe naming conventions for personal privilege accounts help</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/safe-naming-conventions-for-personal-privilege-accounts-help/m-p/1354753#M3229</link>
      <description>&lt;P&gt;Thanks for the response. At the very least placing domain first is a safe bet (pun intended). probably going to forgo the department though&lt;/P&gt;</description>
      <pubDate>Tue, 11 Mar 2025 13:16:20 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/safe-naming-conventions-for-personal-privilege-accounts-help/m-p/1354753#M3229</guid>
      <dc:creator>SFazio</dc:creator>
      <dc:date>2025-03-11T13:16:20Z</dc:date>
    </item>
  </channel>
</rss>

