Zero-trust tags are critical in implementing zero-trust network access (ZTNA) policies. Here are the two key advantages of using zero-trust tags:
* Access Control (Allow or Deny):
* Zero-trust tags can be used to define policies that either allow or deny access to specific network resources based on the tag associated with the user or device.
* This granular control ensures that only authorized users or devices with the appropriate tags can access sensitive resources, thereby enhancing security.
* Determining Security Posture:
* Zero-trust tags can be utilized to assess and determine the security posture of an endpoint.
* Based on the assigned tags, FortiSASE can evaluate the device's compliance with security policies, such as antivirus status, patch levels, and configuration settings.
* Devices that do not meet the required security posture can be restricted from accessing the network or given limited access.
References:
FortiOS 7.6 Administration Guide: Provides detailed information on configuring and using zero-trust tags for access control and security posture assessment.
FortiSASE 23.2 Documentation: Explains how zero-trust tags are implemented and used within the FortiSASE environment for enhancing security and compliance.

Zero Trust Network Access (ZTNA) private access provides the most efficient and secure method for remote users to access a TCP-based application hosted on a private web server. ZTNA ensures that only authenticated and authorized users can access specific applications based on predefined policies, enhancing security and access control.
* Zero Trust Network Access (ZTNA):
* ZTNA operates on the principle of " never trust, always verify, " continuously verifying user identity and device security posture before granting access.
* It provides secure and granular access to specific applications, ensuring that remote users can securely access the TCP-based application hosted on the private web server.
* Secure and Efficient Access:
* ZTNA private access allows remote users to connect directly to the application without needing a full VPN tunnel, reducing latency and improving performance.
* It ensures that only authorized users can access the application, providing robust security controls.
References:
FortiOS 7.6 Administration Guide: Provides detailed information on ZTNA and its deployment use cases.
FortiSASE 23.2 Documentation: Explains how ZTNA can be used to provide secure access to private applications for remote users.

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

The FortiSASE On/off-net detection feature is a two-part configuration designed to optimize bandwidth and user experience by determining when a device is in a trusted environment.
* Rule Set Definition: The first part involves defining what constitutes an " on-net " or " on-fabric " status. In this scenario, the customer successfully configured a rule set named CERT-PUBLIC-IP using the Connects with a known public IP detection type. This tells FortiSASE that if the endpoint's public WAN IP matches the corporate gateway, it is considered to be on the corporate network.
* Profile Exemption Logic: Defining the rule set is not enough to stop the VPN connection. Within the Endpoint Profile (under the Connection tab > On/off-net Settings), there is a specific toggle labeled Exempt endpoint from FortiSASE auto-connect when endpoint is on-net (or in some versions, Bypass FortiSASE when endpoint is on-net ).
* Exhibit Analysis: Looking at the provided exhibit (image_57097d.jpg), the " Exempt endpoint from FortiSASE auto-connect... " toggle is clearly disabled (switched to the left).
* Root Cause: Because this toggle is disabled, FortiClient identifies that it is " on-net " based on the IP rule, but it has no instruction to skip the VPN connection. Consequently, the " Automatically " initiate tunnel setting remains the dominant instruction, causing the VPN to connect regardless of the network location.
To resolve the issue, the administrator must enable the Exempt endpoint from FortiSASE auto-connect when endpoint is on-net option in the SASECert01 profile.

FortiSASE Geofencing and Regional Compliance allow administrators to control where remote users connect based on their physical location, which is determined by the endpoint's public IP address.3
* Default Connection Behavior: By default, FortiSASE uses a "best-effort" geolocation logic to ensure the lowest latency for the user. If an administrator has not configured a specific regional compliance rule for a user's country or region, FortiClient will automatically attempt to connect to the closest available FortiSASE security PoP (Point of Presence) based on proximity.4
* Regional Compliance Rules: When an organization must enforce data residency or specific security routing requirements, they create Regional Compliance rules. According to the FortiSASE 25 Feature Administration Guide, these rules allow the administrator to override the default "closest PoP" behavior for specific countries.
* Connectivity Options: Within a regional compliance rule, the administrator must specify the destination for the traffic. The system provides a choice between two distinct connection types: a FortiSASE Security PoP or an On-premises device (such as a FortiGate acting as a gateway).5 The documentation specifies that a rule is designed to point to one of these types at a time to satisfy the compliance requirement for that specific region.
* Connection Priority: While multiple connections can be managed in a priority table, the logic for Regional Compliance is focused on directing the user to the designated compliant entry point. Option D is incorrect because the connection order is determined by the Priority and custom fail-over connections table; an administrator can manually adjust the sequence, so it is not "always" the security PoP first.