Configure Tenable.sc for HashiCorp Vault (Database)
Required User Role: Any
In Tenable.sc, you can integrate with HashiCorp Vault using database credentials. Complete the following steps to configure Tenable.sc with HashiCorp Vault using database.
Before you begin:
- Ensure you have both a Tenable.sc and HashiCorp Vaultaccount.
Note: HashiCorp Vault provides options for both, KV v1 and v2. However, Tenable.sc only supports integration with KV v1.
To integrate Tenable.sc with HashiCorp Vault using database credentials:
Log in to Tenable.sc.
Click Scanning > Credentials (administrator users) or Scans > Credentials (organizational users).
The Credentials page appears.
At the top of the page, click +Add.
The Add Credential page appears.
- Go to the Database section.
- Click the database type that you want to use. (IBM DB2, MySQL, Oracle Database, PostgreSQL, or SQL Server)
In the Name box, type a name for the credential.
(Optional) Add a Description.
(Optional) Add a Tag to the credential. For additional information about tags, see the Tags section in the Tenable.sc documentation.
- (For Oracle only) Click the Source drop-down to select a source type.
- In the database credential section, click the Authentication Method drop-down.
- Select HashiCorp Vault.
In the Database Credential section, configure the database credentials.
Option Credential Description Required Port
The port on which Tenable.sc communicates with the database. yes SID MySQL The security identifier used to connect to the database. yes Database Name
The name of the database. no Instance Name SQL Server The SQL server name. yes
The Hashicorp Vault IP address or DNS address.
Note: If your Hashicorp Vault installation is in a subdirectory, you must include the subdirectory path. For example, type IP address or hostname/subdirectory path.
The port on which Hashicorp Vault listens.
yes Service Type Oracle Database The unique SID or Service Name that identifies your database. yes Service Oracle Database
The SID or Service Name value for your database instance.
Note: The Service value must match the Service Type option parameter selection.
Specifies the authentication type for connecting to the instance: App Role or Certificates.
yes Client Cert All If Authentication Type is Certificates, the client certificate file you want to use to authenticate the connection. yes Private Key All If Authentication Type is Certificates, the private key file associated with the client certificate you want to use to authenticate the connection. yes
The GUID provided by Hashicorp Vault when you configured your App Role.
yes Role Secret ID All
The GUID generated by Hashicorp Vault when you configured your App Role.
yes Authentication URL All
The path/subdirectory to the authentication endpoint. This is not the full URL. For example:
yes Namespace All The name of a specified team in a multi-team environment. no Hashicorp Vault Type All
The type of Hashicorp Vault secrets engine:
- KV1 — Key/Value Secrets Engine Version 1
- KV2 — Key/Value Secrets Engine Version 2
- AD — Active Directory
yes KV Engine URL All The URL Tenable.sc uses to access the Hashicorp Vault secrets engine. yes
All (Only displays if Hashicorp Vault Type is KV1 or KV2)Specifies if the username is input manually or pulled from Hashicorp Vault. yes Username key All (Only displays if Hashicorp Vault Type is KV1 or KV2)The name in Hashicorp Vault that usernames are stored under. no
(Only displays if Username Source is Manual Entry) The name in Hashicorp Vault that usernames are stored under.
yes Password key All (Only displays if Hashicorp Vault Type is KV1 or KV2)The key in Hashicorp Vault that passwords are stored under. no Secret Name All The key secret you want to retrieve values for. yes Use SSL All When enabled, Tenable.sc uses SSL for secure communications. You must configure SSL in Hashicorp Vault before enabling this option. no Verify SSL All When enabled, Tenable.sc validates the SSL certificate. You must configure SSL in Hashicorp Vault before enabling this option. no
Tenable.sc saves the credential.