The reason for the ping failures is due to the quick mode selectors restricting the subnet. Quick mode selectors define the IP ranges and protocols that are allowed through the VPN tunnel, and if they are not configured correctly, traffic to certain subnets can be blocked.
* Quick Mode Selectors:
* Quick mode selectors specify the source and destination subnets that are allowed to communicate through the VPN tunnel.
* If the selectors do not include the subnet of the webserver (192.168.10.0/24), then the traffic will be restricted, and the ping will fail.
* Diagnostic Output:
* The diagnostic output shows the VPN configuration details, but it is important to check the quick mode selectors to ensure that the necessary subnets are included.
* If the quick mode selectors are too restrictive, they will prevent traffic to and from the specified subnets.
* Configuration Check:
* Verify the quick mode selectors on both the FortiSASE and FortiGate hub to ensure they match and include the subnet of the webserver.
* Adjust the selectors to allow the necessary subnets for successful communication.
References:
* FortiOS 7.2 Administration Guide: Provides detailed information on configuring VPN tunnels and quick mode selectors.
* FortiSASE 23.2 Documentation: Explains how to set up and manage VPN tunnels, including the configuration of quick mode selectors.

The exhibit indicates that the URLhttps://www.bbc.com/is being blocked due to containing a banned word ("fight"). To allow access to this specific URL, you need to adjust the URL filter settings on FortiSASE.
* URL Filtering:
* URL filtering allows administrators to define policies that block or allow access to specific URLs or URL patterns.
* In this case, the URL filter is set to block any URL containing the word "fight."
* Modifying URL Filter:
* Navigate to the Web Filter configuration in FortiSASE.
* Locate the URL filter settings.
* Add an exception for the URLhttps://www.bbc.com/to allow access, even if it contains a banned word.
* Alternatively, remove or adjust the banned word list to exclude the word "fight" if it's not critical to the security policy.
References:
* FortiOS 7.2 Administration Guide: Provides details on configuring and managing URL filters.
* FortiSASE 23.2 Documentation: Explains how to set up and modify web filtering policies, including URL filters.

During FortiSASE provisioning, the FortiSASE administrator needs to configure at least one security point of presence (PoP). A single PoP is sufficient to get started with FortiSASE, providing the necessary security services and connectivity for users.
* Security Point of Presence (PoP):
* A PoP is a strategically located data center that provides security services such as secure web gateway, firewall, and VPN termination.
* Configuring at least one PoP ensures that users can connect to FortiSASE and benefit from its security features.
* Scalability:
* While only one PoP is required to start, additional PoPs can be added as needed to enhance redundancy, load balancing, and performance.
References:
* FortiOS 7.2 Administration Guide: Provides details on the provisioning process for FortiSASE.
* FortiSASE 23.2 Documentation: Explains the configuration and role of security PoPs in the FortiSASE architecture.

The Secure Internet Access (SIA) use case that minimizes individual workstation or device setup is SIA for agentless remote users. This use case does not require installing FortiClient on endpoints or configuring explicit web proxy settings on web browser-based endpoints, making it the simplest and most efficient deployment.
* SIA for Agentless Remote Users:
* Agentless deployment allows remote users to connect to the SIA service without needing to install any client software or configure browser settings.
* This approach reduces the setup and maintenance overhead for both users and administrators.
* Minimized Setup:
* Without the need for FortiClient installation or explicit proxy configuration, the deployment is straightforward and quick.
* Users can securely access the internet with minimal disruption and administrative effort.
References:
* FortiOS 7.2 Administration Guide: Details on different SIA deployment use cases and configurations.
* FortiSASE 23.2 Documentation: Explains how SIA for agentless remote users is implemented and the benefits it provides.

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.2 Administration Guide: Provides details on split tunneling configuration.
* FortiSASE 23.2 Documentation: Explains how to set up and manage split tunneling for specific destinations.