<?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: URL Category Versus URL Filtering Profile in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/url-category-versus-url-filtering-profile/m-p/164078#M53033</link>
    <description>&lt;P&gt;URL Category in the security policy match criteria allows you to &lt;U&gt;vary the security profiles based on the URL category&lt;/U&gt;. &amp;nbsp;Security profiles are things like AntiVirus Profiles, Vulnerability Profiles, WildFire Profiles, Anti-Spyware Profiles, File Blocking Profiles, Data Filtering Profiles, etc. &amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;One common use-case is to allow users to visit questionable URL categories, but restrict the file types they can download from those locations.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You need 2 security policy rules to accomplish this. &amp;nbsp;The first policy allows web-browsing with URL category = unknown/parked/insufficient, and then you attach a strict file blocking profile that prevents dangerous file types from being downloaded (PE, pdf, office, java, flash, etc.) &amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The 2nd security policy is for web-browsing in general, no URL category match, but then you can attach a less restrictive file blocking profile that allows PDFs, office docs, etc.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This concept/tactic is discussed in a little more detail in the "Best Practices for Ransomware Prevention" document, Step #4, found here:&lt;/P&gt;&lt;P&gt;&amp;nbsp;- &lt;A title="Best Practices for Ransomware Prevention" href="https://live.paloaltonetworks.com/t5/Featured-Articles/Best-Practices-for-Ransomware-Prevention/ta-p/74148" target="_blank"&gt;https://live.paloaltonetworks.com/t5/Featured-Articles/Best-Practices-for-Ransomware-Prevention/ta-p/74148&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 30 Jun 2017 12:56:07 GMT</pubDate>
    <dc:creator>jvalentine</dc:creator>
    <dc:date>2017-06-30T12:56:07Z</dc:date>
    <item>
      <title>URL Category Versus URL Filtering Profile</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/url-category-versus-url-filtering-profile/m-p/164044#M53026</link>
      <description>&lt;P&gt;When would you use one over the other?&lt;/P&gt;</description>
      <pubDate>Fri, 30 Jun 2017 09:39:36 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/url-category-versus-url-filtering-profile/m-p/164044#M53026</guid>
      <dc:creator>RodO</dc:creator>
      <dc:date>2017-06-30T09:39:36Z</dc:date>
    </item>
    <item>
      <title>Re: URL Category Versus URL Filtering Profile</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/url-category-versus-url-filtering-profile/m-p/164068#M53029</link>
      <description>&lt;P&gt;URL category in the destination of a security policy will work sort of like a dynamic IP list, it's going to allow a TCP handshake through based on the destination IP belonging to a category&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;URL filtering profile will not care about the session itself (that relies on a web-browsing policy) but will see which url is being accessed and then apply an action with a user-friendly interface if the action is 'negative': a block page will be presented for blocked categories, a continue page can be presented for 'questionable' categories and so on&lt;/P&gt;</description>
      <pubDate>Fri, 30 Jun 2017 10:35:39 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/url-category-versus-url-filtering-profile/m-p/164068#M53029</guid>
      <dc:creator>reaper</dc:creator>
      <dc:date>2017-06-30T10:35:39Z</dc:date>
    </item>
    <item>
      <title>Re: URL Category Versus URL Filtering Profile</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/url-category-versus-url-filtering-profile/m-p/164078#M53033</link>
      <description>&lt;P&gt;URL Category in the security policy match criteria allows you to &lt;U&gt;vary the security profiles based on the URL category&lt;/U&gt;. &amp;nbsp;Security profiles are things like AntiVirus Profiles, Vulnerability Profiles, WildFire Profiles, Anti-Spyware Profiles, File Blocking Profiles, Data Filtering Profiles, etc. &amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;One common use-case is to allow users to visit questionable URL categories, but restrict the file types they can download from those locations.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You need 2 security policy rules to accomplish this. &amp;nbsp;The first policy allows web-browsing with URL category = unknown/parked/insufficient, and then you attach a strict file blocking profile that prevents dangerous file types from being downloaded (PE, pdf, office, java, flash, etc.) &amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The 2nd security policy is for web-browsing in general, no URL category match, but then you can attach a less restrictive file blocking profile that allows PDFs, office docs, etc.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This concept/tactic is discussed in a little more detail in the "Best Practices for Ransomware Prevention" document, Step #4, found here:&lt;/P&gt;&lt;P&gt;&amp;nbsp;- &lt;A title="Best Practices for Ransomware Prevention" href="https://live.paloaltonetworks.com/t5/Featured-Articles/Best-Practices-for-Ransomware-Prevention/ta-p/74148" target="_blank"&gt;https://live.paloaltonetworks.com/t5/Featured-Articles/Best-Practices-for-Ransomware-Prevention/ta-p/74148&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 30 Jun 2017 12:56:07 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/url-category-versus-url-filtering-profile/m-p/164078#M53033</guid>
      <dc:creator>jvalentine</dc:creator>
      <dc:date>2017-06-30T12:56:07Z</dc:date>
    </item>
  </channel>
</rss>

