Discovering Databases for Target Registration

super administrators can import XML files resulting from the Nmap scan command of specified IP address and port ranges to determine which Oracle, Microsoft SQL, MySQL, DB2, or PostgreSQL databases in your database fleet are yet to be registered with Oracle Database Security Central.

About Discovering Databases for Target Registration

super administrators can import the XML file resulting from the Nmap scan command of specified IP address and port ranges to identify databases available for registration with Oracle Database Security Central. Discovered databases can then be assigned to administrators for registration with Oracle Database Security Central.

If you have many databases in your fleet, it may be difficult to determine which ones are not yet registered with Oracle Oracle Database Security Central. The Database Discovery feature allows you to scan specified IP address and port ranges using Nmap commands to determine which databases haven’t been registered with Oracle Database Security Central. The results of the Nmap scan will inform you which Oracle, Microsoft SQL, MySQL, DB2, or PostgreSQL databases have not been registered as targets.

The XML file that is the output of the Nmap scan command is the list of databases. This file can be imported to the Oracle Database Security Central console by a super administrator to list all un-registered databases. Each database can be ignored from future scans or assigned to an administrator for target registration.

Executing Nmap Scan Commands

In order to use the Database Discovery feature, you need to run the Nmap scan command to discover databases in your database fleet. A super administrator will need to upload the results of the Nmap scan command to the Audit Vault Server.

Prerequisites

Contact your network administrator or check your organization’s policies before executing Nmap scan command.
Download the Nmap command tool.

Nmap Download

Note: Only Nmap version 7.92 and 7.94 are supported.

Procedure

While on a Windows or Linux platform, run the following command on a host in your network:
```
nmap -sV -n -p T:<p1-p2> <ip range> --host-timeout <time in minutes>  -oX <xml filepath>
```
Attributes:
- sV - Optional, Probes open ports to determine service/version information.
- n - Optional, No DNS resolution. This option slashes scanning time
- p T:<p1 to p2> - This option scans TCP protocol for port range p1 to p2.
  
  If you do not know the port range, it is recommended to scan the complete port range of 0 - 65536.
- IP Range - IP range that need to scanned. One example is given above, but for more type of ranges refer to the Nmap command documentation
- host-timeout - Enter a time in minutes after which the scan on the host will stop. Some hosts simply take a long time to scan. This may be due to poorly performing or unreliable networking hardware or software, packet rate limiting, or a restrictive firewall.
- oX - XML output file location
For example:
```
nmap -sV -n -p T:1430-6607 10.89.89.0-10.89.89.255 --host-timeout 2m -oX /tmp/tmp.xml
```
Ensure that the XML file is accessible by a super administrator.

Related Topics

Nmap documentation

Importing the XML File for Database Discovery as a Super Administrator

After successfully running the Nmap scan command, the XML file needs to be imported to the Oracle Database Security Central console by a super administrator. Databases can then be assigned to administrators for registration.

Log in to Oracle Database Security Central Console as a super administrator.
Select Targets.
In the left menu, select Database Discovery.
Select Import Nmap XML.
Select Choose File.
Navigate to location of the Nmap output file.
Select Save to import the XML file.
After the XML has been successfully imported, delete the XML file from your local system.

A super administrator will be able to see the list of databases discovered in the Nmap scan and their registration status with DBSecCentral in Database Discovery in the Oracle Database Security Central console.

Related Topics

Viewing the Status of the XML Import Job

Assigning Databases for Registration in Database Discovery as a Super Administrator

After importing the XML file, a super administrator can see the list of discovered databases and their registration status with Oracle Database Security Central. A super administrator can then assign the unregistered databases to other administrator users for target registration.

Log in to Oracle Database Security Central Console as a super administrator.
Select Targets.
In the left menu, select Database Discovery.
Select the database(s) you want to assign to an administrator for registration.
Select Assign admin.
Select the administrator user to assign the database(s) to.

Select Select in the drop down of users if you’d like to unassign the database(s).
Select Save.

Registering Assigned Databases in Database Discovery

If you are an administrator with assigned databases or a super administrator you can register discovered databases with Oracle Database Security Central directly from Database Discovery.

Log in to the Oracle Database Security Central console as a super administrator or an administrator.
Select Targets.
In the left menu, select Database Discovery.
Select a database you want to register with Oracle Database Security Central.

You can only select one database at a time.
Select Register.
Complete registration of the selected database.

For more information see Registering or Removing Targets in Audit Vault Server.

Managing Discovered Databases as a Super Administrator

Super administrators can manage the table of discovered databases by either ignoring or deleting databases.

Ignore a Database

An ignored database appears in the Ignored databases report. You can later move it back to the Discovered databases list or delete it permanently.

Log in to Oracle Database Security Central Console as a super administrator.
Select Targets.
In the left menu, select Database Discovery.
(Optional) Apply or remove filters to the table.
In the Discovered databases report, select the database(s) you want to ignore.

Note: Registered databases cannot be ignored.
Select Ignore.

The selected databases will move to the Ignored databases report (collapsed by default).
(Optional) Enter a comment explaining why the database(s) is being ignored.
Select Save.

Move Ignored Databases Back to the Discovered Databases List

You can move an ignored database back to the Discovered databases list or delete it permanently.

Log in to Oracle Database Security Central Console as a super administrator.
Select Targets.
In the left menu, select Database Discovery.
(Optional) Apply or remove filters to the table.
In the Ignored databases report, select the database(s) you want to move back or delete.
Select Move to discovered databases.

The selected databases will move to the discovered databases report (collapsed by default).
(Optional) Enter a comment explaining why the database(s) is being moved back.
Select Save.

Delete a Database

A deleted database is removed from the table of discovered databases. However, if an XML file from the Nmap scan is imported again, any removed databases will once again show up in the table.

Log in to Oracle Database Security Central Console as a super administrator.
Select Targets.
In the left menu, select Database Discovery.
(Optional) Apply or remove filters to the table.
Select the database(s) you want to delete.
Select Delete.

Viewing the Status of the XML Import Job

Once the XML file has been imported, administrators can view the details and status of the Database Discovery job.

Log in to Oracle Database Security Central Console as an administrator.
Select Settings.
Select System in the left navigation menu.
In the Monitoring section, select Jobs.
Find a Database discovery job to view the details.
Select job details icon to see more details about the job including:
- The user that performed the import
- The time it took for the import to complete
- The number of databases discovered on how many IP addresses