Question 690
A FortiSASE operator faces this issue: A project team enables SSL inspection for internet traffic but fails to deploy the trusted CA to managed endpoints. What corrective configuration or investigation is most appropriate?
Explanation
Correct Answer
Apply this remedy rather than changing unrelated policies: Deploy the approved inspection CA and test trusted and untrusted certificates. This follows from the fact that client trust material is necessary for supported HTTPS inspection without pervasive certificate warnings. The expected result is: Managed endpoints browse inspected HTTPS without invalid-certificate workarounds.
Incorrect Answers
That proposal leaves the central dependency unresolved. The correction is: Deploy the approved inspection CA and test trusted and untrusted certificates. The expected acceptance result is: Managed endpoints browse inspected HTTPS without invalid-certificate workarounds.
This alternative addresses the separate case “An application uses certificate pinning and fails only when full HTTPS inspection is enabled”. The focused remedy is: Create a narrowly approved inspection exception only where technically necessary and permitted. The deciding requirement here is “Deploy the approved inspection CA and test trusted and untrusted certificates”.
The related but distinct situation is “A bank requires inspection of file uploads to a sanctioned SaaS service but the SASE deployment enforces only URL categories”. The focused remedy is: Apply the supported SaaS or DLP inspection control for the sensitive upload action. For the stated problem, “Deploy the approved inspection CA and test trusted and untrusted certificates” addresses the central condition.