<?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: How Passive FTP is filtered in Palo Alto in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/how-passive-ftp-is-filtered-in-palo-alto/m-p/78094#M42819</link>
    <description>&lt;P&gt;&lt;BR /&gt;&lt;SPAN&gt;#Firewall works on the concept of inspection.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#Connection request will be sent on port 21 , return packet will contain the DATA ports ( for example 3453 &amp;nbsp;) &lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Firewall inspects this session and &amp;nbsp;since it a past of a existing session,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;#Firewall Opens a by-default pin hole for the data port &amp;nbsp;( as it already inspected the S2C packet )&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;and the traffic going on the data port&amp;nbsp;are allowed.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sun, 15 May 2016 05:16:53 GMT</pubDate>
    <dc:creator>tsrivastav</dc:creator>
    <dc:date>2016-05-15T05:16:53Z</dc:date>
    <item>
      <title>How Passive FTP is filtered in Palo Alto</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/how-passive-ftp-is-filtered-in-palo-alto/m-p/78092#M42817</link>
      <description>&lt;P&gt;Hi Guys,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I know application FTP covers both Passive and Active FTP. However, my question is how it filters the traffic. I mean how a server Intiating a connection to the client will be filtered and allowed. Can anyone help.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 14 May 2016 15:03:56 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/how-passive-ftp-is-filtered-in-palo-alto/m-p/78092#M42817</guid>
      <dc:creator>yadsingh</dc:creator>
      <dc:date>2016-05-14T15:03:56Z</dc:date>
    </item>
    <item>
      <title>Re: How Passive FTP is filtered in Palo Alto</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/how-passive-ftp-is-filtered-in-palo-alto/m-p/78093#M42818</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The firewall create predict sessions. You can read about it here:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://live.paloaltonetworks.com/t5/Learning-Articles/Palo-Alto-Networks-Firewall-Session-Overview/ta-p/55633" target="_self"&gt;https://live.paloaltonetworks.com/t5/Learning-Articles/Palo-Alto-Networks-Firewall-Session-Overview/ta-p/55633&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Benjamin&lt;/P&gt;</description>
      <pubDate>Sat, 14 May 2016 15:55:38 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/how-passive-ftp-is-filtered-in-palo-alto/m-p/78093#M42818</guid>
      <dc:creator>BenjAudy.MTL</dc:creator>
      <dc:date>2016-05-14T15:55:38Z</dc:date>
    </item>
    <item>
      <title>Re: How Passive FTP is filtered in Palo Alto</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/how-passive-ftp-is-filtered-in-palo-alto/m-p/78094#M42819</link>
      <description>&lt;P&gt;&lt;BR /&gt;&lt;SPAN&gt;#Firewall works on the concept of inspection.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#Connection request will be sent on port 21 , return packet will contain the DATA ports ( for example 3453 &amp;nbsp;) &lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Firewall inspects this session and &amp;nbsp;since it a past of a existing session,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;#Firewall Opens a by-default pin hole for the data port &amp;nbsp;( as it already inspected the S2C packet )&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;and the traffic going on the data port&amp;nbsp;are allowed.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 15 May 2016 05:16:53 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/how-passive-ftp-is-filtered-in-palo-alto/m-p/78094#M42819</guid>
      <dc:creator>tsrivastav</dc:creator>
      <dc:date>2016-05-15T05:16:53Z</dc:date>
    </item>
    <item>
      <title>Re: How Passive FTP is filtered in Palo Alto</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/how-passive-ftp-is-filtered-in-palo-alto/m-p/78095#M42820</link>
      <description>&lt;P&gt;So if your question was how the firewall allows the traffic going on the data ports from Client to server&amp;nbsp;&lt;/P&gt;
&lt;P&gt;then Inspection of the FTP application is the answer&lt;/P&gt;
&lt;P&gt;also predict session plays an imp. role in the same&lt;/P&gt;</description>
      <pubDate>Sun, 15 May 2016 05:17:38 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/how-passive-ftp-is-filtered-in-palo-alto/m-p/78095#M42820</guid>
      <dc:creator>tsrivastav</dc:creator>
      <dc:date>2016-05-15T05:17:38Z</dc:date>
    </item>
  </channel>
</rss>

