<?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: Approach to manage FTP in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/approach-to-manage-ftp/m-p/8277#M6109</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Besides a few business systems that have FTP needs - we block ftp unless you are a "domain" authenticated IT person. Initially we found a few domain or local system accounts that had a business need to FTP (and those we made accommodations for), but overall it was successful very early on. Provided most everyone in your environment logs into the domain - using AD users and groups within the rules works very slick. We also setup a daily report showing FTP usage, to keep an eye on IT usage and DLP. And we include Threat/AV/URL/Wildfire to the ftp allow rule.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Initially we setup the rule in logging only for a few months to get a handle of who/what/when was happening for FTP.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Cheers,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Mike&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 02 Apr 2013 12:49:22 GMT</pubDate>
    <dc:creator>MGoodnow</dc:creator>
    <dc:date>2013-04-02T12:49:22Z</dc:date>
    <item>
      <title>Approach to manage FTP</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/approach-to-manage-ftp/m-p/8275#M6107</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Based on recent research by Palo Alto there appears to be a greater emphasis needed&amp;nbsp; on managing FTP.&amp;nbsp; What approach have you found&amp;nbsp; most easily to deploy?&amp;nbsp; The two options I can think of are:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Controlling who can do FTP&lt;/P&gt;&lt;P&gt;2. Only allowing FTP access to trusted FTP sites&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any thoughts or ideas appreciated. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Phil&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Apr 2013 23:33:41 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/approach-to-manage-ftp/m-p/8275#M6107</guid>
      <dc:creator>HITSSEC</dc:creator>
      <dc:date>2013-04-01T23:33:41Z</dc:date>
    </item>
    <item>
      <title>Re: Approach to manage FTP</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/approach-to-manage-ftp/m-p/8276#M6108</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Depends on your situation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A regular web-browsing client usually doesnt have to be able to use ftp for daily use.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So if your case is to block malware reaching clients then the hole which you allow clients through should be as narrow as possible. And if possible also consider using terminalserver solutions or dedicated (virtual) appliances such as &lt;A href="http://www.webconverger.com/" title="http://www.webconverger.com/"&gt;Webconverger - opensource Web Kiosk PC operating system&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;An easy way to achieve the above (in terms of PA configuration) is a combination of your suggestions.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;First of all, not everyone should be allowed for ftp. And those who are will be limited to dedicated sites.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Im not sure if you can use url filtering for this but if you can then a somewhat healthy approach is to only allow sites which belongs to specific categories.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also dont forget to enable AV scanning in PA for the traffic passing through.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A potential threat is encrypted ftp. There is both SFTP and FTPS. Im not sure if the SSL-termination in PA will help you that much with both of the cases (if any).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Apr 2013 03:12:10 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/approach-to-manage-ftp/m-p/8276#M6108</guid>
      <dc:creator>mikand</dc:creator>
      <dc:date>2013-04-02T03:12:10Z</dc:date>
    </item>
    <item>
      <title>Re: Approach to manage FTP</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/approach-to-manage-ftp/m-p/8277#M6109</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Besides a few business systems that have FTP needs - we block ftp unless you are a "domain" authenticated IT person. Initially we found a few domain or local system accounts that had a business need to FTP (and those we made accommodations for), but overall it was successful very early on. Provided most everyone in your environment logs into the domain - using AD users and groups within the rules works very slick. We also setup a daily report showing FTP usage, to keep an eye on IT usage and DLP. And we include Threat/AV/URL/Wildfire to the ftp allow rule.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Initially we setup the rule in logging only for a few months to get a handle of who/what/when was happening for FTP.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Cheers,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Mike&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Apr 2013 12:49:22 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/approach-to-manage-ftp/m-p/8277#M6109</guid>
      <dc:creator>MGoodnow</dc:creator>
      <dc:date>2013-04-02T12:49:22Z</dc:date>
    </item>
  </channel>
</rss>

