About the Device
Claroty CTD is a robust solution that delivers comprehensive cybersecurity controls for industrial and government environments. A security platform that provides industrial cyber security solutions with full-spectrum IoT and OT visibility, continuous monitoring and real-time risk insights to protect you from evolving threats.
CTD monitors the network for all five signs of potential threat:
Early indicators of attack, such as abnormal DNS scans or failed login attempts.
The presence of known threat signatures
Behavioral anomalies associated with zero-day attacks, such as atypical communication between assets
Engineering operations associated with advanced persistent threat (APT) activity, such as unexpected process value changes
Any activity or indicator that meets your custom-defined criteria
Device Information
Entity | Particulars |
|---|---|
Vendor Name | Claroty |
Product Name | Continuous Threat Detection (CTD) |
Type of Device | Hosted |
Collection Method
Log Type | Ingestion label | Preferred Logging Protocol - Format | Log collection method |
|---|---|---|---|
Claroty Continuous Threat Detection | CLAROTY_CTD | Syslog - CEF | CyberHub |
Port Requirements
Source | Destination | Port |
|---|---|---|
Claroty Continuous Threat Detection | CyberHub | 6514 (TCP) |
To facilitate secure communication and align with our best practice, we strongly encourage the use of Transport Layer Security (TLS) between your security devices and our Adaptive MxDR platform for event forwarding.
While we understand that TLS support may not be available on all devices, if your devices do support TLS communication, we recommend utilizing port 6514 for seamless integration.
In some cases, the upgraded version of the device might incorporate TLS support without prior notice. If you come across such a scenario or for further assistance in configuring TLS, we kindly ask you to reach out to your dedicated Adaptive MxDR Service Delivery Lead.
Device Configuration
If the user is connected to a CTD Server and configures the Syslog from within that site, the syslog message will be sent from that site and there will not be an option from that site to select the other sites.
If the user is connected to the EMC and defines a new syslog, the message will be forwarded from the EMC Server (and not from the site/s).
To configure Syslog from Claroty CTD Server
Log in to CTD Server with admin credentials.
Navigate to Settings > Integrations > SIEM Syslog
In ADD NEW SYSLOG, uncheck Local as we are sending logs to another target.
Below points are mapped exactly as per the reference screenshot:
From (Site) – Select one or multiple sites (i.e. CTD Servers).
Vendor Name - Other
Message Contents – Select which level to log - Alerts, Baselines, Events, or Health Monitoring. Default is Alerts.
Category - Make category selected as ALL.
Message Format – Select CEF
Server – CyberHub IP Address
Port – 6514
Protocol – TLS
When TLS is chosen, the Syslog message will be sent as an encrypted TCP message with CEF format, with an option to add server authentication by uploading a server certificate.
System URL – Automatically shows the source URL; this field is not editable
Save – Click to commit your entries
In Message Content, select Alerts and in Category, select All.
In Message Content select Events and in Category, select All.
In Message Content, select Health Monitoring and enter the value for Interval a per your requirement.
In Message Content, select Baseline.
Protocol: Displays protocols that exist in the specific environment. Select the protocol/s you want to filter for.
Communication Type: Select your required communication types.
Access Type: Select from the list of available access types.
To configure Syslog from EMC Server
Log in to EMC with admin credentials.
Navigate to Settings > Integrations > SIEM Syslog
Click the + to Create New.
Enter the following Configuration:
To: Uncheck LOCAL because we are sending logs to a remote server
From: Select one or multiple CTD sites or ALL from which you want to send syslog for
Vendor name: Select vendor as Other
Message Contents - Select Alerts, Baselines, Events from Message Contents drop-down and configure recommended settings provided before under CTD server configuration.
Message Format – Select CEF
Server – CyberHub IP Address
Port – 6514
Protocol – TLS:
When TLS is chosen, the Syslog message will be sent as an encrypted TCP message with CEF format, with an option to add server authentication by uploading a server certificate.
System URL – Automatically shows the source URL; this field is not editable and does not need to be configured
Save – Click to commit your entries.
Once Syslog configuration gets done then click to Send a Test Message option to test the Syslog servers those were added.
Integration Parameters
Parameters required from customer for Integration.
Property | Default Value | Description |
|---|---|---|
IP Address | Claroty Continuous Threat Detection interface IP address | Hostname or IP address of the device which forwards logs to the CyberHub |