Database activity monitoring (DAM) : Target monitoring configuration tabs and options
 
Target monitoring configuration tabs and options
The monitoring configuration for a target database is displayed when you click the target’s name on the Monitoring Management page.
Table 8: Monitoring configuration page tabs and options
Tabs
Purposes
General
Settings of audit configuration for each target database. You can start and stop monitoring and auditing in this page. It also shows monitoring and auditing status. See “Configuring target database monitoring”.
Alert Policies
Shows the available alert policies with information, such as policy type, status, name, and severity. You can create Data policies from this page, and enable/disable policies for the target. See “Adding alert and audit policies to monitoring”.
Alert Policy Groups
Associate the alert policy group to your target database. See “Adding policy groups to target monitoring”.
Audit Policies
Shows the available audit policies with information. You can create Data policies, or enable/disable policies from this page. See “Adding alert and audit policies to monitoring”.
Note: This tab is only available for collection method "TCP/IP Sniffer" for Oracle, Microsoft SQL Server, Sybase and DB2.
Audit Policy Groups
Associate the audit policy group to your target database. See “Adding policy groups to target monitoring”.
Note: This tab will be only available for collection method "TCP/IP Sniffer" for Oracle, Microsoft SQL Server, Sybase and DB2.
Query Schedule
Specifies a schedule for any database query policies, which are alert policies that query the target database with SQL and save the result as an alert. See “Configuring a database query policy”.
Alert Notification
Configure Alert Notification for monitoring. See “Sending alert notifications”.
Real Time Blocking
Enables or disables real-time blocking for monitoring configurations that use the TCP/IP sniffer, and configures blocking settings. See “Blocking invalid access while monitoring”.
Audit Management
For Oracle, this page shows the issued audit command and all audit commands for each object. For Microsoft SQL Server, this page shows audited events and audited filters used by FortiDB This page is not applicable for Sybase. See “Displaying the history of issued audit commands”.
Note: This tab will be only available for collection method "DB, EXTENDED" or "XML File Agent" for Oracle, "SQL Trace" for Microsoft SQL Server, or "DB2 Agent" for DB2.
White List
In the White List tab, you can configure data policies, which will be automatically excluded from the Alert Policy settings for Oracle or Microsoft SQL Server Server. See “Excluding policies from the Alert Policy settings (whitelist)”.
Note: This tab will be only available for collection method "DB, EXTENDED" for Oracle,"SQL Trace" for Microsoft SQL Server.After Monitor started, the SQL action matching with the white list settings, fortidb will not generante alerts for it. The SQL action matching the white list settings should be known secure action.
See also
Configuring target database monitoring