🚫 🔍 [Deprecated] Claroty via Legacy Agent

🚫 Deprecated: This connector has been deprecated and may be removed in future versions.

🔍 Discovered: This item was discovered by scanning the solution folder but is not listed in the Solution JSON file.

Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊

↑ Back to Connectors Index

Attribute Value
Connector ID Claroty
Publisher Claroty
Used in Solutions Claroty
Collection Method AMA
Connector Definition Files Connector_Claroty_CEF.json

The Claroty data connector provides the capability to ingest Continuous Threat Detection and Secure Remote Access events into Microsoft Sentinel.

Additional Information

🛠️ Device Configuration: Navigate to Configuration > Syslog > Add. Configure Remote Server IP, Port, Protocol, and set Message Format to CEF. Save.

Tables Ingested

This connector ingests data into the following tables:

Table Selection Criteria Transformations Ingestion API Lake-Only
CommonSecurityLog DeviceVendor == "Claroty" ✓ ✓ ✓

💡 Tip: Tables with Ingestion API support allow data ingestion via the Azure Monitor Data Collector API, which also enables custom transformations during ingestion.

Permissions

Resource Provider Permissions:

Setup Instructions

⚠️ Note: These instructions were automatically generated from the connector's user interface definition file using AI and may not be fully accurate. Please verify all configuration steps in the Microsoft Sentinel portal.

NOTE: This data connector depends on a parser based on a Kusto Function to work as expected ClarotyEvent which is deployed with the Microsoft Sentinel Solution.

1. Linux Syslog agent configuration

Install and configure the Linux agent to collect your Common Event Format (CEF) Syslog messages and forward them to Microsoft Sentinel.

Notice that the data from all regions will be stored in the selected workspace 1.1 Select or create a Linux machine

Select or create a Linux machine that Microsoft Sentinel will use as the proxy between your security solution and Microsoft Sentinel this machine can be on your on-prem environment, Azure or other clouds.

1.2 Install the CEF collector on the Linux machine

Install the Microsoft Monitoring Agent on your Linux machine and configure the machine to listen on the necessary port and forward messages to your Microsoft Sentinel workspace. The CEF collector collects CEF messages on port 514 TCP.

  1. Make sure that you have Python on your machine using the following command: python -version.
  1. You must have elevated permissions (sudo) on your machine.

Configure log forwarding using CEF:

  1. Navigate to the Syslog section of the Configuration menu.

  2. Select +Add.

  3. In the Add New Syslog Dialog specify Remote Server IP, Port, Protocol and select Message Format - CEF.

  4. Choose Save to exit the Add Syslog dialog.

3. Validate connection

Follow the instructions to validate your connectivity:

Open Log Analytics to check if the logs are received using the CommonSecurityLog schema.

It may take about 20 minutes until the connection streams data to your workspace.

If the logs are not received, run the following connectivity validation script:

  1. Make sure that you have Python on your machine using the following command: python -version
  1. You must have elevated permissions (sudo) on your machine

4. Secure your machine

Make sure to configure the machine's security according to your organization's security policy

Learn more >

Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊

↑ Back to Connectors Index