<?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: inspect HTTPS in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/inspect-https/m-p/1343129#M76565</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;A quick feasible option would be to use WCCP on the ASA and forward all HTTPS traffic to a Squid proxy server and then use the tool ufdbGuard (&lt;A class="jive-link-custom" href="http://www.urlfilterdb.com/download/software/index.shtml" target="_blank"&gt;http://www.urlfilterdb.com/download/software/index.shtml&lt;/A&gt;) along with Squid to block traffic.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can create specific ACL's to redirect traffic with WCCP on ASa.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 30 Sep 2009 14:37:27 GMT</pubDate>
    <dc:creator>dhananjoy chowdhury</dc:creator>
    <dc:date>2009-09-30T14:37:27Z</dc:date>
    <item>
      <title>inspect HTTPS</title>
      <link>https://community.cisco.com/t5/network-security/inspect-https/m-p/1343128#M76564</link>
      <description>&lt;P&gt;I'm curious if there is a way to stop tunneling applications out HTTPS with ASA 5500.  I know everything is encrypted but is there a way to at least inspect the traffic to make sure it complies with RFC 2818?  Perhaps there's another way to provide some security?&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 11:46:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/inspect-https/m-p/1343128#M76564</guid>
      <dc:creator>snickered</dc:creator>
      <dc:date>2019-03-10T11:46:36Z</dc:date>
    </item>
    <item>
      <title>Re: inspect HTTPS</title>
      <link>https://community.cisco.com/t5/network-security/inspect-https/m-p/1343129#M76565</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;A quick feasible option would be to use WCCP on the ASA and forward all HTTPS traffic to a Squid proxy server and then use the tool ufdbGuard (&lt;A class="jive-link-custom" href="http://www.urlfilterdb.com/download/software/index.shtml" target="_blank"&gt;http://www.urlfilterdb.com/download/software/index.shtml&lt;/A&gt;) along with Squid to block traffic.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can create specific ACL's to redirect traffic with WCCP on ASa.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Sep 2009 14:37:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/inspect-https/m-p/1343129#M76565</guid>
      <dc:creator>dhananjoy chowdhury</dc:creator>
      <dc:date>2009-09-30T14:37:27Z</dc:date>
    </item>
    <item>
      <title>Re: inspect HTTPS</title>
      <link>https://community.cisco.com/t5/network-security/inspect-https/m-p/1343130#M76566</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;is there another tool to run on windows with squid proxy&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 14 Apr 2013 09:11:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/inspect-https/m-p/1343130#M76566</guid>
      <dc:creator>m-mostafa</dc:creator>
      <dc:date>2013-04-14T09:11:46Z</dc:date>
    </item>
  </channel>
</rss>

