<?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 How to correctly decrypt FTP (over TLS)  traffic in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/how-to-correctly-decrypt-ftp-over-tls-traffic/m-p/523048#M108341</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;I am facing the common issue of Passive FTP (over TLS). Basically, the connection fails due to the dynamic ports assigned in the encrypted channel. It is clear that the solution is to configure PA to decrypt the traffic to identify the dynamic port and PA automatically (and temporarily) will open the traffic for that port.&lt;/P&gt;
&lt;P&gt;But unfortunately, I could not find detailed instructions for the implementation.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClEjCAK" target="_blank"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClEjCAK&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I created a decryption rule for my only user with ANY in the service (see attachment) and the problem gets solved, but I didn't feel comfortable with the ANY so I tried filtering by FTP ports. I created a service called FTP Test with TCP 20 and 21 ports.&lt;/P&gt;
&lt;P&gt;Doing this, the traffic did not match, didn't get decrypted and the FTPs connection failed to list the directory.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;could you please help me out with the correct configuration?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Many thanks.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;BR /&gt;&lt;BR /&gt;Please note you are posting a public message where community members and experts can provide assistance. Sharing private information such as serial numbers or company information is not recommended.</description>
    <pubDate>Thu, 01 Dec 2022 15:56:44 GMT</pubDate>
    <dc:creator>JoseCortijo</dc:creator>
    <dc:date>2022-12-01T15:56:44Z</dc:date>
    <item>
      <title>How to correctly decrypt FTP (over TLS)  traffic</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/how-to-correctly-decrypt-ftp-over-tls-traffic/m-p/523048#M108341</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;I am facing the common issue of Passive FTP (over TLS). Basically, the connection fails due to the dynamic ports assigned in the encrypted channel. It is clear that the solution is to configure PA to decrypt the traffic to identify the dynamic port and PA automatically (and temporarily) will open the traffic for that port.&lt;/P&gt;
&lt;P&gt;But unfortunately, I could not find detailed instructions for the implementation.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClEjCAK" target="_blank"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClEjCAK&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I created a decryption rule for my only user with ANY in the service (see attachment) and the problem gets solved, but I didn't feel comfortable with the ANY so I tried filtering by FTP ports. I created a service called FTP Test with TCP 20 and 21 ports.&lt;/P&gt;
&lt;P&gt;Doing this, the traffic did not match, didn't get decrypted and the FTPs connection failed to list the directory.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;could you please help me out with the correct configuration?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Many thanks.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;BR /&gt;&lt;BR /&gt;Please note you are posting a public message where community members and experts can provide assistance. Sharing private information such as serial numbers or company information is not recommended.</description>
      <pubDate>Thu, 01 Dec 2022 15:56:44 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/how-to-correctly-decrypt-ftp-over-tls-traffic/m-p/523048#M108341</guid>
      <dc:creator>JoseCortijo</dc:creator>
      <dc:date>2022-12-01T15:56:44Z</dc:date>
    </item>
    <item>
      <title>Re: How to correctly decrypt FTP (over TLS)  traffic</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/how-to-correctly-decrypt-ftp-over-tls-traffic/m-p/523184#M108362</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;You would need to select the port/service that the traffic is being seen as prior to decryption. Best practice would be to decrypt all traffic and have exceptions to bypass encryption.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope this helps.&lt;/P&gt;</description>
      <pubDate>Fri, 02 Dec 2022 21:07:23 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/how-to-correctly-decrypt-ftp-over-tls-traffic/m-p/523184#M108362</guid>
      <dc:creator>OtakarKlier</dc:creator>
      <dc:date>2022-12-02T21:07:23Z</dc:date>
    </item>
  </channel>
</rss>

