JDBC log source parameters for Oracle Fine Grained Auditing
If QRadar does not automatically detect the log source, add a Oracle Fine Grained Auditing log source on the QRadar Console by using the JDBC protocol.
When using the JDBC protocol, there are specific parameters that you must use.
| Parameter | Value |
|---|---|
| Log Source type | Oracle Fine Grained Auditing |
| Protocol Configuration | JDBC |
| Log Source Identifier |
Type a name for the log source. The name can't contain spaces and must be unique among all log sources of the log source type that is configured to use the JDBC protocol. If the log source collects events from a single appliance that has a static IP address or host name, use the IP address or host name of the appliance as all or part of the Log Source Identifier value; for example, 192.168.1.1 or JDBC192.168.1.1. If the log source doesn't collect events from a single appliance that has a static IP address or host name, you can use any unique name for the Log Source Identifier value; for example, JDBC1, JDBC2. |
| Database Type |
Oracle |
| Predefined Query |
From the list, select None. |
| Table Name |
Type dba_fga_audit_trail as the name of the table that includes the event records. If you change the value of this field from the default, events cannot be properly collected by the JDBC protocol. |
| Compare Field |
Type extended_timestamp to identify new events added between queries to the table by their time stamp. |
| Use Prepared Statements |
Select the Use Prepared Statements check box. Prepared statements allow the JDBC protocol source to set up the SQL statement one time, then run the SQL statement many times with different parameters. For security and performance reasons, it is suggested that you use prepared statements. Clearing this check box requires you to use an alternative method of querying that does not use pre-compiled statements. |
For a complete list of JDBC protocol parameters and their values, see JDBC protocol configuration options.