When configuring FortiSASE Secure Private Access (SPA) with SD-WAN integration, establishing a routing adjacency between FortiSASE and the FortiGate SD-WAN hub requires the use of the Border Gateway Protocol (BGP).
* BGP (Border Gateway Protocol):
* BGP is widely used for establishing routing adjacencies between different networks, particularly in SD-WAN environments.
* It provides scalability and flexibility in managing dynamic routing between FortiSASE and the FortiGate SD-WAN hub.
* Routing Adjacency:
* BGP enables the exchange of routing information between FortiSASE and the FortiGate SD- WAN hub.
* This ensures optimal routing paths and efficient traffic management across the hybrid network.
References:
FortiOS 7.6 Administration Guide: Provides information on configuring BGP for SD-WAN integration.
FortiSASE 23.2 Documentation: Details on setting up routing adjacencies using BGP for Secure Private Access with SD-WAN.

FortiSASE utilizes Security Assertion Markup Language (SAML) to provide a seamless Single Sign-On (SSO) experience for remote users connecting to the cloud infrastructure.
* Role Identification: In a SAML exchange, FortiSASE functions as the Service Provider (SP) . It relies on an external Identity Provider (IdP) -such as Microsoft Entra ID (formerly Azure AD), Okta, or FortiAuthenticator-to authenticate the user ' s identity and provide security assertions. 2
* SAML Group Matching: One of the core features of the FortiSASE SAML implementation is the ability to perform group matching . During the authentication process, the IdP sends a SAML assertion that typically includes an " Attribute Statement " containing the user ' s group memberships. 3 FortiSASE captures this attribute and matches it against locally defined SAML user groups.
* Policy Enforcement: This group matching capability is critical because it allows administrators to apply different Security Internet Access (SIA) or Secure Private Access (SPA) policies based on the user ' s role (e.g., " Marketing " vs. " Finance " ) rather than managing individual users manually.
* Analysis of Incorrect Options: * Options C and D are incorrect because FortiSASE does not natively act as a SAML IdP; it is designed to consume assertions from professional identity management platforms.
* Option B is incorrect because FortiSASE fully supports and relies upon group matching for enterprise-scale policy management.

Deploying FortiAP enables secure internet access for unmanaged personal devices in small branch offices with minimal configuration by automatically directing traffic through FortiSASE, eliminating the need for endpoint installation or complex setup.

To enforce device posture checks and ensure that TCP traffic flows through FortiGate, the FortiGate must act as a ZTNA access proxy and host the ZTNA servers and policies. This setup allows posture validation via FortiSASE while routing traffic securely to protected servers through FortiGate.