Technical Tip: How to bypass local application using a split tunnel in FortiSASE

[RBA]

Description	This article describes how to configure a split tunnel to bypass FortiSASE using the local application and verify in endpoint.
Scope	FortiSASE, FortiClient.
Solution	Local application that has to be bypassed can be specified by their name, full path, or the directory where it is installed. Environment variables (e.g. %programfiles%, %appdata% ) can be used in file and directory paths. For the illustration, 'QuickAssist.exe' is bypassed. Note that it is not specific to quick assist (has dependency on other apps) and can be followed for any local applications. File path can be identified by opening Task Manager and clicking on Open File Location. Copy the path. Navigate to Configuration -> Profiles -> Select and edit the profile. Under 'FortiSASE bandwidth optimization' -> Split tunneling destinations, select Create. Select Local Application and under Match add the path: C:\Program Files (x86)\Microsoft\EdgeWebView\Application\129.0.2792.52\C:\Program Files\WindowsApps\MicrosoftCorporationII.QuickAssist_2.0.32.0_x64__8wekyb3d8bbwe\Microsoft.RemoteAssistance.QuickAssist\QuickAssist.exe Required FQDN can be added. 'remoteassistanceprodacs.communication.azure.com' and 'remoteassistance.support.services.microsoft.com' were added in this scenario. Wait for the SYNC to complete in FortiClient. To verify on endpoint Run netstat -naob from the command line. The output would show the interface from which connection is established/listening. In this case it was taking a physical gateway. Confirm the config is updated in the registry for FortiClient (Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Fortinet\FortiClient\Sslvpn\Tunnels\Secure Internet Access\Traffic Control\apps).