When remote users connected to FortiSASE require access to internal resources on Branch-2, the following process occurs:
* SD-WAN Capability:
* FortiSASE leverages SD-WAN to optimize traffic routing based on performance metrics and priorities.
* In the priority settings, HUB-1 is configured with the highest priority (P1), whereas HUB-2 has a lower priority (P2).
* Traffic Routing Decision:
* FortiSASE evaluates the available hubs (HUB-1 and HUB-2) and selects HUB-1 due to its highest priority setting.
* Once the traffic reaches HUB-1, it is then routed to the appropriate branch based on internal routing policies.
* Branch-2 Access:
* Since HUB-1 has the highest priority, FortiSASE directs the traffic to HUB-1.
* HUB-1 then routes the traffic to Branch-2, providing the remote users access to the internal resources.
References:
FortiOS 7.6 Administration Guide: Details on SD-WAN configurations and priority settings.
FortiSASE 23.2 Documentation: Explains how FortiSASE integrates with SD-WAN to route traffic based on defined priorities and performance metrics.

Onboarding a Secure Web Gateway (SWG) endpoint involves several components to ensure secure and effective integration with FortiSASE. Two key components are the FortiSASE CA certificate and the proxy auto-configuration (PAC) file.
* FortiSASE CA Certificate:
* The FortiSASE CA certificate is essential for establishing trust between the endpoint and the FortiSASE infrastructure.
* It ensures that the endpoint can securely communicate with FortiSASE services and inspect SSL
/TLS traffic.
* Proxy Auto-Configuration (PAC) File:
* The PAC file is used to configure the endpoint to direct web traffic through the FortiSASE proxy.
* It provides instructions on how to route traffic, ensuring that all web requests are properly inspected and filtered by FortiSASE.
References:
FortiOS 7.6 Administration Guide: Details on onboarding endpoints and configuring SWG.
FortiSASE 23.2 Documentation: Explains the components required for integrating endpoints with FortiSASE and the process for deploying the CA certificate and PAC file.

In the Fortinet SASE architecture, Zero Trust Network Access (ZTNA) tags (which have been renamed to Security Posture Tags starting with FortiClient/EMS 7.4.0) play a critical role in continuous posture assessment. These tags are dynamic metadata assign 8 ed to an endpoint based on specific conditions or " tagging rules " defined in the FortiSASE Endpoint Management Service (EMS).
* Posture Determination: The FortiClient agent, installed on the endpoint, monitors the device for various security attributes-such as whether an antivirus is running, the presence of specific registry keys, OS version, or the absence of critical vulnerabilities.
* SIA (Secure Internet Access) Use Case: In SIA scenarios, FortiSASE uses these tags within security policies to control internet access. For example, a policy may allow full internet access only to endpoints tagged as " Compliant " while redirecting " Non-Compliant " devices to a restricted remediation portal.
* SPA (Secure Private Access) Use Case: In SPA (specifically ZTNA Proxy mode), the tags are synchronized from FortiSASE to the corporate FortiGate (acting as the ZTNA Access Proxy). 12 When a user attempts to access a private application, the FortiGate checks the endpoint ' s client certificate and its synchronized ZTNA tags. 13 If the endpoint does not meet the required posture (e.g., it is missing a required " Domain-Joined " tag), access is denied at the session level.
According to the FortiSASE 25 Enterprise Administrator Study Guide , ZTNA tags are fundamental to the
" Zero Trust " principle because they move beyond static identity (username/password) to verify the real-time security state of the device before granting access to either the internet or internal private resources.

To meet the requirement of inspecting all endpoint internet traffic on FortiSASE while excluding Google Maps traffic from the FortiSASE VPN tunnel and redirecting it to the endpoint's physical interface, you should configure split tunneling. Split tunneling allows specific traffic to bypass the VPN tunnel and be routed directly through the endpoint's local interface.
* Split Tunneling Configuration:
* Split tunneling enables selective traffic to be routed outside the VPN tunnel.
* By configuring the Google Maps Fully Qualified Domain Name (FQDN) as a split tunneling destination, you ensure that traffic to Google Maps bypasses the VPN tunnel and uses the endpoint's local interface instead.
* Implementation Steps:
* Access the FortiSASE endpoint profile configuration.
* Add the Google Maps FQDN to the split tunneling destinations list.
* This configuration directs traffic intended for Google Maps to bypass the VPN tunnel and be routed directly through the endpoint's physical network interface.
References:
FortiOS 7.6 Administration Guide: Provides details on split tunneling configuration.
FortiSASE 23.2 Documentation: Explains how to set up and manage split tunneling for specific destinations.

When central management is enabled, security profile group objects are managed exclusively through FortiManager, making them read-only on the FortiSASE portal to ensure centralized policy control.