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? If so, how do I force the source address from the remote ASA so it is an encrypted vpn packet.
I would consider having an onsite server act as a local Filtering service agent.
With Websense you can install distributed filter agents and have them controlled from the same policy server. This allows the websense filtered traffic to quickly be checked against the local filter agent server.
Alternately it may be possible to configure the remote firewall to directly send the requests to the Websense server through the VPN.
url-server (outside) host 126.96.36.199
Your VPN access-lists would need to encrypt traffic between your outside interface IP number and your internal network at the remote location.
access-list vpn-remote-to-central permit ip host 188.8.131.52 184.108.40.206 255.255.255.0
(reverse of that on the central site of course, and add the traffic to your nat 0 access-lists)
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.
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...