<?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: ASA 5505 and Websense Traffic Flow in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-5505-and-websense-traffic-flow/m-p/1595194#M591981</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;No, unfortunately there is no such feature. The ASA VPN and the Websense is independant of each other, and there is no feature that integrate the requirement that you have.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 11 Feb 2011 02:11:37 GMT</pubDate>
    <dc:creator>Jennifer Halim</dc:creator>
    <dc:date>2011-02-11T02:11:37Z</dc:date>
    <item>
      <title>ASA 5505 and Websense Traffic Flow</title>
      <link>https://community.cisco.com/t5/network-security/asa-5505-and-websense-traffic-flow/m-p/1595193#M591980</link>
      <description>&lt;P&gt;We use ASA 5505 appliances at our remote sites and connect to our core network over site to site&lt;/P&gt;&lt;P&gt;VPN's. We allow split tunneling from these remote ASA5505 for local PC's on the remote network segments for&lt;/P&gt;&lt;P&gt; Internet access. We have recently implemented Websense for web filtering and would like to intergate this with the ASA's. I have set this up in test and it works but it appears that all of the traffic is sent to Websense and routed out of our Corporate Internet connection. Is there a way to have it use the Websense&amp;nbsp; filtering service to see if the destination URL's are allowed or blocked but then have the traffic go out the local ISP of these remote location if the URL is allowed?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 19:49:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5505-and-websense-traffic-flow/m-p/1595193#M591980</guid>
      <dc:creator>mabouchard</dc:creator>
      <dc:date>2019-03-11T19:49:12Z</dc:date>
    </item>
    <item>
      <title>Re: ASA 5505 and Websense Traffic Flow</title>
      <link>https://community.cisco.com/t5/network-security/asa-5505-and-websense-traffic-flow/m-p/1595194#M591981</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;No, unfortunately there is no such feature. The ASA VPN and the Websense is independant of each other, and there is no feature that integrate the requirement that you have.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 11 Feb 2011 02:11:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5505-and-websense-traffic-flow/m-p/1595194#M591981</guid>
      <dc:creator>Jennifer Halim</dc:creator>
      <dc:date>2011-02-11T02:11:37Z</dc:date>
    </item>
    <item>
      <title>Re: ASA 5505 and Websense Traffic Flow</title>
      <link>https://community.cisco.com/t5/network-security/asa-5505-and-websense-traffic-flow/m-p/1595195#M591982</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You could exemt your websense box from the VPN interested traffic, so that it doesnt go over the tunnel.&lt;/P&gt;&lt;P&gt;You'll have to either play with the NAT rules on the site to site, ro give websense a diferent IP address.&lt;/P&gt;&lt;P&gt;That way when websense traffic hits the firewall, it isn't 'interested' therefore goes through the firewall as normal, rather than over the tunnel&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 11 Feb 2011 10:35:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5505-and-websense-traffic-flow/m-p/1595195#M591982</guid>
      <dc:creator>leesutcliffe</dc:creator>
      <dc:date>2011-02-11T10:35:08Z</dc:date>
    </item>
  </channel>
</rss>

