Question 500
A Fortinet SD-WAN/FortiSASE operations team encounters the following situation: A company accepts any endpoint to a privileged portal despite a policy requirement to bind access to device identity and user authorization. Which sustained control would best prevent this same failure from recurring?
Explanation
Correct Answer
This guard addresses the recurring failure mode demonstrated by the case: Private access enforcement lacks the required device and user constraints. It guards the same affected workflow, rather than merely checking that some other service works. A successful controlled outcome would be: Only permitted users on compliant endpoints can complete a privileged sign-in.
Incorrect Answers
This control is relevant to another scenario in the stated requirement, specifically: A SaaS administrator sees that the application responds but cannot tell which access policy was applied to two user groups. It would not prevent the present mechanism: Private access enforcement lacks the required device and user constraints. Prevention must be linked to that actual failure mode rather than a generic adjacent control.
This control is relevant to another scenario in the stated requirement, specifically: A region's primary SASE security PoP suffers a service interruption and the monitoring team does not know whether clients are reconnecting elsewhere. It would not prevent the present mechanism: Private access enforcement lacks the required device and user constraints. Prevention must be linked to that actual failure mode rather than a generic adjacent control.
This control is relevant to another scenario in the stated requirement, specifically: An internal app uses long-lived HTTPS sessions, but users see sporadic failures after the SPA resource connector is updated and the team checks only DNS. It would not prevent the present mechanism: Private access enforcement lacks the required device and user constraints. Prevention must be linked to that actual failure mode rather than a generic adjacent control.