<?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 ASA/PIX Websense filter exception functionality in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-pix-websense-filter-exception-functionality/m-p/989023#M940669</link>
    <description>&lt;P&gt;So when you use the "filter url exception" command, does the firewall still inform the Websense server of the URL and just allows it out.  Or does the firewall totally not report on URLs from those addresses to Websense?&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 12:19:56 GMT</pubDate>
    <dc:creator>NotMeHere</dc:creator>
    <dc:date>2019-03-11T12:19:56Z</dc:date>
    <item>
      <title>ASA/PIX Websense filter exception functionality</title>
      <link>https://community.cisco.com/t5/network-security/asa-pix-websense-filter-exception-functionality/m-p/989023#M940669</link>
      <description>&lt;P&gt;So when you use the "filter url exception" command, does the firewall still inform the Websense server of the URL and just allows it out.  Or does the firewall totally not report on URLs from those addresses to Websense?&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 12:19:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-pix-websense-filter-exception-functionality/m-p/989023#M940669</guid>
      <dc:creator>NotMeHere</dc:creator>
      <dc:date>2019-03-11T12:19:56Z</dc:date>
    </item>
    <item>
      <title>Re: ASA/PIX Websense filter exception functionality</title>
      <link>https://community.cisco.com/t5/network-security/asa-pix-websense-filter-exception-functionality/m-p/989024#M940670</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;To accomplish URL filtering, pix can be configured with &lt;/P&gt;&lt;P&gt;&amp;gt; Websense (www.websense.com) or N2H2 (www.n2h2.com) in this way:&lt;/P&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;gt; a)A client establishes a TCP connection to a web server.&lt;/P&gt;&lt;P&gt;&amp;gt; b)The client sends an HTTP request for a page on this server. &lt;/P&gt;&lt;P&gt;&amp;gt; c)The pix intercepts this request and hands it over to the &lt;/P&gt;&lt;P&gt;&amp;gt; filtering server. d)The filtering server decides if the &lt;/P&gt;&lt;P&gt;&amp;gt; client should be allowed access to the requested page. e)If &lt;/P&gt;&lt;P&gt;&amp;gt; the decision is positive, the pix forwards the request to the &lt;/P&gt;&lt;P&gt;&amp;gt; server and the client receives the requested content. f)If &lt;/P&gt;&lt;P&gt;&amp;gt; the decision is negative, the client's request is dropped.&lt;/P&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;gt; NOTE: Websense works with pix version 5.3 onwards and N2H2 &lt;/P&gt;&lt;P&gt;&amp;gt; works with pix version 6.2 onwards. These can only perform &lt;/P&gt;&lt;P&gt;&amp;gt; HTTP filtering not FTP or HTTPS. Although for blocking ftp &lt;/P&gt;&lt;P&gt;&amp;gt; sites, a URL like &lt;A class="jive-link-custom" href="ftp://ftp.somedomain.com" target="_blank"&gt;ftp://ftp.somedomain.com&lt;/A&gt; can be entered.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;however pix do not report the query to websense when you run the exception command &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;hope it answers your Query&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Mar 2008 19:45:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-pix-websense-filter-exception-functionality/m-p/989024#M940670</guid>
      <dc:creator>abinjola</dc:creator>
      <dc:date>2008-03-19T19:45:37Z</dc:date>
    </item>
    <item>
      <title>Re: ASA/PIX Websense filter exception functionality</title>
      <link>https://community.cisco.com/t5/network-security/asa-pix-websense-filter-exception-functionality/m-p/989025#M940671</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;No the exception command removes websense from that traffic.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 25 Apr 2008 15:09:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-pix-websense-filter-exception-functionality/m-p/989025#M940671</guid>
      <dc:creator>ronj</dc:creator>
      <dc:date>2008-04-25T15:09:50Z</dc:date>
    </item>
    <item>
      <title>Re: ASA/PIX Websense filter exception functionality</title>
      <link>https://community.cisco.com/t5/network-security/asa-pix-websense-filter-exception-functionality/m-p/989026#M940672</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Actually in step c) the pix will send the request to the web server as well as checking with the filtering server to see if it is permitted. Then in step f) if the response is negative, the pix will drop the return packet from the web server.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 28 Apr 2008 17:38:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-pix-websense-filter-exception-functionality/m-p/989026#M940672</guid>
      <dc:creator>jogillis</dc:creator>
      <dc:date>2008-04-28T17:38:10Z</dc:date>
    </item>
    <item>
      <title>Re: ASA/PIX Websense filter exception functionality</title>
      <link>https://community.cisco.com/t5/network-security/asa-pix-websense-filter-exception-functionality/m-p/989027#M940673</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The firewall doesn't inform Websense, it just allow the traffic.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 May 2008 04:42:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-pix-websense-filter-exception-functionality/m-p/989027#M940673</guid>
      <dc:creator>rextillojr</dc:creator>
      <dc:date>2008-05-01T04:42:26Z</dc:date>
    </item>
  </channel>
</rss>

