<?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: Checkpoint R77.30 Policy Migration Using Expedition in Expedition Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/expedition-discussions/checkpoint-r77-30-policy-migration-using-expedition/m-p/248186#M1085</link>
    <description>&lt;P&gt;my experience has been to remove the policies that were in place for the cluster communications. As you know PanOS uses out of band communications for their HA so the cluster communication policies are no longer needed.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I would recommend to review but to also review thoroughly before removing and validate those rules are for the cluster communications.&lt;/P&gt;</description>
    <pubDate>Wed, 30 Jan 2019 15:47:26 GMT</pubDate>
    <dc:creator>sjanita</dc:creator>
    <dc:date>2019-01-30T15:47:26Z</dc:date>
    <item>
      <title>Checkpoint R77.30 Policy Migration Using Expedition</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/checkpoint-r77-30-policy-migration-using-expedition/m-p/248108#M1080</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have uploaded the required Checkpoint Config files into Expedition tool. When I looked at the policy, many rules have more than single zone assigned in both source and destination unlike Cisco policy migration. Especially if there are checkpoint firewall objects in either source or destinations I can see many zones assinged. Is it becasue of the networks in the checkpoint objects topology? How to fix this issue? Could you please share your checkpoint migration experience.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks in advance..&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best regards,&lt;/P&gt;
&lt;P&gt;Nagarjuna&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 30 Jan 2019 05:39:54 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/checkpoint-r77-30-policy-migration-using-expedition/m-p/248108#M1080</guid>
      <dc:creator>nagarjuna.b</dc:creator>
      <dc:date>2019-01-30T05:39:54Z</dc:date>
    </item>
    <item>
      <title>Re: Checkpoint R77.30 Policy Migration Using Expedition</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/checkpoint-r77-30-policy-migration-using-expedition/m-p/248129#M1082</link>
      <description>&lt;P&gt;The security zones for the policies are calculated using the static routes that were imported from the routes.txt file. If there are multiple address objects that match different static routes then you will see different security zones in the FROM or TO zones.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Expedition makes the assumption using best practices that network subnet will be segmented into its own security zone if the static routes are configured for different interfaces. If you wish to collapse multiple interfaces/subnets into a similar security zone you can change the zone assignments in the interface or zone configuration.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;After making the change you can run the 'autoZoneAssign' option located in the drop down menu in the upper right hand corner.&lt;/P&gt;</description>
      <pubDate>Wed, 30 Jan 2019 09:14:29 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/checkpoint-r77-30-policy-migration-using-expedition/m-p/248129#M1082</guid>
      <dc:creator>sjanita</dc:creator>
      <dc:date>2019-01-30T09:14:29Z</dc:date>
    </item>
    <item>
      <title>Re: Checkpoint R77.30 Policy Migration Using Expedition</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/checkpoint-r77-30-policy-migration-using-expedition/m-p/248176#M1084</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Thank you for the response. That helps. The actual problem was when there are checkpoint objects in the source and destination(may be for cluster communications) , all zones are being assigned, this may be the networks in the topology! Are these rules needs to be manually corrected or can they be disabled since they are for checkpoint firewall communications?</description>
      <pubDate>Wed, 30 Jan 2019 14:36:38 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/checkpoint-r77-30-policy-migration-using-expedition/m-p/248176#M1084</guid>
      <dc:creator>nagarjuna.b</dc:creator>
      <dc:date>2019-01-30T14:36:38Z</dc:date>
    </item>
    <item>
      <title>Re: Checkpoint R77.30 Policy Migration Using Expedition</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/checkpoint-r77-30-policy-migration-using-expedition/m-p/248186#M1085</link>
      <description>&lt;P&gt;my experience has been to remove the policies that were in place for the cluster communications. As you know PanOS uses out of band communications for their HA so the cluster communication policies are no longer needed.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I would recommend to review but to also review thoroughly before removing and validate those rules are for the cluster communications.&lt;/P&gt;</description>
      <pubDate>Wed, 30 Jan 2019 15:47:26 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/checkpoint-r77-30-policy-migration-using-expedition/m-p/248186#M1085</guid>
      <dc:creator>sjanita</dc:creator>
      <dc:date>2019-01-30T15:47:26Z</dc:date>
    </item>
  </channel>
</rss>

