(Cloud) Why doesn't "SSL Pass Through" in ThreatPulse (cloud service) work?
search cancel

(Cloud) Why doesn't "SSL Pass Through" in ThreatPulse (cloud service) work?

book

Article ID: 165556

calendar_today

Updated On:

Products

Cloud Secure Web Gateway - Cloud SWG

Issue/Introduction

The domain name (example www.abc.com) for an HTTPS website is SSL excrypted. This means that without SSL interception, ThreatPulse cannot determine the domain name.

To effectively add SSL pass through, you must use its resolved IP address (by the domain names) of the target hosts (or its relative IP subnets). This enables the rule to bypass the IP address before the SSL handshake occurs.

 

Note: You can use NSLOOKUP to look up the IP address/es of the target domain.