During deployment of Advanced Threat Protection (ATP) Platform in an environment with a proxy, or after adding a proxy in an environment where ATP Platform is already deployed, the system status begins to show "ATP is Critical" in red.
Traffic from ATP Platform passes through ProxySG or a third party proxy
The System Health status of ATP displays "ATP is Critical" in red.
On mouseover of "ATP is Critical", one of the messages displayed is "Unsupported proxy configuration. Configured proxy is intercepting secure communication. Component(s) affected: LicenseUpdate."
ATP does not support the interception of its SSL communication to and from the Symantec licensing servers. This behavior is by design.
Provide a network route between the ATP platform's MGMT interface and the internet where SSL traffic is not intercepted.
For proxies not published by Symantec, please consult with your manufacturer or vendor for a workaround. You may need to consult Appendix D of the Symantec™ Advanced Threat Protection 3.2 Administration Guide, available here:
To workaround this behavior within Symantec ProxySG
If the environment includes SSLV, please contact support for further assistance.
If the ProxySG is transparently deployed, do one of the following: If the source IP is allowed out to the Internet, then add the ATP server IP as a source IP to the proxy bypass list. If the source IP is not allowed out to the Internet, then add a TCP Tunnel service with the source IP being the ATP Platform
If the ProxySG is explicitly deployed, do one of the following: If the source IP is allowed out to the Internet, then disable the Network Proxy settings within the UI of the ATP Platform If the source IP is not allowed out to the Internet, then add the following policy lines to the local policy file of the ProxySG: