<?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 Security rule for url filtering - best practices? in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/security-rule-for-url-filtering-best-practices/m-p/11190#M8233</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I would like to know what is the impact, if any, when configuring a security policy with allow action and associate with a url filtering profile if we use application as any or application set to web-browsing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I understand the url filtering is only applicable to web-browser traffic by default, but i want to understand what is the best thing to do and what impact come from a wrong choice.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note that this rule goal is not to allow or block traffic. It is goal is to only select traffic from a specific source address (or group) and apply a previous defined url filtering profile to it.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 07 May 2014 00:33:54 GMT</pubDate>
    <dc:creator>Borgiani</dc:creator>
    <dc:date>2014-05-07T00:33:54Z</dc:date>
    <item>
      <title>Security rule for url filtering - best practices?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/security-rule-for-url-filtering-best-practices/m-p/11190#M8233</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I would like to know what is the impact, if any, when configuring a security policy with allow action and associate with a url filtering profile if we use application as any or application set to web-browsing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I understand the url filtering is only applicable to web-browser traffic by default, but i want to understand what is the best thing to do and what impact come from a wrong choice.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note that this rule goal is not to allow or block traffic. It is goal is to only select traffic from a specific source address (or group) and apply a previous defined url filtering profile to it.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 07 May 2014 00:33:54 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/security-rule-for-url-filtering-best-practices/m-p/11190#M8233</guid>
      <dc:creator>Borgiani</dc:creator>
      <dc:date>2014-05-07T00:33:54Z</dc:date>
    </item>
    <item>
      <title>Re: Security rule for url filtering - best practices?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/security-rule-for-url-filtering-best-practices/m-p/11191#M8234</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Vladimir,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;URL filtering is triggered when there is a web-browsing or SSL traffic traversing the device, regardless of what you specify in the Application section of the security policy.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would argue that it is best practice to specify web-browsing (and/or SSL) as the permitted application(s), but this only helps to lock down that security policy further; it is not a requirement for the URL filtering to be triggered.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;P&gt;tasonibare&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 07 May 2014 19:34:54 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/security-rule-for-url-filtering-best-practices/m-p/11191#M8234</guid>
      <dc:creator>tasonibare</dc:creator>
      <dc:date>2014-05-07T19:34:54Z</dc:date>
    </item>
  </channel>
</rss>

