Created on 11-16-2023 03:24 AM Edited on 11-16-2023 03:25 AM By Jean-Philippe_P
Description | This article describes one of the causes why FortiGate is not inspecting Web traffic (Web Filter) and why no web filter logs are generated. This issue is encountered on firewall policy and web filter profile with Proxy inspection mode. |
Scope | FortiGate. |
Solution |
On this deployment, firewall policy and web filter are configured with the following parameters.
However, users are still able to access Social Networking sites. In addition, the debug flow shows that FortiGate is not sending the traffic to the Application Layer for further checking/inspection.
id=65308 trace_id=1061 func=fw_forward_handler line=1009 msg="Allowed by Policy-1: SNAT"
Checking the Forward Traffic logs shows that traffic to Facebook (or blocked URL) is allowed. There are no Web Filter logs shown.
Solution: One of the possible reasons for this behavior is the misconfigured Protocol-Options. Protocol-Options is used by Proxy Inspection mode to determine the protocol to inspect.
Upon enabling the HTTP on Protocol-Options, web filtering works as expected.
id=65308 trace_id=1735 func=fw_forward_handler line=1009 msg="Allowed by Policy-1: AV SNAT"
|
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.