<?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: Cisco ASA to Palo Alto in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/cisco-asa-to-palo-alto/m-p/321494#M82280</link>
    <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/101331"&gt;@SureshBalaji&lt;/a&gt;&amp;nbsp;Your security policy should not configure with any any. At least you should restrict policy for specific zones.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am fully agreed with&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/132521"&gt;@SutareMayur&lt;/a&gt;&amp;nbsp;.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 08 Apr 2020 11:43:16 GMT</pubDate>
    <dc:creator>johnde</dc:creator>
    <dc:date>2020-04-08T11:43:16Z</dc:date>
    <item>
      <title>Cisco ASA to Palo Alto</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/cisco-asa-to-palo-alto/m-p/321372#M82256</link>
      <description>&lt;P&gt;Hi Team, we recently migrated from cisco ASA to Palo Alto 3220, where for one of the policy in cisco ASA has "&amp;nbsp;access-list inside-egress extended permit ip any any", And this access-list is attached to the access-group to the interface "inside". as you can see below.&lt;/P&gt;&lt;P&gt;"access-group inside-egress out interface inside"&lt;/P&gt;&lt;P&gt;as per my understanding from cisco perspective for this access group the traffic which egresses out of the interface named "inside", should evaluate the against the access-list "inside-egress". The following are the access-list related to inside-egress.&amp;nbsp; &amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;access-list inside-egress extended permit icmp host 10.197.37.212 host 10.15.126.119&lt;BR /&gt;access-list inside-egress extended permit tcp host 10.16.17.9 host 10.15.4.84 eq 5707 log interval 1&lt;BR /&gt;access-list inside-egress extended permit ip any any&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When it is converted to Palo Alto, for the "&amp;nbsp;access-list inside-egress extended permit ip any any"&amp;nbsp; tool created a policy stating&amp;nbsp;&lt;/P&gt;&lt;P&gt;Source zone - any, Source subnet- any to destination-subnet- any, destination-zone - "inside" with allow action.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Basically anything from anywhere were allowed to inside zone (which is dangerous wide open policy).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;How we can rectify this, need your advise, for the access-group with "out" attached to the interface and having "permit ip any any" accesslist.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 07 Apr 2020 22:51:03 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/cisco-asa-to-palo-alto/m-p/321372#M82256</guid>
      <dc:creator>SureshBalaji</dc:creator>
      <dc:date>2020-04-07T22:51:03Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ASA to Palo Alto</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/cisco-asa-to-palo-alto/m-p/321487#M82276</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/101331"&gt;@SureshBalaji&lt;/a&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;First of all, you shouldn't allow anything coming any destination&amp;nbsp; zone with source any. I would recommend you to go through the the networks those need to be allowed and allow required subnets only, that too with specific zones.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Mayur&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 08 Apr 2020 11:24:53 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/cisco-asa-to-palo-alto/m-p/321487#M82276</guid>
      <dc:creator>SutareMayur</dc:creator>
      <dc:date>2020-04-08T11:24:53Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ASA to Palo Alto</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/cisco-asa-to-palo-alto/m-p/321494#M82280</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/101331"&gt;@SureshBalaji&lt;/a&gt;&amp;nbsp;Your security policy should not configure with any any. At least you should restrict policy for specific zones.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am fully agreed with&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/132521"&gt;@SutareMayur&lt;/a&gt;&amp;nbsp;.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 08 Apr 2020 11:43:16 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/cisco-asa-to-palo-alto/m-p/321494#M82280</guid>
      <dc:creator>johnde</dc:creator>
      <dc:date>2020-04-08T11:43:16Z</dc:date>
    </item>
  </channel>
</rss>

