Question 860
An operations group at a service-provider edge resolved: An administrator activates a branch-to-SASE tunnel but leaves a broad local firewall bypass permitting protected subnets to egress directly. Which ongoing safeguard should become part of its change process?
Explanation
Correct Answer
Review branch firewall and route bypass paths after integrating with FortiSASE. This control reduces recurrence of the documented mechanism: A surviving broad local allow can defeat intended cloud inspection routing. It creates a repeatable check around the needed response: Narrow the local direct-Internet exception and require approved source traffic to use the cloud-inspected route.
Incorrect Answers
Reconcile subnet inventory and permitted cloud-network policy after VLAN additions. That safeguard addresses another potential failure: A FortiGate connects to a FortiSASE PoP but its branch LAN subnet is missing from the cloud's permitted network or route configuration. It is not the most targeted recurring control for the described cause: A surviving broad local allow can defeat intended cloud inspection routing.
Validate cloud service egress and inspection logging during every branch integration. That safeguard addresses another potential failure: A branch sends protected Internet traffic directly to an ISP even though architecture requires FortiSASE cloud inspection for specified user subnets. It is not the most targeted recurring control for the described cause: A surviving broad local allow can defeat intended cloud inspection routing.
Test private-app reachability and group authorization independently of Internet browsing. That safeguard addresses another potential failure: A company assumes remote FortiClient users can reach branch-only internal apps through the same secure Internet profile without configuring supported private application connectivity. It is not the most targeted recurring control for the described cause: A surviving broad local allow can defeat intended cloud inspection routing.