<?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  Websense in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-websense/m-p/1371669#M750380</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I would consider having an onsite server act as a local Filtering service agent. &lt;/P&gt;&lt;P&gt;With Websense you can install distributed filter agents and have them controlled from the same policy server.&amp;nbsp; This allows the websense filtered traffic to quickly be checked against the local filter agent server. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Alternately it may be possible to configure the remote firewall to directly send the requests to the Websense server through the VPN. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;url-server (outside) host 172.2.2.2&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Your VPN access-lists would need to encrypt traffic between your outside interface IP number and your internal network at the remote location.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list vpn-remote-to-central permit ip host 24.4.4.4 172.2.2.0 255.255.255.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(reverse of that on the central site of course, and add the traffic to your nat 0 access-lists)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A long time ago I did something like this, havent had to in a while though, so I'd test it before putting into production.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 14 Feb 2010 05:19:11 GMT</pubDate>
    <dc:creator>cmcbride</dc:creator>
    <dc:date>2010-02-14T05:19:11Z</dc:date>
    <item>
      <title>ASA  Websense</title>
      <link>https://community.cisco.com/t5/network-security/asa-websense/m-p/1371668#M750377</link>
      <description>&lt;P&gt;If I have ASA's in remote locations with site to site tunnels to the home office where the websense is, can I have the remote ASA make calls to websense like a router can?&amp;nbsp; If so, how do I force the source address from the remote ASA so it is an encrypted vpn packet.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thx.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 17:02:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-websense/m-p/1371668#M750377</guid>
      <dc:creator>whanson</dc:creator>
      <dc:date>2019-03-11T17:02:52Z</dc:date>
    </item>
    <item>
      <title>Re: ASA  Websense</title>
      <link>https://community.cisco.com/t5/network-security/asa-websense/m-p/1371669#M750380</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I would consider having an onsite server act as a local Filtering service agent. &lt;/P&gt;&lt;P&gt;With Websense you can install distributed filter agents and have them controlled from the same policy server.&amp;nbsp; This allows the websense filtered traffic to quickly be checked against the local filter agent server. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Alternately it may be possible to configure the remote firewall to directly send the requests to the Websense server through the VPN. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;url-server (outside) host 172.2.2.2&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Your VPN access-lists would need to encrypt traffic between your outside interface IP number and your internal network at the remote location.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list vpn-remote-to-central permit ip host 24.4.4.4 172.2.2.0 255.255.255.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(reverse of that on the central site of course, and add the traffic to your nat 0 access-lists)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A long time ago I did something like this, havent had to in a while though, so I'd test it before putting into production.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 14 Feb 2010 05:19:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-websense/m-p/1371669#M750380</guid>
      <dc:creator>cmcbride</dc:creator>
      <dc:date>2010-02-14T05:19:11Z</dc:date>
    </item>
  </channel>
</rss>

