Purplemet Connector

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

Purplemet is a Web Application Security Monitoring SaaS solution focused on what hackers may see and exploit. It's complementary to scanners enabling cyber hygiene on a URL portfolio while providing an additional list of vulnerabilities and technologies.

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

Connector Details

Details Description

Supported products

Purplemet

Category

DAST

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:

  • Ensure that your Purplemet account has a Purplemet subscription. Otherwise, the API endpoints are not available.

  • Purplemet API Key

Generate a Purplemet API Key

  1. Navigate to your Purplemet platform.

  2. In the left menu, click Tokens.

  3. Click Add.

  4. Type a Friendly Name (for example, ExposureManagementAPI) and enable the Activation toggle.

  5. Click Generate.

  6. In the upper-right corner, click Confirm.

  7. Ensure the status of the generated API token is Enabled.

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 Key text box, paste the API key you generated in Purplemet.

  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:

Purplemet 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.15.4

https://api.purplemet.com/site

https://api.purplemet.com/site/tag

https://api.purplemet.com/site/{tag_id}/site

https://api.purplemet.com/issue

Findings

Detections

Data Validation

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

Asset Data Validation

Objective: Ensure the number of web applications in Purplemet aligns with the assets displayed in Tenable Exposure Management.

In Purplemet:

  1. Navigate to Web Applications from the left navigation menu.

  2. The list of all web applications associated with the tenant will be displayed.

In Tenable Exposure Management:

  1. Locate your connector assets.

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

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