Question 230
At Aster Media, an infrastructure review by the cross-region WAN engineers is evaluating content workflow access across a global publishing enterprise during a secured remote-work pilot (FT-D-10-03). The review finds that a broad endpoint bypass list sends a sensitive SaaS application outside the FortiSASE inspection path. Any correction must respect this operating requirement: licensed content remains limited to authorized business units. Which ongoing control most directly reduces the chance of this issue returning?
Explanation
Correct Answer
This preventive control directly targets recurrence: Review bypass list reachability against asset and application inventory; make it a repeatable part of Aster Media's change assurance (FT-D-10-03). It sustains the corrective action, replace broad bypass entries with the smallest approved destination exceptions, and must preserve the requirement that licensed content remains limited to authorized business units.
Incorrect Answers
The source case reports that a broad endpoint bypass list sends a sensitive SaaS application outside the FortiSASE inspection path. The alternative is a useful recurring check for: Exercise office-to-home transitions after profile changes; schedule a recorded review after topology changes. The present failure instead depends on: Review bypass list reachability against asset and application inventory; schedule a recorded review after topology changes. The targeted safeguard is “Review bypass list reachability against asset and application inventory; schedule a recorded review after topology changes”.
The source case reports that a broad endpoint bypass list sends a sensitive SaaS application outside the FortiSASE inspection path. “Audit profile assignment after identity-group changes; schedule a recorded review after topology changes” maintains another technical control: Audit profile assignment after identity-group changes; schedule a recorded review after topology changes. It does not directly prevent this case’s specific recurrence, for which “Review bypass list reachability against asset and application inventory; schedule a recorded review after topology changes” addresses: Review bypass list reachability against asset and application inventory; schedule a recorded review after topology changes.
The source case reports that a broad endpoint bypass list sends a sensitive SaaS application outside the FortiSASE inspection path. The alternative is a useful recurring check for: Recheck private profile coverage after adding a hub or private app; include a negative-authorization regression case. The present failure instead depends on: Review bypass list reachability against asset and application inventory; schedule a recorded review after topology changes. The targeted safeguard is “Review bypass list reachability against asset and application inventory; schedule a recorded review after topology changes”.