SonicWall Scrutinizer, in combination with SonicOS Enhanced 5.8 Flow Reporting (when using IPFIX with Extensions) can display reports based criteria such as users, IPS and App Control detections, Gateway Anti-Virus and Anti-Spyware detections, URLs, and more. This article describes ways to configure a report based on users, and customize that report to see the utilized applications, detected threats, accessed domains/URLs, etc.
There are multiple ways to view your reports. This method describes how to view the “SonicWall Users” report, and based on this report; select a user and view Applications/App Conversations, URLs/Domains, Conversations on Well Known Ports (Conversations WKP), and many more.
Filters can be applied manually as well; however that is not covered in this document.
Viewing the SonicWall Users Report



Viewing SonicWall URL Reports Based on SonicWall Users



Viewing Source & Destination Domain Reports Based on SonicWall Users
To view a less verbose report that reports on domains rather than URLs, go back to the SonicWall Users report (refer to: ‘Viewing the SonicWall Users Report’ at the beginning of this article), click on a user, and run the Destination Reports > Domains report. When the report opens, ensure that the Direction drop-down menu is set to Outbound. The example below is filtering specifically on the X1 WAN interface.

The screenshot above displays all domains visited in the Last Hour (the reporting period) by the “macuser” account. Some of these sites may be somewhat misleading. The best examples are right in the top 10. We’ll go over some of the potentially confusing ones below:


Customizing the Report Period
Report data can be further customized by using custom report periods, additional filters, or different time intervals. For example, the line graph is interactive, and allows you to drill down to a specific time period. If there’s a specific time period that you’re interested in drilling into, the time period can be highlighted for a closer look. In the screenshot below, I highlighted the spike from the above screenshot. The resulting report shows a closer look at the spike, using 1 minute intervals. In the example below, the user’s traffic spike spanned about 2 minutes, and peaked at the one minute mark. This may look like a large spike on first glance (especially compared to the rest of the hour that had practically no data), but in reality it was a very small bump that at its peak, hit a rate of about 23 to 24KB/s.
It is important to note that when drilling down to a specific period of time, the reporting period changes to “Custom”, and the period is displayed to the right, above the data table. Custom reporting periods are not dynamic. If the report is saved with the custom reporting period, the same period will be used whenever the saved report is opened. The default listed time periods are dynamic, so it is recommended that reports you wish to save and schedule emails for are saved using one of the provided reporting periods, instead of “Custom”.