I am currently implementing a WSA in a Cisco ASA environment. For all internal devices I use WCCP (the WSA is on inside from the firewall perspective).
However, in the environment there is also a guest network terminating on a DMZ of the firewall. Because of the limitiations in ASA I cant use WCCP for this traffic.
Which is the recommended approach to "proxify" the guest users internet traffic? If possible I want to avoid proxy settings in the devices since this is a network with unknown device types. Also, I want to avoid proxy auto-discovery for the same reason.
Yes, there is a VM infrastructure. However, I don´t really like the idea with one more WSA-instance with its own configuration to manage just for the guest network.
How is this solved in other environments? Is proxy auto-discovery for guest (unmanaged devices) a recommended approach? Is there a way to make this totally transparent for the guest users even though they resides on a DMZ and the WSA is on the inside?
One option is to seperate a guest network by using a seperate subnet rather internally rather then have the guests on the DMZ. Then you may setup an identity based on that subnet. Once you have that identity setup add it to a access policy and define which categories you would like to block, monitor or allow. Remeber when you allow a category the WSA will not use its scanning engines for example, WBRS Web Reputation Score, Webroot or Anti Virus. This will allow you to seprately control the guest network through the WSA. This is the most common setup which I see often.
Erik Kaiser WSA CSE WSA Cisco Forums Moderator
WSA Cisco Forums Moderator
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...