<?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>article Safe Naming Convention Best Practices in PAM Self-Hosted Articles</title>
    <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-articles/safe-naming-convention-best-practices/ta-p/1429706</link>
    <description>&lt;H3&gt;Question&lt;/H3&gt;
Safe Naming Convention Best Practices

&lt;H3&gt;Answer&lt;/H3&gt;
&lt;H2&gt;Naming and Capacity Restrictions &amp;amp; Considerations&lt;/H2&gt;
&lt;UL&gt;&lt;LI&gt;A safe name cannot be more than 28 characters&lt;/LI&gt;&lt;LI&gt;Due to performance considerations, a maximum number of objects stored in a safe is 20000. This includes versions of objects, therefore the recommended number of actual accounts or files stored in a safe is 3000-5000&lt;/LI&gt;&lt;LI&gt;Due to security considerations, it is recommended to separate objects stored in safes in groups, following the “least privilege” concept, to avoid situations where providing access for a user to a group of accounts also gives said user access to unrelated accounts. For example: “Windows Accounts” vs “Window Local Administrators for HR App” (28 character limit was not enforced in this example)&amp;nbsp;Heading 2&amp;nbsp;- RGB 23-69-123&lt;/LI&gt;&lt;/UL&gt;
&lt;H2&gt;Naming Convention Creation Steps&lt;/H2&gt;
&lt;UL&gt;&lt;LI&gt;Define business designations that are important for your environment. For example: Line of Business, Geographical Location, Data Center, Platform, Account Type, Application Association, Environment, etc&lt;/LI&gt;&lt;LI&gt;List them in order of importance&lt;/LI&gt;&lt;LI&gt;Discuss and agree on the resulting layered structure. This will be your Safe Naming Convention Base. Eliminate any layers that are redundant or not needed.&lt;/LI&gt;&lt;LI&gt;List out as many examples of each designation as possible and define 2-4 letter translations for each. For example ORA for Oracle Database or LADM for Local Administrative Account. Alternatively, define a 1-2 digit number and its place in the Safe name instead of a 2-4 letter translation. For example 06 in the 8th and 9th spot for Oracle Database or 1 in the 1st spot for Production&lt;/LI&gt;&lt;LI&gt;Create 7-10 examples of safe names to ensure the structure is sufficiently robust to account for any future need&lt;/LI&gt;&lt;LI&gt;Document the Safe Naming Convention&lt;/LI&gt;&lt;LI&gt;Examples
	&lt;UL&gt;&lt;LI&gt;P-BOS-SRV-WIN-LADM – Local Administrative Accounts (LADM) for Production (P) Windows (WIN) Servers (SRV) in Boston DC (BOS)&lt;/LI&gt;&lt;LI&gt;P-BOS-SRV-WIN-DSVC-HR – Domain Service Accounts (DSVC) for the HR Application (HR) living on Production (P) Windows (WIN) Servers (SRV) in the Boston DC (BOS)&lt;/LI&gt;&lt;LI&gt;D-NYC-DB-ORA-LSVC-HR – Local Service Accounts (LSVC) for the HR Application (HR) living on Development (D) Oracle (ORA) Database (DB) in the NY Data Center (NYC)&lt;/LI&gt;&lt;/UL&gt;
&lt;/LI&gt;&lt;/UL&gt;
&lt;H2&gt;Naming Convention Cheat Sheet&lt;/H2&gt;
&lt;P&gt;Category 1 - Environment:&lt;/P&gt;
&lt;P&gt;Production (P), Development (D), Testing (T), Q/A (Q), etc&lt;/P&gt;
&lt;P&gt;Category 2 (optional)&amp;nbsp;&amp;nbsp;&amp;nbsp;- Geographical Location or domain:&lt;/P&gt;
&lt;P&gt;Datacenter 1 (DC1), Datacenter 2 (DC2), California Datacenter (CA), etc&lt;/P&gt;
&lt;P&gt;Category 3 (optional)&amp;nbsp;&amp;nbsp;&amp;nbsp;- Business Unit/Access Groups/Application:&lt;/P&gt;
&lt;P&gt;Security Team (SEC), Engineering Team (ENG), Support Desk (SUP), Network Team Routers (NWR), Network Team Switches (NWS), etc&lt;/P&gt;
&lt;P&gt;Category 4 - Technology:&lt;/P&gt;
&lt;P&gt;Server (SVR), Workstation (WKS), Network Device (NET), Database (DB), Mainframe (MF), Domain (DOM) etc&lt;/P&gt;
&lt;P&gt;Category 5 - Technology Subtype (flavor):&lt;/P&gt;
&lt;P&gt;Windows (WIN), UNIX (UNX), Linux (LNX), HP-UX (HP), Cisco (CSC), SQL Database (SQL), Oracle Database (ORC)&lt;/P&gt;
&lt;P&gt;Category 6 - Account Type:&lt;/P&gt;
&lt;P&gt;Local Account (LA), Domain Account (DA), Local Service Account (LS), Domain Service Account (DS), Root (RT), Enable Account (EN), SQL SA Account (SA)&lt;/P&gt;
&lt;P&gt;Category 7 - Auto-Detection Enabled Safe&amp;nbsp;&amp;nbsp;&amp;nbsp;(required only if using auto-detection for local accounts):&lt;/P&gt;
&lt;P&gt;Auto-detection (A)&lt;/P&gt;</description>
    <pubDate>Fri, 31 Oct 2025 05:01:04 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2025-10-31T05:01:04Z</dc:date>
    <item>
      <title>Safe Naming Convention Best Practices</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-articles/safe-naming-convention-best-practices/ta-p/1429706</link>
      <description>&lt;H3&gt;Question&lt;/H3&gt;
Safe Naming Convention Best Practices

&lt;H3&gt;Answer&lt;/H3&gt;
&lt;H2&gt;Naming and Capacity Restrictions &amp;amp; Considerations&lt;/H2&gt;
&lt;UL&gt;&lt;LI&gt;A safe name cannot be more than 28 characters&lt;/LI&gt;&lt;LI&gt;Due to performance considerations, a maximum number of objects stored in a safe is 20000. This includes versions of objects, therefore the recommended number of actual accounts or files stored in a safe is 3000-5000&lt;/LI&gt;&lt;LI&gt;Due to security considerations, it is recommended to separate objects stored in safes in groups, following the “least privilege” concept, to avoid situations where providing access for a user to a group of accounts also gives said user access to unrelated accounts. For example: “Windows Accounts” vs “Window Local Administrators for HR App” (28 character limit was not enforced in this example)&amp;nbsp;Heading 2&amp;nbsp;- RGB 23-69-123&lt;/LI&gt;&lt;/UL&gt;
&lt;H2&gt;Naming Convention Creation Steps&lt;/H2&gt;
&lt;UL&gt;&lt;LI&gt;Define business designations that are important for your environment. For example: Line of Business, Geographical Location, Data Center, Platform, Account Type, Application Association, Environment, etc&lt;/LI&gt;&lt;LI&gt;List them in order of importance&lt;/LI&gt;&lt;LI&gt;Discuss and agree on the resulting layered structure. This will be your Safe Naming Convention Base. Eliminate any layers that are redundant or not needed.&lt;/LI&gt;&lt;LI&gt;List out as many examples of each designation as possible and define 2-4 letter translations for each. For example ORA for Oracle Database or LADM for Local Administrative Account. Alternatively, define a 1-2 digit number and its place in the Safe name instead of a 2-4 letter translation. For example 06 in the 8th and 9th spot for Oracle Database or 1 in the 1st spot for Production&lt;/LI&gt;&lt;LI&gt;Create 7-10 examples of safe names to ensure the structure is sufficiently robust to account for any future need&lt;/LI&gt;&lt;LI&gt;Document the Safe Naming Convention&lt;/LI&gt;&lt;LI&gt;Examples
	&lt;UL&gt;&lt;LI&gt;P-BOS-SRV-WIN-LADM – Local Administrative Accounts (LADM) for Production (P) Windows (WIN) Servers (SRV) in Boston DC (BOS)&lt;/LI&gt;&lt;LI&gt;P-BOS-SRV-WIN-DSVC-HR – Domain Service Accounts (DSVC) for the HR Application (HR) living on Production (P) Windows (WIN) Servers (SRV) in the Boston DC (BOS)&lt;/LI&gt;&lt;LI&gt;D-NYC-DB-ORA-LSVC-HR – Local Service Accounts (LSVC) for the HR Application (HR) living on Development (D) Oracle (ORA) Database (DB) in the NY Data Center (NYC)&lt;/LI&gt;&lt;/UL&gt;
&lt;/LI&gt;&lt;/UL&gt;
&lt;H2&gt;Naming Convention Cheat Sheet&lt;/H2&gt;
&lt;P&gt;Category 1 - Environment:&lt;/P&gt;
&lt;P&gt;Production (P), Development (D), Testing (T), Q/A (Q), etc&lt;/P&gt;
&lt;P&gt;Category 2 (optional)&amp;nbsp;&amp;nbsp;&amp;nbsp;- Geographical Location or domain:&lt;/P&gt;
&lt;P&gt;Datacenter 1 (DC1), Datacenter 2 (DC2), California Datacenter (CA), etc&lt;/P&gt;
&lt;P&gt;Category 3 (optional)&amp;nbsp;&amp;nbsp;&amp;nbsp;- Business Unit/Access Groups/Application:&lt;/P&gt;
&lt;P&gt;Security Team (SEC), Engineering Team (ENG), Support Desk (SUP), Network Team Routers (NWR), Network Team Switches (NWS), etc&lt;/P&gt;
&lt;P&gt;Category 4 - Technology:&lt;/P&gt;
&lt;P&gt;Server (SVR), Workstation (WKS), Network Device (NET), Database (DB), Mainframe (MF), Domain (DOM) etc&lt;/P&gt;
&lt;P&gt;Category 5 - Technology Subtype (flavor):&lt;/P&gt;
&lt;P&gt;Windows (WIN), UNIX (UNX), Linux (LNX), HP-UX (HP), Cisco (CSC), SQL Database (SQL), Oracle Database (ORC)&lt;/P&gt;
&lt;P&gt;Category 6 - Account Type:&lt;/P&gt;
&lt;P&gt;Local Account (LA), Domain Account (DA), Local Service Account (LS), Domain Service Account (DS), Root (RT), Enable Account (EN), SQL SA Account (SA)&lt;/P&gt;
&lt;P&gt;Category 7 - Auto-Detection Enabled Safe&amp;nbsp;&amp;nbsp;&amp;nbsp;(required only if using auto-detection for local accounts):&lt;/P&gt;
&lt;P&gt;Auto-detection (A)&lt;/P&gt;</description>
      <pubDate>Fri, 31 Oct 2025 05:01:04 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-articles/safe-naming-convention-best-practices/ta-p/1429706</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2025-10-31T05:01:04Z</dc:date>
    </item>
  </channel>
</rss>

