Configuring the Discoverer

Configuration Settings

SectionKeyValueDescription
[Database]TNS_ADMIN<network service="" name="" location=""></network>Location from where network service names needs to be read
-NET_SERVICE_NAME<net_service_name></net_service_name>Network Service name to be used to make connection
-WALLET_LOCATION<ssl wallet="" location="">|<seps wallet="" location=""></seps></ssl>Location of wallets for secured connections via SSL or SEPS (Secure External Password Store)
-DB_HOSTNAME<hostname>|<ip_address></ip_address></hostname>Hostname or IP Address of the target database server
-DB_PORT

<portnumber></portnumber>

The default is 1521.

Listener port number for the target database. If a port number is not specified, the default port 1521 is used.
-DB_SERVICE_NAME<service_name></service_name>Service name for the target database
-SSL_ENABLED

TRUE | FALSE

The default is FALSE.

Specifies if SSL is enabled or disabled when connecting to the Database Server. This is an optional argument.

It is recommended that the SSL_ENABLED value is set to TRUE. Retain the default FALSE value if you do not require an SSL connection to the Database Server.

If SSL_ENABLED = TRUE, then SSL_TRUSTSTORE is mandatory.

-SSL_TRUSTSTORE

<absolute path="" to="" the="" truststore="" filename=""></absolute>

Example: /opt/oracle/wallets/truststore.jks

Specifies the absolute path to the TrustStore, and the TrustStore file name.

Mandatory if SSL_ENABLED = TRUE.

-SSL_TRUSTSTORE_TYPEPKCS12 | JKS | SSO

Specifies the type of TrustStore.

Use PKCS12 if the Truststore is a Wallet.

Use JKS if the Truststore is an Oracle Java KeyStore.

Use SSO if the Truststore is an auto-login SSO Wallet.

-SSL_KEYSTORE

<absolute path="" to="" the="" keystore="" filename=""></absolute>

Example: /opt/oracle/wallets/keystore.jks

Specifies the absolute path to the KeyStore, and the KeyStore file name.

If SSL_KEYSTORE is not specified, the value specified in SSL_TRUSTSTORE is used.

Mandatory if the Database server requires client authentication.

-SSL_KEYSTORE_TYPEPKCS12 | JKS | SSO

Specifies the type of KeyStore.

Use PKCS12 if the KeyStore is a Wallet.

Use JKS if the KeyStore is an Oracle Java KeyStore.

Use SSO if the KeyStore is an auto-login SSO Wallet.

-SSL_DN<distinguished_name></distinguished_name>

Distinguished Name (DN) of the target Database server.

Specify the DN if the server’s DN needs to be checked.

This is an optional argument.

-SSL_VERSION

1.0 | 1.1 | 1.2

The default is 1.2.

Specifies the version of the SSL protocol to use when connecting to the Database Server. This is an optional argument.

Use 1.0 for SSL version TLSv1.0.

Use 1.1 for SSL version TLSv1.1.

Use 1.2 for SSL version TLSv1.2.

-SSL_CIPHER_SUITES

<cipher_suite1>,<cipher_suite2></cipher_suite2></cipher_suite1>

Example: TLS_RSA_WITH_AES_256_CBC_SHA256 , SSL_RSA_WITH_RC4_128_MD5

Specifies the Cryptographic Algorithms to be used. Multiple entries can be specified as a comma-separated list.

This is an optional argument.

For information about supported cryptographic suites, see https://docs.oracle.com/javase/8/docs/technotes/guides/security/SunProviders.html.

[Discovery Parameters]SENSITIVE_PATTERN_FILES

<file_name>| <file_name1>,<file_name2></file_name2></file_name1></file_name>

The default is sensitive_en.ini.

Specifies the pattern files to be used. Multiple files can be specified as a comma-separated list. The limit is 10 files.

For more information about configuring the Sensitive Data Type pattern file, see Pattern File Configuration (Optional).

-SCHEMA_SCOPE

ALL | <schema1>,<schema2></schema2></schema1>

The default is ALL.

Specifies the schemas to be scanned. Multiple schemas can be specified as a comma-separated list.
-MINROWS

<numerical value=""></numerical>

The default is 1.

Specifies the minimum number of rows in a table for that table to be scanned.

Tables with a number of rows less than what is specified in the minrows parameter are excluded from the scan.

-EXCLUSION_LIST_FILE<exclusion_list_filename>.ini</exclusion_list_filename>

Specifies the file to be used to exclude schemas, tables, or columns from the scan.

For more information about configuring the Exclusion List file, see Configuring the Exclusion List File (Optional).

[Sensitive Categories]

The [Sensitive Categories] section defines which Sensitive Categories are used. Valid risk levels are:

  • Low Risk
  • Medium Risk
  • High Risk

The types of sensitive data are defined in the Sensitive Data Type pattern file. For more information about configuring the Sensitive Data Type pattern file, see Pattern File Configuration (Optional).