Latest update: 2022-07-25
Purpose
This article provides setup information on the Database Connector integration.
Introduction
The Database Connector integration allows the HIAB appliance to export vulnerability findings and related scan data to an external database. Direct access to the internal HIAB database is not provided because it is subject to structural changes for performance optimization and security reasons. Instead, the database connector provides a controlled method for making scan results available outside the platform. By configuring this integration, organizations can automatically send findings data to a supported external database such as Microsoft SQL, MySQL, or PostgreSQL.
This capability is useful when vulnerability data needs to be processed or consumed by other systems, reporting tools, or internal analytics platforms. Once exported, the data can be queried, correlated with other security or operational information, or integrated into existing workflows. The connector therefore enables organizations to extend the value of their vulnerability scanning results by supporting custom analysis, external integrations, and centralized security data management without exposing the internal HIAB database structure.
Requirements
When connecting to the database, you must have permissions to create tables as well as updating data.
Supported External Databases:
-
MS SQL
-
MySQL
-
PostgreSQL
Set Up Database Integration
To set up Database integration:
-
Go to Menu > Settings > Integrations.
-
In the Integration Settings window, select the Database tab.
-
Provide the below information to set up a Database connector:
|
Option |
Description |
|---|---|
|
Host |
Provide the hostname of the external database server. |
|
Port |
Provide the port number the database connector is using to communicate. |
|
Database Name |
Provide the database name of he external database server to which findings data should be exported. |
|
Type |
Select one of the types from the drop-down menu:
|
|
Trust certificate |
When checked the server certificate is trusted, and no checks are performed on it. Default is unchecked. |
|
Username |
Provide the username to authenticate against external database server. |
|
Password |
Provide the password to authenticate against external database server. |
|
Table Name |
Provide a valid name for table in the database. A table is created automatically during HIAB - DB integration process. You can use any special character supported by ASCII, depending on the type of database |
-
Click the Save button to save the current settings.
Set Up a Report Schedule
-
In the HIAB go to Main menu > Netsec > Reporting tools and select the Scheduling tab.
-
Create a schedule with Recipient type as Database and Table Name same as in Integration.
-
Click Save.
Related Articles
- ServiceNow - Legacy
- Identity Provider Settings
- Okta Identity Provider Configuration
- Database Connector (HIAB only)
- Azure AD Identity Provider Configuration
- SNMP (HIAB only)
- ADFS Identity Provider Configuration
- Splunk
- Amazon
- Atlassian Jira
- Syslog (HIAB only)
- Thycotic
- OneLogin Identity Provider Configuration
- CyberArk
- LDAP/AD