claroty/ctd
| Vendor | Claroty Ltd. | Parsers | ✓ |
| Author | CrowdStrike | Dashboards | ✗ |
| Version | 1.2.1 | Alerts | ✗ |
| Minimum LogScale Version | 1.145.0 | Actions | ✗ |
| Use Cases | IoT/OT SecOps | Scheduled Searches | ✗ |
| Supported Log Formats |
|
| Field | Format | Timezone |
|---|---|---|
| Vendor.ext.CtdRealTime | MMM dd yyyy HH:mm:ss | UTC |
| Vendor.ext.CtdTimeGenerated | MMM dd yyyy HH:mm:ss | UTC |
| ts | yyyy-MM-dd'T'HH:mm:ss'Z' | UTC |
The CTD package allows you to leverage it's syslogs to gain insights on alerts, system health monitoring, events and activity log.
This package provides a parser for Claroty CTD events in JSON format.
Breaking Changes
This update includes parser changes, which means that data ingested after upgrade will not be backwards compatible with logs ingested with the previous version.
Updating to version 1.0.0 or newer will therefore result in issues with existing queries in for example dashboards or alerts created prior to this version.
See CrowdStrike Parsing Standard (CPS) 1.1 for more details on the new parser schema.
Follow the CPS Migration to update your queries to use the fields and tags that are available in data parsed with version 1.0.0.
Configurations and Sending The Logs to LogScale
See Claroty Syslog Specification manual for information on how to send Claroty logs to Falcon LogScale Collector.
Installing the Claroty CTD Package in LogScale
Find the repository where you want to send the CTD logs, or create a new one.
Navigate to your repository in the LogScale interface, click Settings and then on the left.
Click and install the LogScale package for CTD (i.e. claroty/ctd).
When the package has finished installing, click on the left (still under the , see Ingest Tokens).
In the right panel, click to create a new token. Give the token an appropriate name (the name of the server and the name of the server the token is ingesting logs for), and leave the parser unassigned.Aassign the parser claroty-ctd to the Log Collector Configuration as described in the documentation Configuration File Examples.
Before leaving this page, view the ingest token and copy it to your clipboard — to save it temporarily elsewhere.
Now that you have a repository set up in LogScale along with an ingest token you're ready to send logs to LogScale.
Next, configure the Falcon LogScale Collector to ship the logs from your syslog server into LogScale. Follow Log Collector Install Falcon LogScale Collector and Configure Falcon LogScale Collector. Log Collector documentation also provides an example of how you can configure your syslog datasource, see Configuration File Examples.
Verify Data is Arriving in LogScale
Once you have completed the above steps the CTD data should be arriving in your LogScale repository.
You can verify this by doing a simple search to see the CTD events:
#Vendor = "claroty"
| #event.module = "ctd"