> For the complete documentation index, see [llms.txt](https://docs.dispel.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dispel.com/integrate-and-administer/integrations/asset-discovery/claroty-xdome.md).

# Claroty xDome

Connect Claroty xDome, through its cloud API, to pull discovered OT, IoT, and IIoT devices into Dispel — enriched with vulnerability findings — mapped to a Wicket.

## Overview

The Claroty xDome integration lets Dispel pull the OT, IoT, and IIoT assets xDome has discovered and bring them in as Dispel devices, enriched with xDome's vulnerability findings. You connect to your xDome tenant once, map it to a Dispel facility and Wicket, and Dispel imports the matching devices and keeps them current on a recurring sync.

Claroty xDome is a cloud asset-discovery integration. Dispel authenticates to the xDome API with an API token and only ever reads from it. Because an xDome tenant represents a single environment, Dispel treats it as one site that you map to a single Wicket — there is no per-site list to work through.

#### What Dispel imports

* Devices xDome has discovered, matched to your existing Dispel devices and imported as new devices where there's no match.
* xDome's vulnerability findings (CVE-based, with CVSS v3 scores) as findings on the matching devices, so you can see a device's known issues without leaving Dispel.

{% hint style="info" %}
**Where to find it.** Sign in as an organization administrator and open [**Settings → Integrations**](https://app.dispel.com/settings/integrations). Claroty xDome appears in the **Asset Discovery / Network Visibility** section. Click **Connect** on the Claroty xDome card to begin.
{% endhint %}

## Before you begin

You'll need the following from xDome:

* An **API token**. In xDome, go to **Settings → Admin Settings → User Management**, create an API User, then generate a token for it.
* Your region-specific **xDome API host** — for example `https://api.claroty.com` or `https://eu.api.claroty.com`.

{% hint style="warning" %}
**The API token is shown once.** xDome displays the token only when you generate it. Copy it then; if you lose it, generate a new one.
{% endhint %}

{% hint style="info" %}
**The token's permissions scope what Dispel sees.** Dispel imports the assets the API User is allowed to read, so give the API User access to the sites whose devices you want in Dispel.
{% endhint %}

## Connecting Claroty xDome

1. Go to [**Settings → Integrations**](https://app.dispel.com/settings/integrations) and click **Connect** on the Claroty xDome card.
2. Optionally set a **Display Name** to tell this integration apart from others (you can connect more than one instance).
3. Fill in the connection fields:

| Field                       | Type       | Notes                                                                                                |
| --------------------------- | ---------- | ---------------------------------------------------------------------------------------------------- |
| **API URL**                 | Config     | Your region-specific xDome API host, e.g. `https://api.claroty.com` or `https://eu.api.claroty.com`. |
| **API Token**               | Credential | The token generated for an API User in xDome. Stored encrypted and never shown again.                |
| **Include Retired Devices** | Config     | Optional. When on, Dispel also imports devices xDome has marked retired. Off by default.             |

4. Click **Test Connection** to confirm Dispel can authenticate. Fix any reported error before saving.
5. Click **Save**. Dispel saves the integration and immediately runs the initial sync.

{% hint style="info" %}
**Your credentials are encrypted.** The API token is encrypted at rest and is never displayed again after you save. When editing later, leave the token field blank to keep the stored value.
{% endhint %}

## Mapping the tenant to a Wicket

Once the initial sync finishes, open the integration to find the **Site Mapping** section. Claroty xDome appears as a single site representing your tenant.

> Map each vendor site to a Dispel facility and Wicket. Devices from mapped sites will be synced into Dispel.

1. Pick a **Facility**.
2. Pick a **Wicket**. If the facility has only one Wicket, Dispel selects it for you.
3. Click **Save Mappings & Import**.

Dispel imports xDome's devices into the mapped Wicket and then reports how many devices were imported. Imported devices appear in the mapped Wicket alongside any devices you've added manually, with their xDome vulnerability findings attached.

## Keeping your inventory current

* Dispel re-syncs automatically on a recurring schedule, so newly discovered devices, changed details, and new findings are picked up without any action from you.
* To pull the latest inventory immediately, open the integration and choose **Refresh**.
* To change connection details or rotate the token, edit the integration and use **Save & Sync**. Leave the token field blank to keep the current token.

Vulnerability findings refresh on every sync, and findings xDome no longer reports drop off automatically.

## Connection status

Each integration shows a status so you always know where it stands:

| Status              | Meaning                                                 |
| ------------------- | ------------------------------------------------------- |
| **Not Initialized** | Saved, but the first sync hasn't run yet.               |
| **Initializing**    | Running the first sync.                                 |
| **Ready**           | Connected and synced; the mapping is applied.           |
| **Needs Refresh**   | New vendor data is available; run a refresh to pull it. |
| **Refreshing**      | A sync is in progress.                                  |
| **Pending Changes** | Mapping changes are saved but not yet applied.          |
| **Applying**        | Importing devices for your saved mapping.               |
| **Failed**          | The last operation failed — see the error guidance.     |

A separate **health badge** (Connected, Degraded, Unreachable) reflects whether Dispel can currently reach the xDome API.

## Troubleshooting

If a sync or test connection fails, Dispel classifies the error and suggests a fix:

| Error                     | What it usually means and how to fix it                                                                                                                       |
| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Authentication Failed** | The API token was rejected. Confirm the API User is active in xDome and the token is current — it's shown only once, so generate a new one if it was lost.    |
| **Endpoint Unreachable**  | Dispel couldn't reach xDome. Verify the API URL is your correct region-specific host (for example `https://api.claroty.com` or `https://eu.api.claroty.com`). |
| **Connection Timed Out**  | xDome took too long to respond — usually a transient network issue; try again.                                                                                |

## Frequently asked questions

<details>

<summary>Where do I create the API token?</summary>

In xDome, go to **Settings → Admin Settings → User Management**, create an API User, and generate a token for it. The token is shown only once, so copy it before leaving the page.

</details>

<details>

<summary>Which API URL should I use?</summary>

Your region-specific xDome API host, for example `https://api.claroty.com` or `https://eu.api.claroty.com`. Use the host for the region your xDome tenant runs in.

</details>

<details>

<summary>What findings does Claroty xDome bring into Dispel?</summary>

xDome's vulnerability findings — CVE-based, with CVSS v3 scores — attached to the matching devices. Findings refresh on every sync, and any xDome no longer reports drop off automatically.

</details>

<details>

<summary>Does Dispel change anything in xDome?</summary>

No. The integration is read-only. Dispel pulls inventory and findings but never creates, modifies, or deletes data in xDome.

</details>

<details>

<summary>Can I connect more than one xDome tenant?</summary>

Yes. Claroty xDome supports multiple integrations, so you can connect several tenants side by side. Give each a distinct **Display Name** to tell them apart.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dispel.com/integrate-and-administer/integrations/asset-discovery/claroty-xdome.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.