FortiSASE is designed around three core secure access use cases:
Secure Internet Access (SIA)
Protects users when accessing the public internet using SWG, FWaaS, DNS security, and threat protection.
Secure SaaS Access (SSA)
Secures access to cloud/SaaS applications with visibility, control, and data protection.
Secure Private Access (SPA)
Provides zero-trust access (ZTNA) to private applications without traditional VPN exposure.

Steering bypass destinations support four destination types: Infrastructure, FQDN, Local Application, and Subnet.
The Apply condition determines whether the bypass applies to On-net, Off-net, or both endpoint states.

FortiSASE is designed to resolve key work-from-anywhere challenges such as lack of visibility and control, inconsistent security across users and locations, and performance issues caused by inefficient traffic paths.

The on/off-net rule setting in FortiSASE classifies endpoints as on-net (inside trusted corporate networks, like branch offices) or off-net (remote or untrusted locations, like home or public Wi-Fi).
Administrators define on-net rules using IP subnets, gateway MACs, or other criteria to trigger behaviors such as exempting on-net endpoints from FortiSASE auto-connect or applying different profiles.

On FortiGate, a policy route (PBR) with action deny does not drop the traffic outright. Instead, it prevents the traffic from being steered by that policy route, and the packet is then handed back to the regular routing lookup (FIB):
Source 10.0.1.130 matches 10.0.1.128/25
Destination 128.66.0.125 matches 128.66.0.0/24
Router policy says action deny → do not use this policy route
Result: FortiGate falls back to the FIB (normal routing table).