Question 290
An administrator diagnoses new HTTPS failures after a FortiGate decryption rollout. The observed symptom is that engineers claim a failed HTTPS handshake is due to web filtering without a web-filter log. What should the engineer investigate or verify?
Explanation
Correct Answer
The appropriate control is to inspect SSL certificate/handshake diagnostics before altering URL categories. TLS setup can fail independently of a later web-filter decision.
Incorrect Answers
Verify the supported TLS versions and permitted cipher negotiation addresses a different symptom: a TLS service fails because the policy enforces an incompatible cipher or protocol. HTTPS negotiation can fail before any higher-layer content is inspected.
Apply a narrowly scoped approved inspection exemption for the pinned application is useful when one certificate-pinned mobile application stops connecting under deep inspection. Pinned clients reject substituted server certificates regardless of general CA trust.
Check certificate subject-alternative-name matching for the requested hostname addresses a different symptom: a browser reports a hostname mismatch only on a specific wildcard service. Wildcard and SAN scope determines which hostnames a certificate validates.