<?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: Rule Order Best Practice in Next-Generation Firewall Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/rule-order-best-practice/m-p/653037#M5079</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;There are many methods to organizing policies and sometimes its gets very complicated. I do something similar to what you have except I dont use Panorama:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Top rules are my global blocks&lt;/LI&gt;
&lt;LI&gt;specific policies to/from&lt;/LI&gt;
&lt;LI&gt;broad/generic policies for large groups etc.&lt;/LI&gt;
&lt;LI&gt;DENY ALL&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;Sometimes it wont work out depending on the logic, top down left to right. Best is to check and see if you already have a policy in place or if you need a new one. Here is a default base config I created with some of this in mind, block first, allow windows updates, then maybe more specific etc. Check the logs to ensure the proper policy is getting used when testing out the traffic.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://live.paloaltonetworks.com/t5/general-articles/secure-day-one-configuration-not-for-the-faint-of-heart/ta-p/435501" target="_blank"&gt;https://live.paloaltonetworks.com/t5/general-articles/secure-day-one-configuration-not-for-the-faint-of-heart/ta-p/435501&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;</description>
    <pubDate>Mon, 25 Nov 2024 20:13:17 GMT</pubDate>
    <dc:creator>OtakarKlier</dc:creator>
    <dc:date>2024-11-25T20:13:17Z</dc:date>
    <item>
      <title>Rule Order Best Practice</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/rule-order-best-practice/m-p/650951#M5069</link>
      <description>&lt;P&gt;We recently migrated to the Palo Alto Firewalls. I am looking for best practice/recommendations on how to properly order firewall rules. We have all our block rules first (geoblocking, malicious sites, specific apps, etc) up top. But what about the rest?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is it supposed to be more defined rules (specific ip to ip) up top? Do general application rules go towards the bottom (ex: any source to any destination using netflix)?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;My thought is to put all the specific rules on top and leave the general/more open ones towards the bottom.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This would go for all sections:&lt;/P&gt;
&lt;P&gt;Shared (overall) Pre-Rules blocks and specific rules&lt;/P&gt;
&lt;P&gt;Shared (overall) Post-Rules more generic open rules/apps&lt;/P&gt;
&lt;P&gt;Specific FWs (pre rules) - more specific for site rules and apps&lt;/P&gt;
&lt;P&gt;Specific FWs (post rules) - more generic open rules/apps&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is there a better way?&lt;/P&gt;</description>
      <pubDate>Sun, 24 Nov 2024 03:10:45 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/rule-order-best-practice/m-p/650951#M5069</guid>
      <dc:creator>AlexMcCreery</dc:creator>
      <dc:date>2024-11-24T03:10:45Z</dc:date>
    </item>
    <item>
      <title>Re: Rule Order Best Practice</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/rule-order-best-practice/m-p/653037#M5079</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;There are many methods to organizing policies and sometimes its gets very complicated. I do something similar to what you have except I dont use Panorama:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Top rules are my global blocks&lt;/LI&gt;
&lt;LI&gt;specific policies to/from&lt;/LI&gt;
&lt;LI&gt;broad/generic policies for large groups etc.&lt;/LI&gt;
&lt;LI&gt;DENY ALL&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;Sometimes it wont work out depending on the logic, top down left to right. Best is to check and see if you already have a policy in place or if you need a new one. Here is a default base config I created with some of this in mind, block first, allow windows updates, then maybe more specific etc. Check the logs to ensure the proper policy is getting used when testing out the traffic.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://live.paloaltonetworks.com/t5/general-articles/secure-day-one-configuration-not-for-the-faint-of-heart/ta-p/435501" target="_blank"&gt;https://live.paloaltonetworks.com/t5/general-articles/secure-day-one-configuration-not-for-the-faint-of-heart/ta-p/435501&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;</description>
      <pubDate>Mon, 25 Nov 2024 20:13:17 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/rule-order-best-practice/m-p/653037#M5079</guid>
      <dc:creator>OtakarKlier</dc:creator>
      <dc:date>2024-11-25T20:13:17Z</dc:date>
    </item>
  </channel>
</rss>

