<?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: PA object naming schema/convention? in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/pa-object-naming-schema-convention/m-p/64526#M38659</link>
    <description>&lt;P&gt;Snake,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I don't think there is a majic bullet here but here are some ideas based on what we are doing. &amp;nbsp;Incorporate a high level identifier nmenonic at the start of the name. &amp;nbsp;This might be customer or physical location or a zone. &amp;nbsp;We then try to have a descriptive nmenonic for the server type or application. &amp;nbsp;Such as Exch2010 or mysqldb. &amp;nbsp;We often add the last octets of the IP address to the name. &amp;nbsp;This helps us know what it's IP address is just by looking at the object name. &amp;nbsp;This becomes helpful when you have larger numbers of Objects (eg. +5000).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope this gives you some ideas.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Phil&lt;/P&gt;</description>
    <pubDate>Sat, 12 Sep 2015 01:35:25 GMT</pubDate>
    <dc:creator>HITSSEC</dc:creator>
    <dc:date>2015-09-12T01:35:25Z</dc:date>
    <item>
      <title>PA object naming schema/convention?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/pa-object-naming-schema-convention/m-p/20799#M15191</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Was about to create a naming schema for PA firewalls objects, but I am wondering if someone already has something I can model mine on so I don't have to reinvent the wheel. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 03 Apr 2013 00:02:48 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/pa-object-naming-schema-convention/m-p/20799#M15191</guid>
      <dc:creator>Snake</dc:creator>
      <dc:date>2013-04-03T00:02:48Z</dc:date>
    </item>
    <item>
      <title>Re: PA object naming schema/convention?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/pa-object-naming-schema-convention/m-p/63735#M38302</link>
      <description>&lt;P&gt;Did you come up with a naming conventions guide?&lt;/P&gt;&lt;P&gt;If so, please share.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Thu, 27 Aug 2015 18:28:15 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/pa-object-naming-schema-convention/m-p/63735#M38302</guid>
      <dc:creator>vsolwazi</dc:creator>
      <dc:date>2015-08-27T18:28:15Z</dc:date>
    </item>
    <item>
      <title>Re: PA object naming schema/convention?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/pa-object-naming-schema-convention/m-p/63737#M38304</link>
      <description>&lt;P&gt;In the past I have used something similar to &amp;lt;device location&amp;gt;&amp;lt;device identifier&amp;gt;&amp;lt;Number, i.e. 00 or 01, etc&amp;gt;. Hope this is what you are asking.&lt;/P&gt;</description>
      <pubDate>Thu, 27 Aug 2015 19:15:52 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/pa-object-naming-schema-convention/m-p/63737#M38304</guid>
      <dc:creator>OtakarKlier</dc:creator>
      <dc:date>2015-08-27T19:15:52Z</dc:date>
    </item>
    <item>
      <title>Re: PA object naming schema/convention?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/pa-object-naming-schema-convention/m-p/63743#M38310</link>
      <description>&lt;P&gt;Hi Snake,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;here is the shortest guide ever:&lt;/P&gt;&lt;LI-SPOILER&gt;KISS! (Keep It Simple, Snake)&lt;/LI-SPOILER&gt;&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; lol, nhf&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;the shorter the better, as long as it is relatively intuitive to a person that knows your convention across the organization. There is also a limit of 63 characters for the name and 255 characters for the description (click on the help in the screen, answer can be often there already)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Luciano&lt;/P&gt;</description>
      <pubDate>Thu, 27 Aug 2015 20:48:33 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/pa-object-naming-schema-convention/m-p/63743#M38310</guid>
      <dc:creator>Lucky</dc:creator>
      <dc:date>2015-08-27T20:48:33Z</dc:date>
    </item>
    <item>
      <title>Re: PA object naming schema/convention?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/pa-object-naming-schema-convention/m-p/64526#M38659</link>
      <description>&lt;P&gt;Snake,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I don't think there is a majic bullet here but here are some ideas based on what we are doing. &amp;nbsp;Incorporate a high level identifier nmenonic at the start of the name. &amp;nbsp;This might be customer or physical location or a zone. &amp;nbsp;We then try to have a descriptive nmenonic for the server type or application. &amp;nbsp;Such as Exch2010 or mysqldb. &amp;nbsp;We often add the last octets of the IP address to the name. &amp;nbsp;This helps us know what it's IP address is just by looking at the object name. &amp;nbsp;This becomes helpful when you have larger numbers of Objects (eg. +5000).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope this gives you some ideas.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Phil&lt;/P&gt;</description>
      <pubDate>Sat, 12 Sep 2015 01:35:25 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/pa-object-naming-schema-convention/m-p/64526#M38659</guid>
      <dc:creator>HITSSEC</dc:creator>
      <dc:date>2015-09-12T01:35:25Z</dc:date>
    </item>
  </channel>
</rss>

