Claroty xDome 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

Claroty xDome

Category

OT (Operational Technology)

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:

Create Claroty xDome User and Generate API Token

To create Claroty xDome API user, grant permissions, and generate API token:

  1. Login with Admin user to Claroty xDome portal.

  2. Navigate to Settings > Admin Settings > User Management.

  3. Click Create User.

  4. In the Username and Title fields, enter a name that clearly identifies the user as dedicated for the integration with Exposure Management.

  5. In the Site Permissions section, select the sites that you want to include in the connector’s scope.

  6. From the Roles list, select Read-Only User.

  7. Click Create User.

  8. After creating the user, click Generate Token.

  9. Save the token in a secure location. You will use it later in the connector setup page in 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 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. (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. 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.

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

Claroty xDome 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.

Device Mapping

Tenable Exposure Management UI Field

[Connector] Field
Unique Identifier UID

Asset - External Identifier or

Asset - Provider Identifier

 vmMetadata.vmId or id
Asset - Name  
Asset - Operating Systems osPlatform

Asset - IPv4 Adresses

Asset - IPv6 Adresses

lastIpAddress and lastExternalIpAddress
Asset - MAC Addresses network_interface.data.properties.macAddress
Asset - Host Fully Qualified DNS fqdn
Asset - First Observation Date firstSeen
Asset - Last Observed At lastSeen

Asset - External Tags

machineTags

computerDnsName

rbacGroupName

healthStatus

riskScore

managedBy

exposureLevel

lastExternalIpAddress

osPlatform

Asset Custom Attributes

device_id: id

healthStatus

exposureLevel

osBuild

osVersion or version

Finding Severity Mapping

Tenable Exposure Management Severity

Claroty xDome 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 Claroty xDome, Tenable uses the cvssScore field to determine severity. If cvssScore is not available, Tenable uses the severity field from the connector, if provided.

Finding Status Mapping

Tenable Exposure Management Status

Claroty xDome Status

Active

all other statuses

Fixed

status=fixed

vulnerability_relevance=irrelevant

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 Exposure Management

Mechanism (When?)

Archiving Assets

    • Asset that appears in Exposure Management and is not returned on the next connector sync.

    		•

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

    • Finding no longer appears in the scan findings.

    • Finding status changes to fixed on the vendor 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

    uid

    Detection vulnerability_id

    Finding

    Asset unique value+ Detection unique value

    API Endpoints in Use

    API version: 1.0

    API

    Use in Tenable Exposure Management

    POST {{{ server_url }}}/api/v1/devices

    Fetch devices

    POST {{{ server_url }}}/api/v1/device_vulnerability_relations

    Fetch findings

    Data Validation

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

    Asset Data Validation

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

    In Claroty xDome:

    1. Navigate to Devices > All Devices.

    2. Notice the total number of devices.

    3. If the API key is scoped to specific sites, apply the same site filter to ensure a matching scope.

    4. Confirm you are viewing the correct active device status (not archived).

    In Tenable Exposure Management:

    1. Locate your connector assets.

    2. Compare the total number of assets between Claroty xDome and Exposure Management.

    Expected outcome: The total numbers returned in Claroty xDome and Exposure Management should match.

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

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

    • Devices that belong to a site not included in the API key's scope will not be ingested.

      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 Claroty xDome aligns with the number of findings in Tenable Exposure Management.

    In Claroty xDome:

    1. Navigate to Risk & Exposure > Vulnerabilities > All Vulnerabilities.

    2. Notice the total number of device-vulnerability pairs.

    In Tenable Exposure Management:

    1. Locate your connector findings.

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

    Expected outcome: The total numbers returned in Claroty xDome 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 or out of scope.

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