1. Oracle Database Security Assessment Tool User Guide
  2. Configuring the Exclusion List File (Optional)

Configuring the Exclusion List File (Optional)

You can optionally specify schemas, tables, or columns to exclude from the scan in the Exclusion List file.

This is an optional step but often required to fine tune the Discoverer to exclude false positives.

To create an Exclusion List file, do the following:

  1. Create an Exclusion List file, and save it in the Discover/conf directory as myexclusion_list.
  2. Specify the schemas, tables, or columns to exclude from the Discoverer scan.
    The following is a sample of the contents of the Exclusion List file.
PAYROLL
IT.ENTITLEMENTS
HR.EMPLOYEE.MARITAL_STATUS
HR.JOB.CANDIDATE

Specify the schemas, tables, or columns to exclude using the format SchemaName.TableName.ColumnName. Type each exclusion entry on a new line.

In the example above, PAYROLL excludes the PAYROLL schema from the discovery scan; IT.ENTITLEMENTS excludes the ENTITLEMENTS table in IT schema; HR.EMPLOYEE.MARITAL_STATUS excludes column MARITAL_STATUS from the HR.EMPLOYEE table. Similarly, HR.JOB.CANDIDATE excludes column CANDIDATE from HR.JOB table.

Note:

The Discoverer CSV report includes a column with the fully qualified column names (FULLY_QUALIFIED_COLUMN_NAME). This column can be used to create the exclusion list file contents and speed up the removal of unwanted columns or false positives from the report in a subsequent run.

  1. Save and close the Exclusion List file.
  2. Update the exclusion_list_file entry in your custom_dbsat.config file to exclusion_list_file = myexclusion_list

For more information about referencing the Exclusion List file, see Configuring dbsat.config.