Created on
08-04-2024
03:41 PM
Edited on
11-30-2025
10:03 PM
By
Anthony_E
| Description | This article describes troubleshooting DLP issues. | ||||||||||
| Scope | FortiGate, FortiProxy. | ||||||||||
| Solution |
DLP (Data Leak Prevention) debug: FortiGate UTM inspects traffic in two modes: Proxy-based inspection and flow-based inspection.
Depending on the type of inspection configured, the daemons handling the DLP inspection will be different. The section below identifies the ways of fetching basic DLP debugs based on the inspection type. DLP in Proxy-based Mode: In Proxy mode, the proxy DLP and scanunit daemon will be involved in the DLP filtering. The intention in this example is to enable scanunit debug along with DLP because the scanunit daemon scans the traffic and passes the packets to the DLP daemon.
WAD debug logs can generate too much output and debug lines that might impact device performance. It is highly recommended to use as many filters as possible that can narrow down the generated logs by the WAD daemon.
To verify that the DLP fingerprint database is present on the FortiGate, use this command: 'diagnose test application dlpfingerprint 2'.
To restart this daemon, 'diagnose test application dlpfingerprint 99'.
Example usage is shown below :
diagnose debug disable diagnose sys scanunit debug dlp diagnose sys scanunit debug level verbose
To stop debugging:
diagnose debug disable
Note: Most of the times when firewall-policies mixes UTM-DLP & UTM-WF, the dlp feature did not take effect on sites that are exempt from inspection in URL-Filter: Difference between action 'Allow' and 'Exempt' in static URL filter |
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 2025 Fortinet, Inc. All Rights Reserved.