ZIA TLS Inspection secures HTTPS browsing by dynamically creating intermediate certificates for client sessions. The proxy terminates the TLS session, inspects headers and payload when policy requires it, and then re-encrypts traffic toward the destination. This lets Zscaler identify malware, phishing, DLP violations, and policy risks hidden inside encrypted sessions. Option C (Intermediate certificates are created for each client connection) is correct because intermediate certificate generation is what allows the browser to maintain a trusted encrypted session while Zscaler performs inspection.
Why the other options are incorrect:
A. Storing connection streams for future customer review: Storing full connection streams would be packet/session archiving. TLS inspection works by proxying and re-signing certificates, not by saving streams for later review.
B. Removing certificates and reconnecting client connection using HTTP: Downgrading HTTPS to HTTP would remove encryption and break the security model. ZIA keeps secure sessions by issuing an intermediate certificate and re-encrypting traffic.
D. Logging which clients receive the original webserver certificate: Logging original-certificate recipients is audit information at best. It does not explain how ZIA secures and inspects the TLS session.
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit