<?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: Block known bad TLDs? in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/block-known-bad-tlds/m-p/64001#M38438</link>
    <description>&lt;P&gt;You could try to define custom applications using regex signatures for http GET requests and block those applications in the&amp;nbsp;security rulebase.&lt;/P&gt;</description>
    <pubDate>Wed, 02 Sep 2015 13:49:16 GMT</pubDate>
    <dc:creator>mvidic</dc:creator>
    <dc:date>2015-09-02T13:49:16Z</dc:date>
    <item>
      <title>Block known bad TLDs?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/block-known-bad-tlds/m-p/63997#M38434</link>
      <description>&lt;P&gt;My CISO want's to block known bad TLDs (such as .zip or .review) in our Palo. I know how to block specific url(s), but is there any way to block an entire TLD?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm running into issues blocking *.zip since it will also block legitimate URL traffic that has *.zip* in its URL.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 02 Sep 2015 13:22:29 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/block-known-bad-tlds/m-p/63997#M38434</guid>
      <dc:creator>grumpycat</dc:creator>
      <dc:date>2015-09-02T13:22:29Z</dc:date>
    </item>
    <item>
      <title>Re: Block known bad TLDs?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/block-known-bad-tlds/m-p/64001#M38438</link>
      <description>&lt;P&gt;You could try to define custom applications using regex signatures for http GET requests and block those applications in the&amp;nbsp;security rulebase.&lt;/P&gt;</description>
      <pubDate>Wed, 02 Sep 2015 13:49:16 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/block-known-bad-tlds/m-p/64001#M38438</guid>
      <dc:creator>mvidic</dc:creator>
      <dc:date>2015-09-02T13:49:16Z</dc:date>
    </item>
    <item>
      <title>Re: Block known bad TLDs?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/block-known-bad-tlds/m-p/64030#M38458</link>
      <description>&lt;P&gt;Hi Grumpycat, welcome,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;did you try blocking *.zip/ with the slash at the end? If that does not work, you might as well either accept false positives (and act upon them manually by allowing custom URLs reported to you in a separate whitelist) or trust to the other defensive mechanisms of firewall (vulnerabilities and threats protection, etc) and create separate custom category for any *.zip and set action to it as "continue", with fair warning to the users that they might be visiting malicious domain and to take extra caution...&lt;/P&gt;&lt;P&gt;Or, to alter suggestion by mvidic, try to play with regex, apps and custom signatures and try to allow certain longer urls that contain .zip in the URL (downloads of zip files...?) but I can't wrap my head around the fact that you want to block .zip but don't want to block it at the same time, can you share offending urls as examples so we can take a look at them perhaps?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Luciano&lt;/P&gt;</description>
      <pubDate>Wed, 02 Sep 2015 18:06:03 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/block-known-bad-tlds/m-p/64030#M38458</guid>
      <dc:creator>Lucky</dc:creator>
      <dc:date>2015-09-02T18:06:03Z</dc:date>
    </item>
    <item>
      <title>Re: Block known bad TLDs?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/block-known-bad-tlds/m-p/64035#M38463</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I just tried with the ".how" TLD and it blocks correctly with the filter "*.how/".&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Benjamin&lt;/P&gt;</description>
      <pubDate>Wed, 02 Sep 2015 18:33:23 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/block-known-bad-tlds/m-p/64035#M38463</guid>
      <dc:creator>BenjAudy.MTL</dc:creator>
      <dc:date>2015-09-02T18:33:23Z</dc:date>
    </item>
    <item>
      <title>Re: Block known bad TLDs?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/block-known-bad-tlds/m-p/64037#M38465</link>
      <description>&lt;P&gt;Hi Benjamin,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;FWIW - I think OPs problem was that *.zip filter caught more than they bargained for (it was also blocking any zip file download, I assume) &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; I am not sure how their specific .zip download URL was looking like.... all those download links are doing weird things with redirections and stuff, just to force-feed you more ads, maybe it was &lt;A href="http://whatever.domain/some_file.zip/than_page_with_ads/something.html" target="_blank"&gt;http://whatever.domain/some_file.zip/than_page_with_ads/something.html&lt;/A&gt; &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for the quick test, tho, everyone appreciates some concrete and quick help.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Wed, 02 Sep 2015 18:38:45 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/block-known-bad-tlds/m-p/64037#M38465</guid>
      <dc:creator>Lucky</dc:creator>
      <dc:date>2015-09-02T18:38:45Z</dc:date>
    </item>
    <item>
      <title>Re: Block known bad TLDs?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/block-known-bad-tlds/m-p/64041#M38467</link>
      <description>&lt;P&gt;Actually, I tried the URL "&lt;A href="http://www.howstuffworks.com/a.how&amp;quot;" target="_blank"&gt;http://www.howstuffworks.com/a.how"&lt;/A&gt; and the firewall doesn't block the request, so the filter seems to do what the OP wanted.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Benjamin&lt;/P&gt;</description>
      <pubDate>Wed, 02 Sep 2015 19:02:55 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/block-known-bad-tlds/m-p/64041#M38467</guid>
      <dc:creator>BenjAudy.MTL</dc:creator>
      <dc:date>2015-09-02T19:02:55Z</dc:date>
    </item>
    <item>
      <title>Re: Block known bad TLDs?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/block-known-bad-tlds/m-p/64134#M38517</link>
      <description>&lt;P&gt;I have not, but I will definitely try. Thanks for the suggestion!&lt;/P&gt;</description>
      <pubDate>Thu, 03 Sep 2015 17:17:44 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/block-known-bad-tlds/m-p/64134#M38517</guid>
      <dc:creator>grumpycat</dc:creator>
      <dc:date>2015-09-03T17:17:44Z</dc:date>
    </item>
    <item>
      <title>Re: Block known bad TLDs?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/block-known-bad-tlds/m-p/64135#M38518</link>
      <description>&lt;P&gt;Exactly. Here's a good example of the situation that I ran into when I tried to block ".zip/".&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I tested downloading FileZilla at&amp;nbsp;'sourceforge.net/projects/filezilla/files/FileZilla_Client/3.13.1/FileZilla_3.13.1_win32.zip/download?nowrap'&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Looking in my Palo, this URL was blocked. I've also opened up a Palo support case to see if an engineer has any recommendations. Who knows, this may end up as a feature request. &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 03 Sep 2015 17:30:24 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/block-known-bad-tlds/m-p/64135#M38518</guid>
      <dc:creator>grumpycat</dc:creator>
      <dc:date>2015-09-03T17:30:24Z</dc:date>
    </item>
    <item>
      <title>Re: Block known bad TLDs?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/block-known-bad-tlds/m-p/64138#M38519</link>
      <description>&lt;P&gt;Which version of Pan-OS are you using? It works properly on my firewall (v6.1.6) :&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;IMG src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/203i83EF72BE4C397AB9/image-size/original?v=mpbl-1&amp;amp;px=-1" alt="Zip block" title="Zip block" border="0" /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Benjamin&lt;/P&gt;</description>
      <pubDate>Thu, 03 Sep 2015 17:57:12 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/block-known-bad-tlds/m-p/64138#M38519</guid>
      <dc:creator>BenjAudy.MTL</dc:creator>
      <dc:date>2015-09-03T17:57:12Z</dc:date>
    </item>
    <item>
      <title>Re: Block known bad TLDs?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/block-known-bad-tlds/m-p/64139#M38520</link>
      <description>&lt;P&gt;I'm running 6.1.4. I guess it could be a versioning issue. Let me do some more testing to make sure I didn't flub up on something. I appreciate your ongoing help.&lt;/P&gt;</description>
      <pubDate>Thu, 03 Sep 2015 18:03:19 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/block-known-bad-tlds/m-p/64139#M38520</guid>
      <dc:creator>grumpycat</dc:creator>
      <dc:date>2015-09-03T18:03:19Z</dc:date>
    </item>
    <item>
      <title>Re: Block known bad TLDs?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/block-known-bad-tlds/m-p/64175#M38531</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am not sure how are you going to distinguish between 'something.zip/download?nowrap' and 'sourceforge.net/projects/filezilla/files/FileZilla_Client/3.13.1/FileZilla_3.13.1_win32.zip/download?nowrap'? .... and even something.zip can have subdomains and sub-subdomains, so you can't work around http:// neither....I think that your best guess is still to go with "continue" for this special category, if that matching of .zip/ does not work out &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;</description>
      <pubDate>Fri, 04 Sep 2015 06:54:52 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/block-known-bad-tlds/m-p/64175#M38531</guid>
      <dc:creator>Lucky</dc:creator>
      <dc:date>2015-09-04T06:54:52Z</dc:date>
    </item>
  </channel>
</rss>

