Bright Connector

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

The following steps allow you to configure this connector for use with Tenable Exposure Management from start to finish.

Prerequisites and User Permissions

Before you begin configuring the connector, make sure to:

• Create an API key in Bright:

  1. Navigate to Settings > API Keys.
  2. Select Create API Key.
  3. For Scopes, select: groups:read, projects:read, and issues:read.
  4. Do not set an expiration date.
  5. Save the key securely.

  Important!The user account creating the key must have access to all Bright projects you intend to ingest into Exposure Management.

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 Keytext box, paste the API key you generated earlier.

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

   • (Optional) Fetch unconfirmed issues: Select to ingest issues that Bright has not yet confirmed. Clearing this option in a later sync marks previously ingested unconfirmed issues as Fixed in Exposure Management.

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

Bright 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 UI field	Bright field
Asset Uniqueness criteria	id
Asset – Name	ns
Asset - Last Observed At	summary.lastScan
Asset - Custom Attributes	groups (from enrichment) labels (list) id scansByStatus (list) issuesBySeverity (list) issuesLength lastScan uniqueHosts
Asset - External Tags	labels, groups (from enrichment)

Finding Mapping

Tenable Exposure Management UI field	Bright field
Findings uniqueness criteria	id (Issue ID)
Finding > Name	type
Severity Driver	severity
Finding > Description	details
CVEs	cve
CWEs	cwe
First Seen	createdAt
Last Seen (Observed)	lastReported
Custom Attributes	page url - ' Bright Security ' +projectId +'/issues/'+ id method entryPointId resources (list) screenshots (list) exposure details request (dict) response (dict) protocol url resources

Finding Status Mapping

Tenable Exposure Management status	Bright status
Open (Active)	New, Recurring
Risk Acknowledged	Ignored
Fixed	Resolved

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:

API Endpoints in Use

API version: v2.2.2

Support Limitations and Expected Behavior

• Bright Core is out of scope.
• Fetch unconfirmed issues:
  • If you select this option for one sync and clear it for a subsequent sync, all previously ingested unconfirmed issues are marked Fixed in Tenable Exposure Management.

Data Validation

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

Asset Data Validation

Objective: Confirm that the number of Bright projects equals the number of Bright web applications in Exposure Management (after accounting for configuration and archiving).

In Bright:

1. Navigate to Projects and ensure all relevant projects are visible.
2. If you configured scope‑limiting options (for example, only certain projects), apply equivalent filters.
3. Record the total number of projects.

In Exposure Management:

1. Navigate to Assets.
2. Filter 3rd Party Connectors to Bright and Asset Type to Web Application.
3. Compare the total asset count with the Bright projects count.

Expected outcome: The total number of Bright projects matches the number of Bright web applications in Tenable Exposure Management. Minor differences can occur if projects were archived, excluded by connector scope, or not returned in the most recent sync.

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

• The asset was archived because it was not returned in the last sync or due to Asset Retention settings.

Finding Data Validation

Objective: Confirm that the number of Bright issues on a given project matches the number of Exposure Management findings for that web application.

In Bright:

1. Open a project and navigate to Issues.
2. Use the export or on‑screen totals to obtain the issue count.

In Exposure Management:

1. Navigate to Findings and filter by Bright.
2. Filter down to the specific web application (project) and compare the finding count.

Expected outcome: The number of Bright issues matches the number of findings in Tenable Exposure Management for the same project. Differences may occur if findings were marked Resolved, excluded from the latest sync, or associated with assets that were archived.

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

• The finding was marked Resolved in Bright and appears as Fixed in Tenable Exposure Management.

• The finding was not returned by Bright in the most recent sync.

• The related asset was archived and is no longer visible.