The correct answer is C. HTTPS Inspection requires the Security Gateway to inspect encrypted TLS/SSL traffic. For outbound HTTPS Inspection, the gateway effectively creates separate encrypted sessions: one between the client and gateway, and another between the gateway and the external server. To do this without browser certificate warnings, the gateway must use an outbound Certificate Authority certificate that client systems trust. Official R82 HTTPS Inspection documentation states that the first time HTTPS Inspection is enabled on a Security Gateway, the administrator must create an outbound CA certificate or import a CA certificate already deployed in the organization. Option A is wrong because URL Filtering can benefit from HTTPS Inspection but is not the essential certificate component. Option B is incorrect because DNS resolution alone does not enable TLS interception. Option D is unrelated; NAT controls address translation, not certificate-based inspection of encrypted HTTPS traffic. Without the CA certificate and correct trust deployment to endpoints, HTTPS Inspection would either fail or generate certificate trust warnings for users. Reference topics: HTTPS Inspection, outbound CA certificate, certificate deployment, encrypted traffic inspection.
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