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.

Tip: For more information on how third-party integrations work, see Connectors.

Connector Details

Details Description

Supported products

HackerOne

Category

Bug Bounty

Ingested data

Assets and Findings

Ingested Asset Classes

Web Application

Integration type

UNI directional (data is transferred from the Connector to Tenable Exposure Management in one direction)

Supported version and type

SaaS (latest)

Prerequisites and User Permissions

Before you begin configuring the connector, make sure you have the following:

Generate API Identifier and Token in HackerOne

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

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

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

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

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

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

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.

API Endpoints in Use

API version: v1

/me/programs

Program ID for following steps

/programs/{programId}

Program handle for following steps and asset enrichment
/programs/{programId}/structured_scopes Assets (Web applications)
/reports?filter[program][]={programHandle}

Findings

Detections

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 in HackerOne aligns with the number of assets 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:

  • The asset status changed to one of the selected statuses defined in the Asset Retention configuration.

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

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.