BlackDuck (formerly WhiteHat) Connector

The following is not supported in Tenable FedRAMP Moderate environments. For more information, see the Tenable FedRAMP Product Offering.

BlackDuck Continuous Dynamic (formerly WhiteHat™ Dynamic) rapidly and accurately finds vulnerabilities in websites and applications with the scale and agility you need to identify security risks across your entire application portfolio.

Prerequisites and User Permissions

Before you begin configuring the connector, make sure to:

• Identify your WhiteHat API (BlackDuck Continuous Dynamic) URL (e.g., https://sentinel.whitehatsec.com/api)

• Generate a WhiteHat (BlackDuck Continuous Dynamic) API Key:

  1. Navigate to the BlackDuck Continuous Dynamic Platform.

  2. In the My Profile page, select API Key.

  3. Type your password into the Verify Password text field.

  4. Click Authenticate to display your key. If you have never requested your API key before, a key will be generated for you.

  Tip: For more information, see the WhiteHat Documentation.

Add a Connector

To add a new connector:

1. In the left navigation menu, click Connectors.

   The Connectors page appears.

   

2. In the upper-right corner, click Add new connector.

   The Connector Library appears.

   

3. In the search box, type the name of the connector.

4. On the tile for the connector, click Connect.

   The connector configuration options appear.

Configure the Connector

To configure the connector:

1. (Optional) In the Connector's Name text box, type a descriptive name for the connector.

2. (Optional) To use a preconfigured on-prem connector to connect to this connector, from the Gateway drop-down, select the on-prem connector you want to use for the connector. Otherwise, select Don't use gateway.

   Note: For information about configuring a gateway, see Tenable On-Prem Connector.

3. In the API Url section, type your Whitehat (BlackDuck Continuous Dynamic) API base URL.

4. In the API Key text box, paste the API key you generated in Whitehat (BlackDuck Continuous Dynamic).

5. In the Data pulling configuration section, you can configure dynamic settings specific to the connector.

   • In the Asset Retention text box, type the number of days after which you want assets to be removed from Tenable Exposure Management. If an asset has not been detected or updated within the specified number of days, it is automatically removed from the application, ensuring your asset inventory is current and relevant.

     Tip: For more information, see Asset Retention.

6. In the Test connectivity section, click the Test Connectivity button to verify that Tenable Exposure Management can connect to your connector instance.
   

   • A successful connectivity test confirms that the platform can connect to the connector instance. It does not, however, guarantee that the synchronization process will succeed, as additional syncing or processing issues may arise.
     

   • If the connectivity test fails, an error message with details about the issue appears. Click Show tests for more information about the exact error.
     

     

7. In the Connector scheduling section, configure the time and day(s) on which you want connector syncs to occur.

   Tip: For more information, see Connector Scheduling.

8. Click Create. Tenable Exposure Management begins syncing the connector. The sync can take some time to complete.
   

9. To confirm the sync is complete, do the following:

   • Navigate to the Connectors page and monitor the connector's status. Sync is complete once the connector status is Connected.

   • View the sync logs for the connector to monitor the logs for a successful connection.

BlackDuck Continuous Dynamic in Tenable Exposure Management

Locate Connector Assets in Tenable Exposure Management

As the connector discovers assets, Tenable Exposure Management ingests those devices for reporting.

To view assets by connector:

1. In Tenable Exposure Management, navigate to the Assets page.

2. In the Filters section, under 3rd Party Connectors, click the connector name for which you want to view assets.

   

   The asset list updates to show only assets from the selected connector.

3. Click on any asset to view Asset Details.

Locate Connector Weaknesses in Tenable Exposure Management

As the connector discovers weaknesses, Tenable Exposure Management ingests those weaknesses for reporting.

To view weaknesses by connector: 

1. In Tenable Exposure Management, navigate to the Weaknesses page.

2. In the Filters section, under 3rd Party Connectors, click the connector name for which you want to view weaknesses.

   

   The weaknesses list updates to show only weaknesses from the selected connector.

3. Click on any weakness to view Weakness Details.

Locate Connector Findings in Tenable Exposure Management

As the connector discovers individual findings, Tenable Exposure Management ingests those findings for reporting.

To view findings by connector:

1. In Tenable Exposure Management, navigate to the Findings page.

2. In the Filters section, under 3rd Party Connectors, click the connector name for which you want to view findings

   

   The findings list updates to show only assets from the selected connector.

3. Click on any asset to view Finding Details.

Data Mapping

Exposure Management integrates with the connector via API to retrieve relevant weakness and asset data, which is then mapped into the Exposure Management system. The following tables outline how fields and their values are mapped from the connector to Exposure Management.

Web Application Mapping

Tenable Exposure Management Value	WhiteHat (BlackDuck Continuous Dynamic) Value
Unique Identifier	id
Asset - Name	label
Asset - First Observation Date	first_completed_scan.timestamp
Asset - Last Observed At	last_completed_scan.timestamp
Asset - Webapp Homepage Screenshot Url	allowed_hosts[0.hostname
Asset - External Tags	tags
Asset Custom Attributes	id client_id organization description allowed_hosts asset_owner_name wsi_global_rank wsi_score scan_status asset_phase groups

Finding Mapping

Tenable Exposure Management UI Field	WhiteHat (BlackDuck Continuous Dynamic) Field
Unique Identifier	id
Finding Name	class
Severity Driver	cvss_v3_scoreor or cvss_v3_score_rating
Description	description.description
First Seen	opened
Last seen (Observed)	modified
Finding Custom Attributes	attack_vectors description_prepend whitehat link: https://source.whitehatsec.com/asset-management/site-summary/{{ site }}/findings/{{ id } impact reason risk cvss_v3_score_rating cvss_v3_vector

Finding Status Mapping

Finding Severity Mapping

Uniqueness Criteria

Tenable Exposure Management uses defined uniqueness criteria to determine whether an ingested asset or finding should be recognized as a distinct record. These criteria help define how assets and findings are identified and counted from each connector.

Tip:  Read all about Third-Party Data Deduplication in Tenable Exposure Management

The uniqueness criteria for this connector are as follows:

Status Update Mechanisms

Every day, Tenable Exposure Management syncs with the vendor's platform to receive updates on existing findings and assets and to retrieve new ones (if any were added).

The table below describes how the status update mechanism works in the connector for findings and assets ingested into Tenable Exposure Management.

API Endpoints in Use

Data Validation

This section shows how to validate and compare data between Tenable Exposure Management and the BlackDuck Continuous Dynamic platform.

Asset Data Validation

Objective: Ensure the number of assets in BlackDuck Continuous Dynamic aligns with the number of assets displayed in Tenable Exposure Management.

In BlackDuck Continuous Dynamic:

1. Navigate to the Assets section.

2. Set the assets filter to:

   • Asset type: Site

     

3. Click Filter to apply.

   These site assets correspond to the filtered BlackDuck Continuous Dynamic DAST assets in Exposure Management.

In Tenable Exposure Management:

1. Locate your connector assets.

2. Compare the total number of assets between BlackDuck Continuous Dynamic DAST and Tenable Exposure Management.

Expected outcome: The total numbers returned in BlackDuck Continuous Dynamic and Exposure Management should match.

If an asset is not visible in Exposure Management, check the following conditions:

• Archived based on the last observed date (last seen).

• Archived because it did not return in the connector's next sync.

  Tip: To learn more on how assets and findings change status, see Status Update Mechanisms.

Finding Data Validation

Objective: Ensure that the total number of findings between BlackDuck Continuous Dynamic and Exposure Management is consistent.

In BlackDuck Continuous Dynamic:

1. Navigate to the Findings section.

2. Set the findings filter to:

   • Asset type: Site

   • Vulnerability Status: Open

3. Click Filter to apply.

4. Scroll to the bottom of the list to view the total number of open findings.

In Tenable Exposure Management:

1. Locate your connector findings.

2. Compare the total number of findings between BlackDuck Continuous Dynamic and Tenable Exposure Management.

Expected outcome: Exposure Management only displays findings that are in "Open" status and tied to an asset of type "Site" in WhiteHat (BlackDuck Continuous Dynamic). Counts may differ if filters are misapplied or if related assets are missing. If filtered correctly in both platforms, the total number returned in WhiteHat (BlackDuck Continuous Dynamic) and Exposure Management should match.

If a finding is missing from Exposure Management or no longer active, check the following conditions:

• The finding is marked as Fixed and appears under the Fixed state on the Findings screen.

• The finding no longer appears because its related asset was archived.

  Tip: To learn more on how assets and findings are archived or change status, see Status Update Mechanisms.