<?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: FTD Rule Logic for URL Filtering in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ftd-rule-logic-for-url-filtering/m-p/3772546#M1012097</link>
    <description>Hi,&lt;BR /&gt;Could you brief your issue you are facing...?</description>
    <pubDate>Thu, 03 Jan 2019 21:33:34 GMT</pubDate>
    <dc:creator>Abheesh Kumar</dc:creator>
    <dc:date>2019-01-03T21:33:34Z</dc:date>
    <item>
      <title>FTD Rule Logic for URL Filtering</title>
      <link>https://community.cisco.com/t5/network-security/ftd-rule-logic-for-url-filtering/m-p/3761384#M1012094</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;
&lt;P&gt;I have been running into an issue with setting up rules in FTD specifically involving URL Filtering.&amp;nbsp; If I create a rule set like below:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Seq | Source int | Dest int | Source Add | Destination Add | Port | URL Categories | Action&lt;/P&gt;
&lt;P&gt;&amp;nbsp; 1&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;any&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; any&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;any&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; any&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;any&amp;nbsp; &amp;nbsp; Gambling,etc&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; Block&lt;/P&gt;
&lt;P&gt;&amp;nbsp; 2&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;out&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; inside&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; any&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;x.x.x.x&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;443&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;any&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;Allow&lt;/P&gt;
&lt;P&gt;&amp;nbsp; 3&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;inside&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;outside&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;any&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; any&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;any&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; any&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;Allow&lt;/P&gt;
&lt;P&gt;&amp;nbsp; Default Action&amp;nbsp; &amp;nbsp;- Block&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It appears Rule 1 for URL creates a permit ip any any and sends traffic to the snort engine for URL filtering, if it is not a blocked category or url , the traffic is passed without farther inspection.&amp;nbsp; Basically what I am seeing is everything is wide open inbound and the only rule to increment hit counter is rule # 1.&amp;nbsp; I have run into this issue twice on two different FTDs.&amp;nbsp; I am confused on why this is or if I am just not understanding something.&amp;nbsp; Anyone have a set up like this?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am checking which rule is being hit via packet trace when ssh'd into the FTD.&lt;/P&gt;
&lt;P&gt;Chris&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 16:33:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-rule-logic-for-url-filtering/m-p/3761384#M1012094</guid>
      <dc:creator>cmlozano8</dc:creator>
      <dc:date>2020-02-21T16:33:42Z</dc:date>
    </item>
    <item>
      <title>Re: FTD Rule Logic for URL Filtering</title>
      <link>https://community.cisco.com/t5/network-security/ftd-rule-logic-for-url-filtering/m-p/3761499#M1012095</link>
      <description>Hi,&lt;BR /&gt;For URL filtering create a rule like specifying the zones INSIDE to OUTSIDE and specify the URL category to BLOCK. &lt;BR /&gt;&lt;BR /&gt;HTH&lt;BR /&gt;Abheesh</description>
      <pubDate>Tue, 11 Dec 2018 18:18:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-rule-logic-for-url-filtering/m-p/3761499#M1012095</guid>
      <dc:creator>Abheesh Kumar</dc:creator>
      <dc:date>2018-12-11T18:18:50Z</dc:date>
    </item>
    <item>
      <title>Re: FTD Rule Logic for URL Filtering</title>
      <link>https://community.cisco.com/t5/network-security/ftd-rule-logic-for-url-filtering/m-p/3772517#M1012096</link>
      <description>Thanks Abheesh,  I think we had a misconception of how FTD rules work.</description>
      <pubDate>Thu, 03 Jan 2019 20:27:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-rule-logic-for-url-filtering/m-p/3772517#M1012096</guid>
      <dc:creator>cmlozano8</dc:creator>
      <dc:date>2019-01-03T20:27:50Z</dc:date>
    </item>
    <item>
      <title>Re: FTD Rule Logic for URL Filtering</title>
      <link>https://community.cisco.com/t5/network-security/ftd-rule-logic-for-url-filtering/m-p/3772546#M1012097</link>
      <description>Hi,&lt;BR /&gt;Could you brief your issue you are facing...?</description>
      <pubDate>Thu, 03 Jan 2019 21:33:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-rule-logic-for-url-filtering/m-p/3772546#M1012097</guid>
      <dc:creator>Abheesh Kumar</dc:creator>
      <dc:date>2019-01-03T21:33:34Z</dc:date>
    </item>
  </channel>
</rss>

