---
sourceDocument: Australia Operational Technology Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/operational-technology

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Operational Technology Management

ft:clusterId :

    - optm

bundleId :

    - optm

workflow :

    - Technology


---

# Service Graph Connector Integration for Claroty CTD

# Service Graph Connector Integration for Claroty CTD {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Service Graph Connector Integration for Claroty CTD

The Service Graph Connector Integration for Claroty Continuous Threat Detection (CTD) enables users to seamlessly integrate Claroty CTD with the ServiceNow Operational Technology Manager application.
This integration allows for the importation of detected devices and sites, enhancing the Configuration Management Database (CMDB) with critical security data.
Show full answer Show less  

## Key Features

* **Supported Versions:** Compatible with Claroty CTD versions 4.4.3 and later.
* **Data Import:** The integration facilitates the import of sites, detected devices, connections, and installed programs into the CMDB.
* **Guided Setup:** Provides an organized sequence for configuring the integration.
* **CMDB Integrations Dashboard:** Offers a central view to monitor the status and results of all integrations, allowing for filtering by time or integration run.
* **Data Mapping:** Utilizes the Robust Transform Engine (RTE) for data mapping from Claroty CTD to ServiceNow CMDB classes.
* **Default Query Parameters:** Includes built-in filters to control the import of devices based on approval and validation status.

## Key Outcomes

By integrating with the ServiceNow platform, organizations can enhance their operational visibility, improve security incident response, and maintain accurate asset records in the CMDB. This integration ensures that only relevant and validated data from Claroty CTD is imported, streamlining asset management and threat detection processes.  
Integrate Claroty Continuous Threat Detection (CTD) with the ServiceNow
Operational Technology Manager application to import detected devices and Claroty CTD sites (sensor or Network Intrusion Detection System appliances).

## Request apps on the Store {#sgc-cmdb-integration-claroty-ctd__section_ot5_kdx_hyb}

Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) website to view all the available apps and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the [ServiceNow Store version history release notes](https://www.servicenow.com/docs/r/store-release-notes/sn-store-release-notes.html).

## Supported versions {#sgc-cmdb-integration-claroty-ctd__section_qlx_sdx_hyb}

Claroty CTD Version:

* 4.4.3 or later
* 5.1
{#sgc-cmdb-integration-claroty-ctd__ul_obr_xqx_1fc}

## Use cases {#sgc-cmdb-integration-claroty-ctd__section_abl_xdx_hyb}

Use the Service Graph Connector Integration for Claroty Continuous Threat Detection with the Operational Technology Manager application to import the following information to the Configuration Management Database (CMDB)

* Sites
* Devices detected by each site
* Connections (or baselines)
* Installed programs

{#sgc-cmdb-integration-claroty-ctd__ul_jtl_ydx_hyb}

The following figure shows the detection method for importing Claroty CTD data into the CMDB.

## Guided setup {#sgc-cmdb-integration-claroty-ctd__section_vmn_12x_hyb}

The guided setup for the Service Graph Connector Integration for Claroty CTD provides an organized sequence of tasks to configure the integration on your instance. To access the guided setup, see [Configure guided setup](https://servicenow-prod.fluidtopics.net/muHWRrURuB2V1CNL2PIq6w "Use the guided setup for Service Graph Connector Integration for Claroty CTD to lead you through the integration steps.").

## CMDB integrations dashboard {#sgc-cmdb-integration-claroty-ctd__section_anq_fww_prb}

The Integration Commons for CMDB store app provides a dashboard with a central view of the status, processing results, and processing errors of all installed integrations. You can see metrics for all integration runs. You
can filter the view to a specific CMDB integration, a specific time duration, or a specific integration run. For more details about monitoring integrations in the CMDB Integrations Dashboard, see [Integration Commons for CMDB](https://www.servicenow.com/docs/access?context=integration-commons-for-cmdb&version=australia&pubname=australia-servicenow-platform&ft:locale=en-US#section_fxg_lh4_blb).

## Data mapping {#sgc-cmdb-integration-claroty-ctd__section_oyb_cfx_hyb}

Data from the Claroty CTD data sources is mapped and transformed into the ServiceNow
CMDB Configuration Item (CI) class definitions using the Robust Transform Engine (RTE). Data is inserted into the ServiceNow
CMDB using the Identification and Reconciliation Engine (IRE).  
The following table lists the data sources included for the Service Graph Connector Integration for Claroty CTD and the corresponding staging tables where the imported data is loaded.{#sgc-cmdb-integration-claroty-ctd__table_hj2_r1x_c1c__entry__2}

| Data source | Staging table |
|-|-|
| SG-OT Claroty CTD Devices | SG-OT Claroty CTD Devices Import \[sn_clarotyctdsgc_sg_ot_claroty_ctd_devices_import\] |
| SG-OT Claroty CTD Baselines | SG-OT Claroty CTD Baselines Import \[sn_clarotyctdsgc_sg_ot_claroty_ctd_baselines_import\] |
| SG-OT Claroty CTD Programs | SG-OT Claroty CTD Programs Import \[sn_clarotyctdsgc_sg_ot_claroty_ctd_programs_import\] |
| SG-OT Claroty CTD Sites | SG-OT Claroty CTD Sites Import \[sn_clarotyctdsgc_sg_ot_claroty_ctd_sites_import\] |
[Table 1. Data sources and staging tables for Claroty CTD]

{#sgc-cmdb-integration-claroty-ctd__table_hj2_r1x_c1c}

The imported data from the staging tables is then inserted into the following target tables:

* Computer \[cmdb_ci_computer\]
* Hardware \[cmdb_ci_hardware\]
* IP Address \[cmdb_ci_ip_address\]
* Network Adapter \[cmdb_ci_network_adapter\]
* OT Device Details \[cmdb_ot_entity\]
* OT Control Module \[cmdb_ci_ot_control_module\]
* OT Control System \[cmdb_ci_ot_control\]
* Serial Number \[cmdb_serial_number\]

{#sgc-cmdb-integration-claroty-ctd__ul_mkw_qfx_hyb}

For more information, see [CMDB classes targeted](https://servicenow-prod.fluidtopics.net/ZGBlaBIwMarvSLdetWkr6A "When you complete the setup tasks, you can configure the integration periodically to pull data from Claroty CTD. The data is saved in tables that extend from the Configuration item [cmdb_ci] table.").

## Default query parameters for the Service Graph Connector Integration for Claroty CTD {#sgc-cmdb-integration-claroty-ctd__section_shz_rtd_kyb}

By default, the Service Graph Connector Integration for Claroty CTD is shipped with query parameter filters. You can modify their values based on ServiceNow entitlements that you have with the IntegrationHub Enterprise package.

When you begin importing the data from the Claroty CTD, the Service Graph Connector Integration for Claroty CTD uses the default query parameter filters that are listed in the following table.
{#sgc-cmdb-integration-claroty-ctd__filters-sgc-claroty-ctd_table_xlv_kpr_kwb_entry_3}

| Query parameter filter | Value | Description |
|-|-|-|
| approved_exact | true | Unapproved devices on the Claroty CTD aren't imported because the value of approved_exact is set to true. |
| valid_exact | true | Invalid devices on the Claroty CTD aren't imported because the value of valid_exact is set to true. |
| special_hint_exact | 0 | Address types that aren't set to 0 (unicast) on the Claroty CTD aren't imported. |
| ghost_exact | false | If there's an device on the Claroty CTD that is classified as a ghost, the Service Graph Connector Integration for Claroty CTD doesn't import it because the default value is set to false. |
[Table 2. Default query parameter filters]

{#sgc-cmdb-integration-claroty-ctd__table_yl3_xtd_kyb}
* **[Configure the Service Graph Connector Integration for Claroty CTD](https://servicenow-prod.fluidtopics.net/muHWRrURuB2V1CNL2PIq6w)**   
  Use the guided setup for Service Graph Connector Integration for Claroty CTD to lead you through the integration steps.
* **[Validate NIDS sensors](https://servicenow-prod.fluidtopics.net/3GGlxUEQakAD09SIG1orNA)**   
  Validate the Network IDS (NIDS) sensors once they're imported to prepare for device import. The sensors can only pass the validation if they aren't in learning mode as such sensors aren't eligible for device import.
* **[Accessing the connection details of the Service Graph Connector Integration for Claroty CTD](https://servicenow-prod.fluidtopics.net/j5_wzcKgKehdmkzzOQLc7A#sgc-cmdb-claroty-ctd-conn)**   
  You can access the connection details of the Service Graph Connector Integration for Claroty CTD in a single view using the common connection framework (CCF) included within the Integration Commons for CMDB (sn_cmdb_int_util) store app.
* **[CMDB classes targeted in the Service Graph Connector Integration for Claroty CTD](https://servicenow-prod.fluidtopics.net/ZGBlaBIwMarvSLdetWkr6A)**   
  When you complete the setup tasks, you can configure the integration periodically to pull data from Claroty CTD. The data is saved in tables that extend from the Configuration item \[cmdb_ci\] table.

