ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

How the SEP client communicates with WSS when integration is used'

book

Article ID: 199115

calendar_today

Updated On:

Products

Endpoint Protection Integration Component Endpoint Protection Web Security Service - WSS

Issue/Introduction

When you have a WSS integration policy assigned to your SEP client, you need to know if the network traffic, which leaves SEP client towards WSS proxy, is encrypted.

Cause

With WTR (Web Traffic Redirection) there are two loopback proxies setup.

The first is to go out to pull down "resolver.pac". This conversation is not encrypted.

The second loopback proxy via resolver.pac is encrypted.

Environment

Endpoint Protection and Web Security Services integration

Resolution

The first connection established by the client to go to WSS is not encrypted, this is only the request to pull resolver.pac. It is not the actual session with the website. The second time through the loopback the traffic during the browsing session is encrypted.

Additional Information

Best Practices SEP and WSS integration: https://knowledge.broadcom.com/external/article/173381/best-practices-for-endpoint-protection-a.html