Claroty xDome

Claroty xDome is a modular SaaS-based cybersecurity platform capable of long-term flexibility. You can configure Claroty xDome to send device alert events (when determined to be a threat) through an API endpoint to generate third-party alerts in InsightIDR.

Data can be sent from your Claroty xDome account to InsightIDR from event collection through the Cloud.

To set up the Claroty xDome event source, complete these steps:

1. Read the requirements and complete any prerequisite steps.
2. Configure Claroty xDome to send data to InsightIDR.
3. Configure InsightIDR to collect data from the event source.
4. Test the configuration.

You can also:

• Review sample logs.

Requirements

Before InsightIDR can start ingesting data from Claroty xDome, you must:

• Create an API user
• Generate an API token

Configure Claroty xDome to send data to InsightIDR

To ensure InsightIDR can receive data from Claroty xDome, you must configure a few settings within the Claroty xDome platform.

1. Log in to your Claroty xDome account and create an API User from Admin Settings > User Management. Read the documentation from Claroty xDome for further guidance.
2. Select a role for your API user with adequate permissions for alerts and devices. If a role does not exist, you can generate one from the Role Based Permissions page. A Read-Only user is sufficient for this configuration.
3. Choose your Site Permissions.
4. Generate an API token. Store this token in a secure place for later use.

Configure InsightIDR to receive data from the event source

After you create your API User in Claroty xDome and obtain the API token, you can set up your Claroty xDome event source in InsightIDR.

Task 1: Select Claroty xDome

1. Go to Data Collection and click Setup Event Source > Add Event Source.
2. Do one of the following:
   • Search for Claroty xDome in the event sources search bar.
   • In the Product Type filter, select Third Party Alerts.
3. Select the Claroty xDome event source tile.

Task 2: Set up the Cloud Connection

1. In the Add Event Source panel, select Run On Cloud.
2. Name the event source. This will be the name of the log that contains the event data in Log Search. If you do not name the event source, the log name will default to Claroty xDome.
3. Optionally, select the option to send unparsed data.
4. Select your Account Attribution preference:
   • Use short name attribution: The system first attempts to attribute data by email address, for example, jsmith@myorg.example.com. If the first attempt is unsuccessful, attribution is attempted by short name, for example, jsmith. If the short name is unsuccessful, attribution is attempted by a user’s first and last name, for example, John Smith.
   • Use fully qualified domain name attribution: The system first attempts to attribute data by email address, for example, jsmith@myorg.example.com. If the first attempt is unsuccessful, attribution is attempted by a user’s first and last name, for example, John Smith. This option is best if your environment has collisions with short names.
5. Optionally, in a multi-domain environment, use the dropdown menu to select your main Active Directory domain. See Deploy in Multi-domain Environments and Advanced Event Source Settings.
6. Click Add a New Connection.
7. In the Create a Cloud Connection screen, enter a name for the new connection.
8. In the API Token field, add a new credential:
   • Name your credential.
   • Describe your credential.
   • Select the credential type.
   • Enter the API Token you created in Configure Claroty xDome to send data to InsightIDR.
   • Specify the product access for this credential.
9. Optionally, enter the hostname for your Claroty xDome instance. If a value is not entered, the hostname defaults to api.claroty.com.
10. Click Save Connection.
11. Click Save.

Test the configuration

The event types that InsightIDR parses from this event source are:

• Third Party Alerts

To test that event data is flowing into InsightIDR through the Cloud Connection:

1. View the raw logs:
   1. From the Data Collection Management page, click the Event Sources tab.
   2. Find the event source you created and click View raw log. If the Raw Logs modal displays raw log entries, logs are successfully flowing to InsightIDR.
2. Use Log Search to find the log entries. After approximately seven minutes, you can verify that log entries are appearing in Log Search.
   1. From the left menu, go to Log Search.
   2. In the Log Search filter, search for the new event source you created.
   3. Select the log sets and the log names under each log set. Claroty xDome logs flow into these log sets:
      • Third Party Alerts
   4. Set the time range to Last 10 minutes and click Run.

The Results table displays all log entries that flowed into InsightIDR in the last 10 minutes. The keys and values that are displayed are helpful when you want to build a query and search your logs.

Sample logs

Single device alert

 
1
  {
2
      "alert_assignees": [],
3
      "alert_category": "Risk",
4
      "alert_class": "predefined",
5
      "alert_description": "Outdated firmware detected on 2 None devices",
6
      "alert_id": 2,
7
      "alert_labels": [
8
        "Top Priority"
9
      ],
10
      "alert_type_name": "Outdated Firmware",
11
      "device_alert_detected_time": "2023-10-19T16:21:01+00:00",
12
      "device_alert_status": "Unresolved",
13
      "device_alert_updated_time": "2023-10-19T16:21:01+00:00",
14
      "device_assignees": [
15
        "Admin"
16
      ],
17
      "device_category": "Medical",
18
      "device_first_seen_list": [
19
        "2023-10-19T16:32:04.127979+00:00"
20
      ],
21
      "device_ip_list": [
22
        "10.101.10.27"
23
      ],
24
      "device_labels": [],
25
      "device_last_seen_list": [
26
        "2023-10-19T16:32:01+00:00"
27
      ],
28
      "device_mac_list": [
29
        "00:40:9d:10:15:b7"
30
      ],
31
      "device_network_list": [
32
        "Corporate"
33
      ],
34
      "device_purdue_level": "Level 4",
35
      "device_retired": false,
36
      "device_risk_score": "Very Low",
37
      "device_site_name": "New York General Hospital",
38
      "device_subcategory": "Patient Devices",
39
      "device_type": "Patient Monitor",
40
      "device_uid": "f342efb7-4f4a-4ac0-8045-0711fb2c5528",
41
      "mitre_technique_enterprise_ids": [],
42
      "mitre_technique_enterprise_names": [],
43
      "mitre_technique_ics_ids": [],
44
      "mitre_technique_ics_names": []
45
    }