Reporting Administration

Administrator Help | Forcepoint Web Security and Forcepoint URL Filtering | v8.5.x

Related topics:

Configuring how requests are logged

Assigning categories to risk classes

Configuring reporting preferences

Configuring Log Server

Log Database administration settings

Configuring investigative reports

Self-reporting

In organizations that use only the default administrator account (admin), everyone who uses the Forcepoint Security Manager has access to all reporting settings and tools. In organizations that use delegated administration, access to reporting settings and tools is controlled by members of the Super Administrator role (see Editing roles).

Administrators with access to reporting settings have many options for customizing reporting in their environment.

The Forcepoint URL Database organizes categories into risk classes. Risk classes suggest possible types or levels of vulnerability posed by sites in those categories. Use the Settings > General > Risk Classes page to customize risk classes for your organization. See Assigning categories to risk classes.

Use the Settings > Reporting > Preferences page to configure the email server used to distribute reports, activate self-reporting, and configure how long scheduled reports are stored on the management server. Also configure whether Real-Time Monitor collects data all the time, or only when Real-Time Monitor is open. See Configuring reporting preferences.

Logging is the process of storing information about Internet activity in a Log Database so that you can generate reports.

Use the Settings > General > Logging page to enable logging, select the categories to be logged, and determine what user information is logged. See Configuring how requests are logged for more information.

Use the Settings > Reporting > Log Server page to manage the way the log records are processed and connections to the Log Database. See Configuring Log Server.

Use the Settings > Reporting > Log Database page to administer the Log Database, including database partition, URL logging, browse time, and trend data options. See Log Database administration settings.

An end user who uses the Filtering Service has no direct or indirect influence over the database. Thus, although the log entry is stored in the MSSQL database, the user did not direct its storage and cannot retrieve it.

The only interface to the database itself is from the Log Server, the Reporting services, and the Manager. Filtering Service and Content Gateway do not access the database, but instead send information via the Log Server.