Question 280
A Fortinet SD-WAN/FortiSASE operations team encounters the following situation: An organization wants a private application reachable only to its employees, yet the proposed architecture publishes the application as an ordinary unrestricted internet service. 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: The proposal conflates private application reachability with public internet exposure. It guards the same affected workflow, rather than merely checking that some other service works. A successful controlled outcome would be: Only entitled users reach the private application while internet scans cannot access an unprotected origin.
Incorrect Answers
This control is relevant to another scenario in the stated requirement, specifically: A procurement team licenses only part of the planned remote-user population, yet the design assumes all seasonal workers receive the same protected access. It would not prevent the present mechanism: The proposal conflates private application reachability with public internet exposure. 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 healthcare supplier sends regional employee traffic to a distant PoP despite a contractual requirement to keep security inspection within an approved geography. It would not prevent the present mechanism: The proposal conflates private application reachability with public internet exposure. 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 rural field station has only an edge router and must secure all site traffic; the proposed rollout installs per-user endpoint agents on devices it does not control. It would not prevent the present mechanism: The proposal conflates private application reachability with public internet exposure. Prevention must be linked to that actual failure mode rather than a generic adjacent control.