Database
Nessus supports database authentication using PostgreSQL, DB2, MySQL SQL Server, Oracle, and MongoDB.
Database
Nessus supports the following authentication methods:

Option |
Description |
---|---|
Username |
The username for the database. |
Password |
The password for the supplied username. |
Database Type |
Nessus supports Oracle, SQL Server, MySQL, DB2, Informix/DRDA, and PostgreSQL. |

In Nessus Manager, you have the option of using CyberArk to manage your credentials. CyberArk is a popular enterprise password vault that helps you manage privileged credentials to use in a scan.

Option | Description |
Required |
---|---|---|
Username | The target system’s username. | yes |
Lieberman host |
The Lieberman IP/DNS address. Note: If your Lieberman installation is in a subdirectory, you must include the subdirectory path. For example, type IP address or hostname / subdirectory path. |
yes |
Lieberman port | The port on which Lieberman listens. | yes |
Lieberman API URL | The URL Nessus uses to access Lieberman. | no |
Lieberman user | The Lieberman explicit user for authenticating to the Lieberman API. | yes |
Lieberman password | The password for the Lieberman explicit user. | yes |
Lieberman Authenticator |
The alias used for the authenticator in Lieberman. The name should match the name used in Lieberman. Note: If you use this option, append a domain to the Lieberman user option, i.e., domain\user. |
no |
Lieberman Client Certificate |
The file that contains the PEM certificate used to communicate with the Lieberman host. Note: If you use this option, you do not have to enter information in the Lieberman user, Lieberman password, and Lieberman Authenticator fields. |
no |
Lieberman Client Certificate Private Key | The file that contains the PEM private key for the client certificate. | no |
Lieberman Client Certificate Private Key Passphrase | The passphrase for the private key, if required. | no |
Use SSL |
If Lieberman is configured to support SSL through IIS, check for secure communication. |
no |
Verify SSL Certificate |
If Lieberman is configured to support SSL through IIS and you want to validate the certificate, check this option. Refer to Custom CA documentation for how to use self-signed certificates. |
no |
System Name | In the rare case your organization uses one default Lieberman entry for all managed systems, enter the default entry name. | no |
Database Port | The port on which Nessus communicates with the database. | yes |
Database Name | (PostgreSQL and DB2 databases only) The name of the database. | no |
MongoDB
Option |
Description |
---|---|
Username |
The username for the database. |
Password |
The password for the supplied username. |
Database |
Name of the database to audit. |
Port |
Port the database listens on. |