When using DNS filtering with logging, the username of the person making the DNS requests is stored in the duser= field in the log. This works great when the user is accessing the Fortigate DNS server through FortiClient SSL-VPN. However, it does not work for users that just send traffic through the firewall without using VPN. The duser= field is missing in that case.
For regular traffic, the duser= field gets populated from Active Directory integration, but for some reason this does not happen for DNS traffic directed at the Fortigate.
What is the best way to deal with DNS policy violations, when the Fortigate does not log who the user is? That makes it somewhat difficult to track down which users need to be educated. Is there a setting that I am missing?
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
@weggh
You may need to modify firewall policy that allows DNS traffic - Web traffic. In Source field, try to also add user-groups that will have access.
This way, in forward logs you will see IP and username that has tried to reach to some specific destinations.
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1547 | |
1031 | |
749 | |
443 | |
210 |
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.