HackerOne Connector

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

HackerOne is a vulnerability coordinator and bug bounty platform that connects businesses with penetration testers and cybersecurity researchers.

The HackerOne platform allows organizations to set their scope, track bug reports, and manage payouts from one location. When integrated with the Tenable Exposure Management, you can review Website vulnerabilities on your assets, while leveraging the power of Tenable Exposure Management discoverability and automation. In this article, you will find how to connect, locate, and automate HackerOne with Tenable Exposure Management.

Prerequisites and User Permissions

Before you begin configuring the connector, make sure to:

• Generate HackerOne API Identifier and Token:

  Note: Because this is a read-only user, when you create the API identifier, there is no need to assign the identifier or token to a group.

  1. In HackerOne, navigate to Organization Settings > API Tokens.

  2. Click Create API Token.

  3. Enter an identifier for the new API token. Copy the identifier somewhere safe.

  4. Click Add API token.

  5. Store the generated API token.

  6. Click I have stored the API Token.

     TIP: For more information, see HackerOne documentation on API Tokens.

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 Identifier and API Key text boxes, paste the API credentials you generated in HackerOne.

4. 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.

5. 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.
     

     

6. 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.

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

8. 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.

HackerOne 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	HackerOne Value
Unique Identifier	asset_identifier
Asset - Name	asset_identifier
Asset - First Observation Date	created_at
Asset - Last Observed At	updated_at
Asset - Webapp Homepage Screenshot Url	asset_identifier
Asset - External Tags	handle eligible_for_bounty eligible_for_submission
Asset Custom Attributes	reference max_severity

Finding Mapping

Tenable Exposure Management UI Field	HackerOne Field
Unique Identifier	asset_identifier + report id
Finding Name	title
CVEs	cve_ids
CWEs	external_id
Severity Driver	score or rating
Description	vulnerability_information
First Seen	created_at
Last seen (Observed)	last_activity_at
Finding Custom Attributes	custom_fields report_id report_state asigned_to hackerone_rating weakness_type weakness_type_description reporter_name reporter_username attack_vector attack_complexity privileges_required user_interaction scope confidentiality integrity availability cvss_score eligible_for_bounty eligible_for_submission relationships.structured_scope.data.attributes.asset_identifier

Finding Status Mapping

Finding Severity Mapping

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.

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:

Support Limitations and Expected Behavior

This section outlines any irregularities, expected behaviors, or limitations related to integration of the connector and Exposure Management. It also highlights details about ingested and non-ingested data to clarify data handling and functionality within this integration.

API Endpoints in Use

API version: v1

Data Validation

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

Asset Data Validation

Objective: Ensure the number of assets (Domains) in HackerOne aligns with the number of assets (Web Applications) displayed in Tenable Exposure Management.

In HackerOne:

1. From the top menu bar, select the relevant Program/Company name.

   

2. Scroll down to see the Program assets list in the Scopes table.

   Important! Only domains are ingested into the Exposure Management platform.

   

In Tenable Exposure Management:

1. Locate your connector assets.

2. Compare the total number of assets between HackerOne and Tenable Exposure Management.

Expected outcome: The total numbers returned in HackerOneand Exposure Management should match.

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

• 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 HackerOne and Exposure Management is consistent.

In HackerOne:

1. Navigate to Inbox and note the program reports.

   
   

2. Filter to see only open states (findings).

3. Click on a specific report (finding) to see it’s related asset.

   

In Tenable Exposure Management:

1. Locate your connector findings.

2. Compare the total number of findings between HackerOne and Tenable Exposure Management.

Expected outcome: The total numbers returned in HackerOne 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.