Application-aware traffic steering selects appropriate paths according to intended access: internet/SaaS sessions exit directly at the branch, while protected corporate destinations traverse a secure tunnel to the central gateway or VPNC. Define the traffic identification, routing policy and NAT behavior so enterprise prefixes are not accidentally leaked onto the public internet. Validate DNS steering and failover when the primary tunnel becomes unavailable. Full tunneling adds needless SaaS backhaul, while bridging everything removes the central enterprise inspection and reachability requested. For a SaaS call, local breakout avoids an unnecessary detour through the data center, while a private ERP connection remains tunneled. Validate DNS steering and how the return traffic selects its route.
A full tunnel hairpins SaaS traffic to the corporate gateway; pure bridging loses the desired corporate tunnel path. Application-aware split tunneling distinguishes the two destinations. VPN reachability, DNS behavior, and return routes must support both paths.
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit