A FortiGate administrator is using the built-in FortiGuard web filter to block malicious websites. Users report that they can still access a site that is categorized as 'Malware' by FortiGuard. The administrator verifies that the web filter profile is applied to the policy and that the category is set to block. What is the most likely reason for this issue?
Without SSL inspection, FortiGate cannot see the full URL or the server certificate details for HTTPS traffic, so it cannot apply web filtering based on the category of the site. The web filter may see only the IP address or SNI, which might not be categorized. Enabling SSL inspection allows FortiGate to decrypt and inspect the traffic, enforcing the web filter. This is the most common reason for web filter bypass on HTTPS sites.
Why this answer
The most likely reason is that the site uses HTTPS and SSL inspection is not enabled. FortiGate cannot inspect the encrypted traffic to determine the URL category, so the web filter cannot block it. Enabling SSL inspection allows FortiGate to decrypt and apply the web filter.
Other options like cache, monitor mode, or FortiGuard reachability are less likely given the scenario details. Thus, SSL inspection is the key.