Content Filtering Events and Logs Overview
Use this page to view information about security events based on Content filtering policies. The event viewer provides a view of all content filtering events and how the events are handled by content filter. This page can be used to view traffic on the network in real time or as a debugging tool to view how content filtering is operating.
Content filtering provides basic data loss prevention functionality. Content filtering screens traffic based on MIME type, file extension, protocol commands, and embedded object type. It either permits or blocks specific commands or extensions on a protocol-by-protocol basis.
Using the time-frame slider, you can quickly focus on the area of activity that you are most interested in. Once the time range is selected, all of the data presented in your view is refreshed automatically. You can also use the Custom button to set a custom time range.
There are two ways to view your data. You can select either the summary view or the detail view.
Content Filtering Events—Summary View
Click Summary View for a brief summary of all the content filtering events in your network. The top of the page has a swim lane graph of all the content filtering events against the blocked events. You can use the widgets at the bottom of the page to view critical information such as top blocked protocol commands, top reasons, and top sources. See Table 1 for descriptions of the widgets in this view.
Table 1: Widgets in Summary View
Top Blocked Protocol commands
Top command names or file extensions blocked on a protocol‐byprotocol basis.
Top reasons for blocking the content. For example: Inappropriate or harmful communication.
Top source IP addresses of the network traffic; sorted by event count.
Content Filtering Events—Detail View
Click Detail View for comprehensive details of events in a tabular format that includes sortable columns. You can aggregate the events using the Group by option. For example, you can group the events based on source country. The table includes information such as the event name, UTM category, source IP address, source country, and so on.
The Legacy Node option is displayed in the event viewer after the legacy log collector node is added on the Logging Nodes page. We’ve added the legacy log collector support only for read only purpose to view existing log collector data. New logs should point to Security Director Insights VM as the log collector. Select the Legacy Node checkbox to view the existing log collector data. When you clear the Legacy Node checkbox, Security Director Insights log collector data is displayed.
See Table 2 for descriptions of columns in this view.
Table 2: Columns in Detail View
Time when the event occurred.
Event name of the log.
Source country name from where the event originated.
Source IP address from where the event occurred (IPv4 or IPv6).
Description of the log.
UTM Category or Virus Name
UTM category of the log: enhanced, local, and redirect.
Accessed URL name that triggered the event.
Type of traffic. For example, ftp and http.
Action taken for the event: warning, allow, and block.
IP address of the log source (IPv4 or IPv6).
Hostname in the log.
User traffic received from the zone.
Role names associated with the event.
Reason for the log generation. For example, unrestricted access.
Name of the content filtering profile that triggered the event.