The end user must enter their credential to register FortiClient With FortiSASE. Enabling this feature provides an additional layer of security during FortiClient Registration.

In FortiSASE, dedicated IP addresses are used to assign unique IPs to remote users, enabling precise traffic control, auditing, and user identification. They also support traffic isolation for enhanced security and policy enforcement.

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.6 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.

In FortiSASE, Zero Trust Network Access (ZTNA) tags-also known as security posture tags-are used to dynamically grant or deny access based on the real-time security state of an endpoint. This mechanism ensures that only devices meeting specific compliance requirements can access protected resources or the internet.
* Endpoint Analysis: The Managed Endpoints exhibit shows that while Jumpbox only has the FortiSASE-Compliant tag, the Windows-AD endpoint has been assigned both FortiSASE-Compliant and FortiSASE-Non-Compliant tags. This indicates that a security posture check on the Windows-AD device has failed, triggering a rule that applies the non-compliant tag.
* Policy Evaluation: The Secure Internet Access Policy table shows two custom policies. The first policy, named Non-compliant , uses the FortiSASE-Non-Compliant tag as its source and has the action set to Deny . The second policy, Web Traffic , allows access for FortiSASE-Compliant users.
* Root Cause of Outage: Because FortiSASE (powered by FortiOS) processes security policies in a top- down sequence, the " Non-compliant " policy is evaluated first. Since Windows-AD matches the source criteria for this " Deny " policy, its traffic is blocked before it can reach the " Accept " policy.
Although the exhibit shows a warning icon for the FortiClient version on Windows-AD, the direct cause of the internet outage is the explicit Deny policy triggered by the change in the device ' s security posture (the application of the Non-Compliant tag).