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

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

Connector Details

Details Description

Supported products

 ORDR AI Protect for Security

Category

OT (Operational Technology)

Asset Inventory

Network Scanner

Ingested data

Assets and Findings

Ingested Asset Classes

Devices

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 to:

  1. Identify your ORDR Server URL (e.g., , https://ordr-sce.example.com or https://192.168.1.50)

  2. Generate ORDR integration credentials (username and password).

Generate ORDR Integration Credentials

To generate credentials in the ORDR platform:

  1. Log in to the ORDR platform.

  2. In the top navigation bar, click Integrations.
    The External Services and Tools Integration page appears.

  3. In the search box, type Platform API.

  4. In the results table, click Platform API.
    The Platform API (Service Detail) panel appears.

  5. In the API Username and API Password boxes, type a username and password.

  6. Copy the Username and Password to a safe location. You need them to configure the connector.

  7. Click Save.

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 page 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 Server URL text box, enter the ORDR Server URL of your organization.

  3. In the Username and Password text boxes, enter the credentials you generated earlier.

  4. Data pulling configuration: This configuration has dynamic settings tailored to the specific connector and integration type. Below are the configurations relevant to this connector.

    • Fetch Vulnerabilities: (Optional) To fetch vulnerabilities in addition to devices, select the Fetch Vulnerabilities checkbox.

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

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

Finding Severity Mapping

Tenable Exposure Management Severity

ORDR Score

Critical

CVSS: 9.0 - 10.0

Severity: Critical

High

CVSS: 7.0 - 8.9

Severity: High

Medium

CVSS: 4.0 - 6.9

Severity: Medium

Low

CVSS: 1-3.9

Severity:Low

None

CVSS:0

Severtity: empty

Note:For ORDR, Tenable uses the riskScore field to determine severity

Finding Status Mapping

Tenable Exposure Management Status

ORDR Status

Active

 All other statuses

Fixed

clear=True

mute=True

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.

Update Type in Tenable Exposure Management

Mechanism (When?)

Archiving Assets

  • Asset that appears in Tenable Exposure Management and isn't returned on the next connector's sync.

  • Asset not seen for X days according to "Last Seen". See Asset Retention

Change a Finding status from "Active" to "Fixed"

  • Finding no longer appears in the scan findings

  • Finding status changes to clear=True or mute=True on the vendor's side.
Note: Updates on the vendor side are reflected in Tenable Exposure Management only when the next scheduled connector sync time is complete (once a day).

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:

Data

Uniqueness Criteria

Asset

MacAddress

Detection vulnId

Finding

Asset unique value + Detection unique value + alarmHash

API Endpoints in Use

API version: 1.0.21

API

Use in Tenable Exposure Management

GET {{{ server_url }}}/Rest/Devices

Devices

GET {{{ server_url }}}/Rest/Vulnerabilities

Findings

Data Validation

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

Asset Data Validation

Objective: Ensure the number of devices in ORDR aligns with the number of devices displayed in Tenable Exposure Management.

In ORDR:

  1. Navigate to Devices.

  2. Note the total number of Devices.

In Tenable Exposure Management:

  1. Locate your connector assets.

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

Expected outcome: The total numbers returned in ORDR and Tenable Exposure Management should match.

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

  • Archived based on the last observed date (field last_Seen_list)

  • Archived because it is not under the same tenant GUID.

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

Finding Data Validation

Objective: Ensure the number of findings in ORDR aligns with the number of findings in Tenable Exposure Management.

In ORDR:

  1. Navigate to Security > Vulnerabilities and Info.

  2. In Vulnerability Summary, note the total number of Vulnerabilities.

  3. Click a vulnerability to view its details and affected assets.

Expected outcome: The total numbers returned in ORDR and Tenable Exposure Management should match.

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

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

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