<?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 ASA5505 https filtering in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa5505-https-filtering/m-p/2110886#M394588</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Juoni,&lt;/P&gt;&lt;P&gt;but in this way won't we block all the google.com?&lt;/P&gt;&lt;P&gt;Robert&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 06 Dec 2012 21:08:53 GMT</pubDate>
    <dc:creator>robert_bukowicki</dc:creator>
    <dc:date>2012-12-06T21:08:53Z</dc:date>
    <item>
      <title>ASA5505 https filtering</title>
      <link>https://community.cisco.com/t5/network-security/asa5505-https-filtering/m-p/2110878#M394569</link>
      <description>&lt;P&gt;hi everybody,&lt;/P&gt;&lt;P&gt;I'd like to ask if it is possibility to block only gmail.com. gmail uses https. I don' t want to block google.com and I need to pass a few https web sites.&lt;/P&gt;&lt;P&gt;maybe it will be better when I block all https flow and pass only a few https web sites&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;P&gt;Robert&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 00:33:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa5505-https-filtering/m-p/2110878#M394569</guid>
      <dc:creator>robert_bukowicki</dc:creator>
      <dc:date>2019-03-12T00:33:45Z</dc:date>
    </item>
    <item>
      <title>ASA5505 https filtering</title>
      <link>https://community.cisco.com/t5/network-security/asa5505-https-filtering/m-p/2110879#M394571</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Robert,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can filter connection requests that originate outobund although you can&amp;nbsp; use acces list in order to prevent outbound access to&amp;nbsp; specific content servers, it is difficult to manage usage this way&amp;nbsp; because of the size and dynamic nature of the Internet, regular ACL can block gmail.com IP address (whatever resolves on the nslookup) but if the IP change (most likely) then the ASA allows gmail to go through. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can simplify&amp;nbsp; configuration and improve security appliance performance with the use&amp;nbsp; of a separate server that runs Internet filtering product such as websense or N2H2. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CSC module also offers URL content filtering features that can block HTTPS request. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Juan Lombana&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please rate helpful posts.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Dec 2012 15:56:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa5505-https-filtering/m-p/2110879#M394571</guid>
      <dc:creator>julomban</dc:creator>
      <dc:date>2012-12-06T15:56:42Z</dc:date>
    </item>
    <item>
      <title>ASA5505 https filtering</title>
      <link>https://community.cisco.com/t5/network-security/asa5505-https-filtering/m-p/2110880#M394573</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi Juan,&lt;/P&gt;&lt;P&gt;thanks for your answer, but CSC module is not suitable for ASA5505.&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;&lt;P&gt;Robert&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Dec 2012 19:45:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa5505-https-filtering/m-p/2110880#M394573</guid>
      <dc:creator>robert_bukowicki</dc:creator>
      <dc:date>2012-12-06T19:45:24Z</dc:date>
    </item>
    <item>
      <title>ASA5505 https filtering</title>
      <link>https://community.cisco.com/t5/network-security/asa5505-https-filtering/m-p/2110881#M394575</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Robert,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am sorry I forgot for a second that you have an ASA5505. Then your best option is a websense device doing deep HTTPS filtering. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Juan Lombana&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please rate helpful posts.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Dec 2012 19:55:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa5505-https-filtering/m-p/2110881#M394575</guid>
      <dc:creator>julomban</dc:creator>
      <dc:date>2012-12-06T19:55:30Z</dc:date>
    </item>
    <item>
      <title>ASA5505 https filtering</title>
      <link>https://community.cisco.com/t5/network-security/asa5505-https-filtering/m-p/2110882#M394577</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Juan,&lt;/P&gt;&lt;P&gt;so we've got 2 options:&lt;/P&gt;&lt;P&gt;1. pricier: purchase of a websense device&lt;/P&gt;&lt;P&gt;or&lt;/P&gt;&lt;P&gt;2. cheaper: creating ACL and checking gmail.com IP addrerss every day.&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;&lt;P&gt;Robert&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Dec 2012 20:11:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa5505-https-filtering/m-p/2110882#M394577</guid>
      <dc:creator>robert_bukowicki</dc:creator>
      <dc:date>2012-12-06T20:11:40Z</dc:date>
    </item>
    <item>
      <title>Re: ASA5505 https filtering</title>
      <link>https://community.cisco.com/t5/network-security/asa5505-https-filtering/m-p/2110883#M394580</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the newer ASA softwares its possible to configure the ASA to do DNS lookups and use FQDN in the access-list.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ASA will then update the IP address every now and then to the access-list rule using the FQDN.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Though this is not a very efficient way to block the site by itself.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Jouni&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Dec 2012 20:15:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa5505-https-filtering/m-p/2110883#M394580</guid>
      <dc:creator>Jouni Forss</dc:creator>
      <dc:date>2012-12-06T20:15:22Z</dc:date>
    </item>
    <item>
      <title>ASA5505 https filtering</title>
      <link>https://community.cisco.com/t5/network-security/asa5505-https-filtering/m-p/2110884#M394582</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi Jouni,&lt;/P&gt;&lt;P&gt;I use the newest vesion of ASA software (9.0.1)&lt;/P&gt;&lt;P&gt;could you tell me how to configure it in a few steps?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Dec 2012 20:44:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa5505-https-filtering/m-p/2110884#M394582</guid>
      <dc:creator>robert_bukowicki</dc:creator>
      <dc:date>2012-12-06T20:44:14Z</dc:date>
    </item>
    <item>
      <title>Re: ASA5505 https filtering</title>
      <link>https://community.cisco.com/t5/network-security/asa5505-https-filtering/m-p/2110885#M394585</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The very simplest version would be this&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I configured this on my home ASA just now&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;WAN = my "outside" interface&lt;/LI&gt;&lt;LI&gt;LAN-IN = my local LANs interface ACL&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;dns domain-lookup WAN&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;dns server-group DefaultDNS&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt; name-server x.x.x.x&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt; name-server y.y.y.y&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;object network GMAIL&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt; fqdn gmail.google.com&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;access-list LAN-IN line 1 deny ip any object GMAIL&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;show access-list LAN-IN&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;access-list LAN-IN line 1 extended deny ip any object GMAIL 0x6eafaae2&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp; access-list LAN-IN line 1 extended deny ip any fqdn gmail.google.com (resolved) 0x14e1856b&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp; access-list LAN-IN line 1 extended deny ip any host 173.194.32.39 (gmail.google.com) (hitcnt=0) 0x6eafaae2&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp; access-list LAN-IN line 1 extended deny ip any host 173.194.32.40 (gmail.google.com) (hitcnt=0) 0x6eafaae2&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp; access-list LAN-IN line 1 extended deny ip any host 173.194.32.34 (gmail.google.com) (hitcnt=0) 0x6eafaae2&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp; access-list LAN-IN line 1 extended deny ip any host 173.194.32.32 (gmail.google.com) (hitcnt=0) 0x6eafaae2&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp; access-list LAN-IN line 1 extended deny ip any host 173.194.32.41 (gmail.google.com) (hitcnt=0) 0x6eafaae2&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp; access-list LAN-IN line 1 extended deny ip any host 173.194.32.33 (gmail.google.com) (hitcnt=0) 0x6eafaae2&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp; access-list LAN-IN line 1 extended deny ip any host 173.194.32.36 (gmail.google.com) (hitcnt=0) 0x6eafaae2&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp; access-list LAN-IN line 1 extended deny ip any host 173.194.32.35 (gmail.google.com) (hitcnt=0) 0x6eafaae2&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp; access-list LAN-IN line 1 extended deny ip any host 173.194.32.38 (gmail.google.com) (hitcnt=0) 0x6eafaae2&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp; access-list LAN-IN line 1 extended deny ip any host 173.194.32.37 (gmail.google.com) (hitcnt=0) 0x6eafaae2&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp; access-list LAN-IN line 1 extended deny ip any host 173.194.32.46 (gmail.google.com) (hitcnt=0) 0x6eafaae2&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Though I kinda have a feeling this might block something you are not wanting to block.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I guess some solution might be to block DNS replies from coming in when the host queries for the gmail DNS name.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Jouni&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Dec 2012 20:50:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa5505-https-filtering/m-p/2110885#M394585</guid>
      <dc:creator>Jouni Forss</dc:creator>
      <dc:date>2012-12-06T20:50:48Z</dc:date>
    </item>
    <item>
      <title>ASA5505 https filtering</title>
      <link>https://community.cisco.com/t5/network-security/asa5505-https-filtering/m-p/2110886#M394588</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Juoni,&lt;/P&gt;&lt;P&gt;but in this way won't we block all the google.com?&lt;/P&gt;&lt;P&gt;Robert&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Dec 2012 21:08:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa5505-https-filtering/m-p/2110886#M394588</guid>
      <dc:creator>robert_bukowicki</dc:creator>
      <dc:date>2012-12-06T21:08:53Z</dc:date>
    </item>
    <item>
      <title>ASA5505 https filtering</title>
      <link>https://community.cisco.com/t5/network-security/asa5505-https-filtering/m-p/2110887#M394590</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In cases like Google or Facebook I'm afraid this wont be that good solution or might not even work that well.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And usually there is some way around it anyway&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Jouni&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Dec 2012 21:12:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa5505-https-filtering/m-p/2110887#M394590</guid>
      <dc:creator>Jouni Forss</dc:creator>
      <dc:date>2012-12-06T21:12:45Z</dc:date>
    </item>
    <item>
      <title>ASA5505 https filtering</title>
      <link>https://community.cisco.com/t5/network-security/asa5505-https-filtering/m-p/2110888#M394592</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Robert,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;At the end the ASA is not your best option to block based on URL's. A URL filtering device such as websense is your best option, I know it is expensive however it is design for this type of blocking. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Juan Lombana&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please rate helpful posts.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Dec 2012 21:25:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa5505-https-filtering/m-p/2110888#M394592</guid>
      <dc:creator>julomban</dc:creator>
      <dc:date>2012-12-06T21:25:24Z</dc:date>
    </item>
  </channel>
</rss>

