Are you trying to use the WSA as an "inline" device? It is not designed to do that...
It sits to the side of the flow and you direct traffic to it one of 2 ways: WCCP off of your ASA, or via proxy settings on the client, whether you do it manually, PAC file, group policy...
M1 should be connected, that's your managment interface.
P1 should be connected, and you run WCCP on the ASA to get traffice to it so that that traffic gets proxied.
T1 can be connected, and you echo the port that the ASA is connected to the port that T1 is connected to to get the L4 traffic monitoring (its the destination for an ethernet tap, the WSA doesn't do the ethernet tap itself)
Take a look at the quickstart guide (you should have one on paper in the box).
For all versions of the Email Security Appliance (ESA) and Security Management Appliance (SMA), some Secure Sockets Link (SSL) certificates issued from the QuoVadis root certificate authority (CA) trust chain before 2021-03-31 cannot b...
Automation and programmability for networking and security are increasingly important topics. Every release since ISE 1.2 has included new REST API capabilities to better automate and integrate ISE with the rest of your network, appli...
The latest iteration (v2.3.4) of the Cisco Secure Firewall Migration Tool adds public beta support for S2S VPN migrations from ASA:
Policy-based (crypto map) Pre-Shared key authentication type VPN configuration to Firepower Management Center
Cisco Defense Orchestrator (CDO) is a cloud-based, multi-device manager that manages security products like Adaptive Security Appliance (ASA), Firepower Threat Defense next-generation firewall, and Meraki devices, to name a few.
We make improvement...
This document presents the ISE data limiting best practices that can dramatically improve the system performance on ISE.
Your deployment may be impacted if the alarms tab on ISE shows High load average, high CPU or high memoy usage alarm...