Fortinet FortiDB User manual

www.fortinet.com
FortiDB
Version 3.2
Utilities User Guide

FortiDB Utilities User Guide
Version 3.2
December 19, 2008
15-32000-81369-20081219
© Copyright 2008 Fortinet, Inc. All rights reserved. No part of this publication including text, examples,
diagrams or illustrations may be reproduced, transmitted, or translated in any form or by any means,
electronic, mechanical, manual, optical or otherwise, for any purpose, without prior written permission of
Fortinet, Inc.
Trademarks
ABACAS, APSecure, FortiASIC, FortiBIOS, FortiBridge, FortiClient, FortiDB, FortiGate, FortiGuard,
FortiGuard-Antispam, FortiGuard-Antivirus, FortiGuard-Intrusion, FortiGuard-Web, FortiLog,
FortiManager, Fortinet, FortiOS, FortiPartner, FortiProtect, FortiReporter, FortiResponse, FortiShield,
FortiVoIP, and FortiWiFi are trademarks of Fortinet, Inc. in the United States and/or other countries. The
names of actual companies and products mentioned herein may be the trademarks of their respective
owners

Table of Contents
FortiDB Version 3.2 Utilities User Guide
15-32000-81369-20081219 1
Table of Contents
FortiDB MA Utilities ................................................................................................. 3
Auto Discovery......................................................................................................... 4
DB2 .....................................................................................................................................6
MS-SQL ..............................................................................................................................6
Connection Summary .............................................................................................. 8
Rule Chaining ........................................................................................................... 9
Chaining with Parameterized User-Defined Rules............................................................11
General PUDR Steps...................................................................................................12
PUDR Process.............................................................................................................12
PUDR Eligible Rules....................................................................................................13
Chaining the UBM Policy and PUDR Together ...........................................................14
Alert Behavior ..............................................................................................................17
PUDR Alert Behavior with Multiple SELECT-List Objects
in the Violating SQL Statement...................................................................................18
Report Manager...................................................................................................... 20
Alert Report Manager........................................................................................................20
Setting a Report Schedule...........................................................................................20
Reporting by Time .......................................................................................................23
Enabling Email Recipients ...........................................................................................23
Specifying Report Parameters.....................................................................................23
Activating ARM ............................................................................................................27
Running and Analyzing Reports ..................................................................................27
Custom Reports ................................................................................................................30
Using This Feature ......................................................................................................30
Scheduling ...................................................................................................................30
Customer and Company Information...........................................................................32
Report and Template Generation and Management ...................................................33
Report History..............................................................................................................39
Licensing and Administration ............................................................................................40
Custom Report Properties ...........................................................................................40
SOX Compliance Reports.................................................................................................42
Reports and Acronyms ...............................................................................................43
Common Report Header Fields ...................................................................................43
SOX Report Specifics ........................................................................................... 44
History of Privilege Changes Report (HPC)......................................................................44
COBIT Objectives and Setup Requirements ..............................................................44

FortiDB Version 3.2 Utilities User Guide
215-32000-81369-20081219
Table of Contents
Report Body Columns .................................................................................................44
Abnormal or Unauthorized Changes to Data Report (AUC) .............................................45
COBIT Objectives and Setup Requirements ..............................................................45
Report Body Columns .................................................................................................45
Abnormal Use of Service Accounts Report (AUS) ...........................................................46
COBIT Objectives and Setup Requirements ..............................................................46
Report Body Columns .................................................................................................46
Abnormal Termination of Database Activity Report (ATD) ...............................................47
COBIT Objectives and Setup Requirements ..............................................................47
Report Body Columns .................................................................................................47
End of Period Adjustments Report (EPA) ........................................................................48
COBIT Objectives and Setup Requirements ..............................................................48
Report Body Columns .................................................................................................48
Determining Your Reporting Period.............................................................................49
Verification of Audit Settings Report (VAS) ......................................................................50
COBIT Objectives and Setup Requirements ..............................................................50
Report Body Columns .................................................................................................50
Licensing and Administration.......................................................................................51
Index ........................................................................................................................ 53

FortiDB MA Utilities
FortiDB Version 3.2 Utilities User Guide
15-32000-81369-20081219 3
FortiDB MA Utilities
FortiDB MA provides several utilities to help you use other modules:
•Auto Discovery to ease the burden of manually setting up database
connections
•Connection Summary to show which database connections are Open or are
Open and Running
•Rule Chaining to trigger one rule based upon another
•Report Manager for custom, offline reports

FortiDB Version 3.2 Utilities User Guide
415-32000-81369-20081219
Auto Discovery
Auto Discovery
FortiDB MA provides the ability to search for, and establish connections to,
databases on your network. Rather than manually entering all of the connection
information, you can have FortiDB MA automatically discover it for you.
Selecting Addresses for Auto-Discovery
In order to use this feature:
1Select the Database->New menu, and click the Auto Discovery button on the
Create New Database Connection screen. Or you can just select Auto Discovery
from the Main page.
2Enter an IP address range and specify the RDBMS type you are interested in.
3By clicking the Edit button next to the desired type of database, you can enter a
range of ports, in case there are databases listening on non-default ports.
4Click Close to close the Edit Port Range screen.

Auto Discovery
FortiDB Version 3.2 Utilities User Guide
15-32000-81369-20081219 5
Selecting Non-Standard Ports for Auto-Discovery
5Click the Begin Discovery button.
Results from Auto-Discovery

FortiDB Version 3.2 Utilities User Guide
615-32000-81369-20081219
DB2 Auto Discovery
Discovered Database Information Populating Connection Form
The process will automatically return:
• Database Type and version
• IP address (with port if applicable)
• Database name/instance
Once the Auto Discovery list is returned, you can create, by clicking the Add
button on the Discovered Database Applications screen, the database
connections you wish to assess or monitor.
The additional required and recommended fields will need to be completed
manually. (See the FortiDB MA Administration Guide for more information on
setting up connections)
DB2
Auto Discovery does not return the database name and version for DB2 UDB with
V8 Fix Pack 10.
MS-SQL
It is sometimes necessary to temporarily open another port in your firewall to
make sure the Auto Discovery program communicates with all SQL Server
versions. You should configure the firewall on your target machine so that it allows
UDP packets:

Auto Discovery MS-SQL
FortiDB Version 3.2 Utilities User Guide
15-32000-81369-20081219 7
• Destined for port 1434
• Originating from the port whose number is specified in the dss.udpport
property in dssConfig.properties.
Note: FortiDB MA sends a packet to port 1434, which MSSQL uses in order to
return information about itself such as instance name, version, etc. (Even though
this is an MSSQL-specific port number, FortiDB MA uses it for all Auto-Discovery-
related transmissions.)

FortiDB Version 3.2 Utilities User Guide
815-32000-81369-20081219
MS-SQL Connection Summary
Connection Summary
The Connection Summary utility allows you to see, by FortiDB MA module and in
one place, a dashboard view of all of your database connections.
Connection Summary Button
Connection Summary Output

Rule Chaining MS-SQL
FortiDB Version 3.2 Utilities User Guide
15-32000-81369-20081219 9
Rule Chaining
The Rule Chaining module allows you to associate rules so that one, the source1
rule, can influence the execution of another, the target2rule. Both rules are
established with the same target database.
Rule Chaining Setting Screen
FortiDB MA offers two types of chained-rule pairs:
• Rule pairs in which there are no parameters passed. (In this case, you may
use Guarded Items from Privilege Monitor (PM), Metadata monitor (MM),
Content Monitor (CM), and User Behavior Monitor (UBM))
• Rule pairs in which there are parameters passed(In this case, you may use
Guarded Items only from User Behavior Monitor (UBM))
You invoke Rule Chaining from the tree navigator on the left.
1. This is sometimes called the original rule.
2. This is sometimes called the chained rule.

FortiDB Version 3.2 Utilities User Guide
10 15-32000-81369-20081219
MS-SQL Rule Chaining
Configuring a Rule Chain for a Specific Target Database Connection
You can perform the following:
• Choose the target database (the database you want to run the rules against)
• Add item (new chain)
• Delete item
• View/Modify item (make changes to an existing chain)
• Enable item (a chain does not have to be enabled when it is created)
• Disable item
Rule Chaining Setting Screen

Rule Chaining Chaining with Parameterized User-Defined Rules
FortiDB Version 3.2 Utilities User Guide
15-32000-81369-20081219 11
After the database has been specified and you have clicked on [Add Item], you
will be presented with the Create Rule Chaining Settings page.
Here, you need to:
• Name the Rule Chain
• Select the policy you want to use as the Source Rule
• Select the target rule (Chained Rule) you want to execute, once the first rule
had been violated.
• Specify whether you want the chain to run immediately upon source-rule
violation or not. Run Immediately means that the target rule will run as soon
as there is a source-rule violation. Run as Scheduled means that the target
rule will run according to the module-, database-, or item-specific schedule that
is in effect for the source rule.
• Decide whether you want to immediat1ely enable the chain or not. Unless you
check the Enable Chain? checkbox, the chain won't be in effect. This allows
you to create the chain and then only use it when needed.
You can see the Module and the name of the available guarded items for all
policies. For example, 'PM|' or 'UBM|' preceding the rule name indicates the PM,
or UBM module, respectively.
After the Rule Chain is invoked, alerts will appear with those of other policies.
Chaining with Parameterized User-Defined Rules
Parameters, specific to the RDBMS type of your target database, can be passed
from the source to the target in order to permit the target to perform specific tasks,
such as to kill the session of a suspicious user.
The source rule can be a UBM User, Object, or Session Policy. The target rule can
only be a User-Defined Rule (UDR) and specifically one that can accept
parameters: a Parameterized User Defined Rule (PUDR). The PUDR functionality
can be accessed within the UBM module. (See the FortiDB MA User Behavior
Monitor (UBM) User Guide)
When there is a violation of the source rule, the target UDR gets executed, with
the parameters passed from the source rule. An alert is generated both for the
source violation and for the PUDR execution.
1. A module schedule will be overridden by a database-specific schedule, if one is set. A
database-specific schedule will be overridden by an item-specific schedule if one is set.
Note: For UBM policies, which are indicated in green, you can pass parameters
from the Source Rule to the Chained Rule, if the latter is a Parameterized User-
Defined Rule (PUDR) and if the Chain meets certain other conditions. For more
information on how to create a PUDR see the FortiDB MA User Behavior Monitor
(UBM) User Guide. For more information on using PUDRs in a chain, see
Chaining with Parameterized User-Defined Rules).

FortiDB Version 3.2 Utilities User Guide
12 15-32000-81369-20081219
Chaining with Parameterized User-Defined Rules Rule Chaining
General PUDR Steps
The general step for creating a chain that uses a PUDR are:
1In UBM, define an Object, User, or Session policy that will be your Source Rule.
2In UBM, define a PUDR that will be your Target Rule
3In the Rule Chaining module, define a chain which associates the UBM policy and
the PUDR.
PUDR Process
Parameterized User-Defined Rule Flow Diagram
The PUDR process involves these steps.
1The source rule is violated and an alert is generated.
2FortiDB MA determines if there is a PUDR that is chained to the source rule.
• If a rule is chained, FortiDB MA fetches the information on the chain
relationship
3FortiDB MA checks to see if the source rule is to be run immediately or not.
4FortiDB MA checks to see if the chained rule is a PUDR vs. a regular policy
aIf a regular UDR, FortiDB MA runs the UDR without passing any
variables.
bIf the rule is a PUDR and is set to be run immediately, FortiDB MA
passes the parameters defined in the rule chain to the PUDR.
cIf the rule is a PUDR and is set to be run with the schedule settings of
the source rule, FortiDB MA indicates that parameters have to be
passed for the successful execution of the PUDR.
5An alert is generated for the PUDR.

Rule Chaining Chaining with Parameterized User-Defined Rules
FortiDB Version 3.2 Utilities User Guide
15-32000-81369-20081219 13
PUDR Eligible Rules
Disabled Parameter Checkboxes
If the chosen target rule cannot accept parameters, they will be grayed out.
Validating the PUDR before Saving
If one or more variables selected do not appear in the PUDR, FortiDB MA
presents a warning message.

FortiDB Version 3.2 Utilities User Guide
14 15-32000-81369-20081219
Chaining with Parameterized User-Defined Rules Rule Chaining
Chaining the UBM Policy and PUDR Together
Associating a Source Rule That Can Pass parameters with a PUDR
Example of Chaining to a PL/SQL-based PUDR
In this Oracle PL/SQL kill-session example, we:
1Create a DB user, BAD_GUY, whose session we will monitor, in our Oracle target
database.
Item Setting for Session Policy

Rule Chaining Chaining with Parameterized User-Defined Rules
FortiDB Version 3.2 Utilities User Guide
15-32000-81369-20081219 15
Policy Settings for Suspicious Login Time
2Create a UBM Session Policy, our Source rule, in order to monitor BAD_GUY and
generate an alert to trigger our Target rule, a PUDR. We will pass the Session ID
from the Source to the Target rule.
3Create a Target PUDR, in the UBM module, which will contain the following kill-
session code. That code, in turn, will accept our passed Session ID parameter
(shown in red):

FortiDB Version 3.2 Utilities User Guide
16 15-32000-81369-20081219
Chaining with Parameterized User-Defined Rules Rule Chaining
4Login as BAD_GUY at an "abnormal" time (Here, that is anytime except between 3
and 4 AM)
DECLARE
v_str VARCHAR2(80) := 'ALTER SYSTEM KILL SESSION
'||chr(39);
v_statementVARCHAR2(80);
sesid NUMBER;
serial NUMBER;
usernameVARCHAR(50);
osuser VARCHAR(50);
machine VARCHAR(50);
program VARCHAR(50);
BEGIN
SELECT sid, serial#,username,osuser,machine,program
INTO sesid,serial,username,osuser,machine,program
FROM v$session
WHERE audsid =$sessionid;
v_statement := v_str||sesid||','||serial||chr(39)||'
IMMEDIATE';
EXECUTE IMMEDIATE v_statement;
DBMS_OUTPUT.PUT_LINE
(TO_CHAR
(SYSDATE,'YYYY/MM/DD HH24:MI:SS') ||
' A suspicious session has been killed.'||
' [Username]'||username||
' [Osuser]'||osuser||' [Machine]'||machine||
' [Program]'||program) ;
EXCEPTION
WHEN no_data_found THEN
DBMS_OUTPUT.PUT_LINE
(TO_CHAR
(SYSDATE,'YYYY/MM/DD HH24:MI:SS') ||
' A suspicious session is not found at this moment.');
END;

Rule Chaining Chaining with Parameterized User-Defined Rules
FortiDB Version 3.2 Utilities User Guide
15-32000-81369-20081219 17
Chained-Rule Alerts: (UBM Session Policy and PUDR)
5Get an alert when the (the Session Policy) Source rule is violated.
6Get another alert when the chained PUDR executes and, in this case kills the
session of BAD_GUY.
7And, in the Alert Details dialog, display DB user name, OS user name, machine
name, and source-program name as shown above.
Resulting Killed Session
8Notice that our SQLPlus session has been killed
Alert Behavior
This topic describes various alert behavior users should be aware of.
Table Columns That Could Appear in Alerts
Be careful when specifying the SQL for your UDRs. Statements like "SELECT *
FROM <table_name>", where <table_name> has a lot of columns, may produce
alerts that are difficult to read due to the large number of columns. It is better to be
more specific like "SELECT <column_name1>, ... , <column_nameN> from
<table_name>".
For example using Oracle, v$session has over 40 columns, so instead of this
statement:
SELECT * FROM v$session WHERE osuser = '$osusername'
you might want to use one with specific columns, like:

FortiDB Version 3.2 Utilities User Guide
18 15-32000-81369-20081219
Chaining with Parameterized User-Defined Rules Rule Chaining
SELECT username, osuser, terminal FROM v$session WHERE osuser =
'$osusername'
Multiple Source-Rule-Violation Behavior
When using the Rule Chaining feature with PUDRs, you might expect a target-
policy alert for each source-policy alert. However, unless there is a change in the
passed parameter, there will be only one PUDR alert--despite multiple source-
policy alerts.
For example, assume you have a session policy for your source rule, are passing
the terminal name to the target PUDR, and that the session policy is violated
twice. In this case, you will get two session-policy alerts because, due to different
timestamps, the session policy alerts are not the same. However, you will get only
one PUDR alert because the terminal name doesn't change.
DB Example
For example, when using a DB2 target database and passing $objectowner,
only one PUDR (target rule) alert will show up, regardless of how many times the
source rule gets violated. (A source-rule alert will appear for each violation.)
$objectowner is replaced by the creator parameter which represents the
authorization ID of the user who pre-compiled the application1. This ID does not
change when a user executes multiple SQL queries thereby triggering multiple
source-rule alerts. Therefore, you can expect only one PUDR alert.
For example, assume:
aYou set up a source-rule User Policy that monitors user X.
bYou have a target-rule PUDR that expects $objectowner to be
passed; like this:
SELECT '$objectowner' FROM SYSIBM.SYSDUMMY1 AS
SYSDUMMY1
cUser X issues these two queries:
SELECT * from my.employee
SELECT * from x.table1
In this case, two source-rule alerts should show up but only one PUDR (target
rule) alert.
PUDR Alert Behavior with Multiple SELECT-List Objects in the Violating SQL State-
ment
FortiDB MA can detect, and alert on, only the first item in a multiple-object
SELECT list.
For example, assume you have created a user policy which gets violated by a
user's executing:
SELECT * FROM vje.test, vje.test1
1. For more information, see
http://publib.boulder.ibm.com/infocenter/db2luw/v8/index.jsp?topic=/com.ibm.db2.udb.doc/admin/r000
7595.htm