<?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: Firewall Rule Consolidation in Expedition Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/expedition-discussions/firewall-rule-consolidation/m-p/252109#M1241</link>
    <description>&lt;P&gt;You can use the 'Merge' option, unser Filters (See attached graphic) to display which rules can be consolidated.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;A common starting point to check for rules that can be merged are to filter on same From/Source/To/Destination. After deciding whether or not to merge the security policies you can then change or your match criteria (e.g. From/Source/To/Service or Application).&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Once the results of the similar policies are highlighted you can then choose to 'Merge' the policies by using the merge option (see graphic 2).&lt;/P&gt;</description>
    <pubDate>Mon, 04 Mar 2019 05:53:11 GMT</pubDate>
    <dc:creator>sjanita</dc:creator>
    <dc:date>2019-03-04T05:53:11Z</dc:date>
    <item>
      <title>Firewall Rule Consolidation</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/firewall-rule-consolidation/m-p/252097#M1238</link>
      <description>&lt;P&gt;Hi All,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am trying to consolidate firewall rules on one Palo Alto firewall. I have uploaded the config to Expedition but I am struggling to understand how to run the analysis that will provide me with information on duplicate rules or suggested consolidation. Would someone be able to provide me with some detailed instructions? Any help is appreciated!&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;-Sig&lt;/P&gt;</description>
      <pubDate>Mon, 04 Mar 2019 02:11:55 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/firewall-rule-consolidation/m-p/252097#M1238</guid>
      <dc:creator>Signet</dc:creator>
      <dc:date>2019-03-04T02:11:55Z</dc:date>
    </item>
    <item>
      <title>Re: Firewall Rule Consolidation</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/firewall-rule-consolidation/m-p/252109#M1241</link>
      <description>&lt;P&gt;You can use the 'Merge' option, unser Filters (See attached graphic) to display which rules can be consolidated.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;A common starting point to check for rules that can be merged are to filter on same From/Source/To/Destination. After deciding whether or not to merge the security policies you can then change or your match criteria (e.g. From/Source/To/Service or Application).&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Once the results of the similar policies are highlighted you can then choose to 'Merge' the policies by using the merge option (see graphic 2).&lt;/P&gt;</description>
      <pubDate>Mon, 04 Mar 2019 05:53:11 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/firewall-rule-consolidation/m-p/252109#M1241</guid>
      <dc:creator>sjanita</dc:creator>
      <dc:date>2019-03-04T05:53:11Z</dc:date>
    </item>
    <item>
      <title>Re: Firewall Rule Consolidation</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/firewall-rule-consolidation/m-p/252203#M1244</link>
      <description>&lt;P&gt;That is exactly what I am looking for. Thank you Sjanita!&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 04 Mar 2019 18:32:26 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/firewall-rule-consolidation/m-p/252203#M1244</guid>
      <dc:creator>Signet</dc:creator>
      <dc:date>2019-03-04T18:32:26Z</dc:date>
    </item>
  </channel>
</rss>

