Upstream security appliance only sees traffic as coming from the Cisco WSA proxy
So we have a new security appliance near our edge. It is only reporting traffic as coming from the web proxy...which is the job of a proxy, perfect. Except it is making security research efforts a pain in the ass cross referencing the actual internal host and where they're going. I am constantly switching back and forth between the proxy and security appliance trying to figure who/what/where/when.
Research shows X-forwarded-for (XFF) can be turned on within the cisco WSA proxy to attach a header allowing said security appliance to get a proper host IP address, and not just the proxy itself.
Does anyone have any experience in setting up proper XFF within a web proxy? I have been back and forth with our local Cisco SE, and then TAC, and all they keep saying is for me to check this one box about forwarding XFF traffic, and it still does not work.
Posted Mar 16, 2022, 10:12 PM UTC
It is just one box to enable XFF. But, if the traffic is encrypted, it needs to be decrypted to add the header. The upstream device needs to also understand the XFF header, also needs to decrypt the traffic, and may need to be configured to use the XFF header.
Yeah downstream device definitely needs to be able to check for the value of that header. See if you can force tls with a cert for destination controls in the WSA. If you have a Designated Service Manager assigned for your contract then hit them up for guidance, they're always super useful.