<?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 URL Filtering on ASA with RegEx, but getting unexpected results in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/url-filtering-on-asa-with-regex-but-getting-unexpected-results/m-p/2165199#M361027</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Let's try it the easy way:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regex dropbox "\dropbox\.com"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;class-map type inspect http match-any block-url-class&amp;nbsp; &lt;/P&gt;&lt;P&gt;match request header host regex dropbox&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; policy-map type inspect http block-url-policy&amp;nbsp; &lt;/P&gt;&lt;P&gt; parameters&amp;nbsp; &lt;/P&gt;&lt;P&gt;&amp;nbsp; class block-url-class&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; drop-connection log &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;policy-map global_policy&amp;nbsp; &lt;/P&gt;&lt;P&gt;class inspection_default&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;inspect http block-url-policy&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 01 Mar 2013 22:06:48 GMT</pubDate>
    <dc:creator>jocamare</dc:creator>
    <dc:date>2013-03-01T22:06:48Z</dc:date>
    <item>
      <title>URL Filtering on ASA with RegEx, but getting unexpected results</title>
      <link>https://community.cisco.com/t5/network-security/url-filtering-on-asa-with-regex-but-getting-unexpected-results/m-p/2165198#M361024</link>
      <description>&lt;P&gt;I'm trying to block access to dropbox.com on our ASA5510. I have it setup and it blocks dropbox.com just fine. But it is also blocking google.com. I can't figure out why. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here's my config. When it blocks google, it blocks it with the &lt;/P&gt;&lt;P&gt;terminated by inspection engine, reason - disconnected, dropped packet.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regex Block_Dropbox "\.dropbox\.com"&lt;/P&gt;&lt;P&gt;access-list URL_Filtering extended permit tcp any any eq www&lt;/P&gt;&lt;P&gt;access-list URL_Filtering extended permit tcp any any eq https&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;class-map type regex match-any Block_Domains&lt;/P&gt;&lt;P&gt;match regex Block_Dropbox&lt;/P&gt;&lt;P&gt;class-map type inspect http match-all Block_These_Domains&lt;/P&gt;&lt;P&gt;match request header host regex class Block_Domains&lt;/P&gt;&lt;P&gt;class-map inspection_default&lt;/P&gt;&lt;P&gt;match default-inspection-traffic&lt;/P&gt;&lt;P&gt;class-map httptraffic&lt;/P&gt;&lt;P&gt;match access-list URL_Filtering&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;policy-map type inspect dns preset_dns_map&lt;/P&gt;&lt;P&gt;parameters&lt;/P&gt;&lt;P&gt;message-length maximum 512&lt;/P&gt;&lt;P&gt;policy-map type inspect http http_inspection_policy&lt;/P&gt;&lt;P&gt;parameters&lt;/P&gt;&lt;P&gt;protocol-violation action drop-connection&lt;/P&gt;&lt;P&gt;class Block_These_Domains&lt;/P&gt;&lt;P&gt;drop-connection&lt;/P&gt;&lt;P&gt;policy-map global_policy&lt;/P&gt;&lt;P&gt;class inspection_default&lt;/P&gt;&lt;P&gt;inspect dns preset_dns_map &lt;/P&gt;&lt;P&gt;inspect ftp &lt;/P&gt;&lt;P&gt;inspect h323 h225 &lt;/P&gt;&lt;P&gt;inspect h323 ras &lt;/P&gt;&lt;P&gt;inspect netbios &lt;/P&gt;&lt;P&gt;inspect rsh &lt;/P&gt;&lt;P&gt;inspect rtsp &lt;/P&gt;&lt;P&gt;inspect skinny &lt;/P&gt;&lt;P&gt;inspect esmtp &lt;/P&gt;&lt;P&gt;inspect sqlnet &lt;/P&gt;&lt;P&gt;inspect sunrpc &lt;/P&gt;&lt;P&gt;inspect tftp &lt;/P&gt;&lt;P&gt;inspect sip &lt;/P&gt;&lt;P&gt;inspect xdmcp &lt;/P&gt;&lt;P&gt;policy-map inside-policy&lt;/P&gt;&lt;P&gt;class httptraffic&lt;/P&gt;&lt;P&gt;inspect http http_inspection_policy&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;service-policy global_policy global&lt;/P&gt;&lt;P&gt;service-policy inside-policy interface inside&lt;SPAN id="mce_marker"&gt; &lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 01:08:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/url-filtering-on-asa-with-regex-but-getting-unexpected-results/m-p/2165198#M361024</guid>
      <dc:creator>abrrymnvette</dc:creator>
      <dc:date>2019-03-12T01:08:21Z</dc:date>
    </item>
    <item>
      <title>URL Filtering on ASA with RegEx, but getting unexpected results</title>
      <link>https://community.cisco.com/t5/network-security/url-filtering-on-asa-with-regex-but-getting-unexpected-results/m-p/2165199#M361027</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Let's try it the easy way:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regex dropbox "\dropbox\.com"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;class-map type inspect http match-any block-url-class&amp;nbsp; &lt;/P&gt;&lt;P&gt;match request header host regex dropbox&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; policy-map type inspect http block-url-policy&amp;nbsp; &lt;/P&gt;&lt;P&gt; parameters&amp;nbsp; &lt;/P&gt;&lt;P&gt;&amp;nbsp; class block-url-class&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; drop-connection log &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;policy-map global_policy&amp;nbsp; &lt;/P&gt;&lt;P&gt;class inspection_default&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;inspect http block-url-policy&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Mar 2013 22:06:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/url-filtering-on-asa-with-regex-but-getting-unexpected-results/m-p/2165199#M361027</guid>
      <dc:creator>jocamare</dc:creator>
      <dc:date>2013-03-01T22:06:48Z</dc:date>
    </item>
    <item>
      <title>URL Filtering on ASA with RegEx, but getting unexpected results</title>
      <link>https://community.cisco.com/t5/network-security/url-filtering-on-asa-with-regex-but-getting-unexpected-results/m-p/2165200#M361029</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Why matching HTTPS in the ACL if this is an HTTP inspection?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please just use the HTTP protocol on the ACL and give it a try ( clear local-host ) before the test&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Mar 2013 22:07:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/url-filtering-on-asa-with-regex-but-getting-unexpected-results/m-p/2165200#M361029</guid>
      <dc:creator>Julio Carvajal</dc:creator>
      <dc:date>2013-03-01T22:07:21Z</dc:date>
    </item>
    <item>
      <title>URL Filtering on ASA with RegEx, but getting unexpected results</title>
      <link>https://community.cisco.com/t5/network-security/url-filtering-on-asa-with-regex-but-getting-unexpected-results/m-p/2165201#M361030</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; That works for dropbox.com, but when I use &lt;A href="https://www.dropbox.com"&gt;https://www.dropbox.com&lt;/A&gt; I can still get through. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Mar 2013 22:48:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/url-filtering-on-asa-with-regex-but-getting-unexpected-results/m-p/2165201#M361030</guid>
      <dc:creator>abrrymnvette</dc:creator>
      <dc:date>2013-03-01T22:48:06Z</dc:date>
    </item>
    <item>
      <title>URL Filtering on ASA with RegEx, but getting unexpected results</title>
      <link>https://community.cisco.com/t5/network-security/url-filtering-on-asa-with-regex-but-getting-unexpected-results/m-p/2165202#M361031</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Because if if I use https, I can still get to the website. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Mar 2013 22:49:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/url-filtering-on-asa-with-regex-but-getting-unexpected-results/m-p/2165202#M361031</guid>
      <dc:creator>abrrymnvette</dc:creator>
      <dc:date>2013-03-01T22:49:09Z</dc:date>
    </item>
    <item>
      <title>URL Filtering on ASA with RegEx, but getting unexpected results</title>
      <link>https://community.cisco.com/t5/network-security/url-filtering-on-asa-with-regex-but-getting-unexpected-results/m-p/2165203#M361032</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Encrypted traffic, end of the road.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The ASA won't be able to see the request on the HTTP request, so it won't block it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The CSC module is a good partner in crime when blocking HTTPS on the ASA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But, we don't always have a spare CSC to use, so, here's something you can try:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can block HTTPS by dropping the DNS request.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For this to work properly the DNS request for resolving the&amp;nbsp; ip of HTTPS URL must go through ASA which means if user and it's DNS&amp;nbsp; server both are behind same interface of ASA then this would not work.&amp;nbsp; As we are dropping the blocked web-site request during it's DNS&amp;nbsp; resolution Request.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As this solution works based on dropping the DNS server reply&amp;nbsp; thereby this does not only block HTTPS but any other kind of traffic as&amp;nbsp; well (HTTP, FTP, etc.) where the user accesses a server using its name&amp;nbsp; and hence has to perform a DNS query. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="text-decoration: underline; "&gt;What to do:&lt;BR /&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTTPS websites use a SSL tunnel from the end device to the end&amp;nbsp; server, so the firewall isn’t capable of inspecting the SSL traffic. So&amp;nbsp; Instead of using URL inspection, we can configure DNS inspection.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; The ASA inspects the DNS request from the internal DNS server or end&amp;nbsp; device to the external DNS server. We can use regular expressions to&amp;nbsp; match the FQDN of a website. Below is an example configuration of&amp;nbsp; blocking access to the website (and applications using a DNS entry to&amp;nbsp; this website) facebook.com&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; regex domain_facebook.com “\.facebook\.com”&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; !&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; class-map type regex match-any DomainBlockList&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; match regex domain_facebook.com&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; !&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; policy-map type inspect dns Pol-DNS-inspect&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; parameters&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; message-length maximum 512&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; match domain-name regex class DomainBlockList&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; drop-connection log&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; !&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; policy-map global_policy&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; class inspection_default&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; inspect dns Pol-DNS-inspect&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; !&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; service-policy global_policy global&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A problem with this approach could be the DNS cache on the internal&amp;nbsp; DNS server. This is domain name is queried before configuring the&amp;nbsp; inspection, the domain will be available until the DNS cache from the&amp;nbsp; DNS server expires. In urgent situation you can maybe clear the DNS&amp;nbsp; cache yourself.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Mar 2013 23:00:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/url-filtering-on-asa-with-regex-but-getting-unexpected-results/m-p/2165203#M361032</guid>
      <dc:creator>jocamare</dc:creator>
      <dc:date>2013-03-01T23:00:31Z</dc:date>
    </item>
    <item>
      <title>URL Filtering on ASA with RegEx, but getting unexpected results</title>
      <link>https://community.cisco.com/t5/network-security/url-filtering-on-asa-with-regex-but-getting-unexpected-results/m-p/2165204#M361033</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Also...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can use FQDN along with Access-lists so the DNS request doesn't have to go through the ASA.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Mar 2013 23:02:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/url-filtering-on-asa-with-regex-but-getting-unexpected-results/m-p/2165204#M361033</guid>
      <dc:creator>jocamare</dc:creator>
      <dc:date>2013-03-01T23:02:20Z</dc:date>
    </item>
  </channel>
</rss>

