<?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 Inter Zone traffic in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/inter-zone-traffic/m-p/268144#M74531</link>
    <description>&lt;P&gt;I have created a policy rule in palo alto from INSIDE zone to OUTSIDE zone all the traffic is allowed. and I am able to ping from a inside device to a outside host however when I try to ping from outside host to the inside host it is not working.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Do I need to create allow rules from OUTSIDE zone to INSIDE as well?&lt;/P&gt;&lt;P&gt;because in ASA when we intiate the traffic from inside to outside then outside to inside traffic is allowed automatically and we do not need to create rules as the cisco ASA allows traffic by just checking the active session if it were initiated already from the inside zone which has the higher securiy level.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;please help me understard this concept in palo alto.&lt;/P&gt;</description>
    <pubDate>Sat, 08 Jun 2019 19:55:49 GMT</pubDate>
    <dc:creator>Ayush_paloalto</dc:creator>
    <dc:date>2019-06-08T19:55:49Z</dc:date>
    <item>
      <title>Inter Zone traffic</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/inter-zone-traffic/m-p/268144#M74531</link>
      <description>&lt;P&gt;I have created a policy rule in palo alto from INSIDE zone to OUTSIDE zone all the traffic is allowed. and I am able to ping from a inside device to a outside host however when I try to ping from outside host to the inside host it is not working.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Do I need to create allow rules from OUTSIDE zone to INSIDE as well?&lt;/P&gt;&lt;P&gt;because in ASA when we intiate the traffic from inside to outside then outside to inside traffic is allowed automatically and we do not need to create rules as the cisco ASA allows traffic by just checking the active session if it were initiated already from the inside zone which has the higher securiy level.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;please help me understard this concept in palo alto.&lt;/P&gt;</description>
      <pubDate>Sat, 08 Jun 2019 19:55:49 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/inter-zone-traffic/m-p/268144#M74531</guid>
      <dc:creator>Ayush_paloalto</dc:creator>
      <dc:date>2019-06-08T19:55:49Z</dc:date>
    </item>
    <item>
      <title>Re: Inter Zone traffic</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/inter-zone-traffic/m-p/268151#M74532</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/113935"&gt;@Ayush_paloalto&lt;/a&gt;&amp;nbsp;This is called stateful inspection, so the return path for sessions is implicitly allowed.&lt;/P&gt;&lt;P&gt;Furthermore, apps which negotiate random high ports like RPC, FTP, SIP/RTP etc. are automatically detected and implicit rules are in place for these sessions.&lt;/P&gt;&lt;P&gt;So with the zone concept, you allow ping from zone inside to zone outside and that work's fine, as you said.&lt;/P&gt;&lt;P&gt;But your second scenario, ping from zone outside to zone inside is not covered by your rule and so will be matched to the interzone default policy, which per default drops the traffic.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So in short: yes, everything works as expected, return traffic is implicitly allowed and you need an additional rule&lt;/P&gt;</description>
      <pubDate>Sat, 08 Jun 2019 20:01:24 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/inter-zone-traffic/m-p/268151#M74532</guid>
      <dc:creator>Chacko42</dc:creator>
      <dc:date>2019-06-08T20:01:24Z</dc:date>
    </item>
  </channel>
</rss>

