Tags beginning with
| Table of Contents | ||||
|---|---|---|---|---|
|
Introduction
The tags beginning with edr.cylance
...
identify events generated by Cylance
...
.
...
Valid tags and data tables
...
The full tag has only three must have 4 levels. The first two are fixed as edr and .cylance. The third level identifies the type of the tag identifies the supported Cylance log event type.
...
technology
...
brand
...
type
events sent, and the fourth level indicates the event subtype.
Technology | Brand | Type | Subtype |
|---|---|---|---|
edr | cylance | protect |
|
|
...
optics |
|
These are the valid tags and corresponding data tables that will receive the parsers' data:
Tag | Data table |
|---|---|
edr.cylance.protect.app | edr.cylance.protect.app |
edr.cylance.protect.audit | edr.cylance. |
...
protect.audit |
edr.cylance. |
...
protect.script | edr.cylance.protect.script |
edr.cylance.protect. |
...
device | edr.cylance.protect.device |
edr.cylance.protect.devicecontrol | edr.cylance. |
...
For more information, read more about Devo tags.
Configuration
In Cylance you need to set up a Syslog/SIEM integration in order to forward events to your Devo Relay.
On the relay, you need to define a series of rules that identify the event types by a string found in the source message, then apply the corresponding tag. To prevent further rule processing on events that match a rule, we make sure to select the Stop processing checkbox.
| Info |
|---|
| This conforms to the relay rule Scenario 2: Apply a Devo tag based on data found in the inbound event. |
In the examples below, we use port 13003 but you should use any port that you can dedicate to these events. And this port should be the one you set up Cylance to send the events to.
...
Rule 1: AppControl events
- Source Port → 13003
- Source Message → Event Type: AppControl
- Target Tag → edr.cylance.app
- Check the Stop processing checkbox.
...
...
Rule 2: AuditLog events
- Source Port → 13003
- Source Message → Event Type: AuditLog
- Target Tag → edr.cylance.audit
- Check the Stop processing checkbox.
...
...
Rule 3: Device management events
- Source Port → 13003
- Source Message → Event Type: Device
- Target Tag → edr.cylance.device
- Check the Stop processing checkbox.
...
...
Rule 4: Memory protection events
- Source Port → 13003
- Source Message → Event Type: ExploitAttempt
- Target Tag → edr.cylance.memory
- Check the Stop processing checkbox.
...
...
Rule 5: Script Execution control events
- Source Port → 13003
- Source Message → Event Type: ScriptControl
- Target Tag → edr.cylance.script
- Check the Stop processing checkbox.
...
...
Rule 6: Threat and threat classification events
- Source Port → 13003
- Source Message → Event Type: Threat
- Target Tag → edr.cylance.threat
- Check the Stop processing checkbox.
...
Related articles
...
protect.devicecontrol | |
edr.cylance.protect.threats | edr.cylance.protect.threats |
edr.cylance.protect.memory | edr.cylance.protect.memory |
edr.cylance.optics.process | edr.cylance.optics.process |
edr.cylance.optics.file | edr.cylance.optics.file |
edr.cylance.optics.registry | edr.cylance.optics.registry |
edr.cylance.optics.network | edr.cylance.optics.network |
edr.cylance.optics.memory | edr.cylance.optics.memory |
edr.cylance.optics.dns | edr.cylance.optics.dns |
edr.cylance.optics.log | edr.cylance.optics.log |
edr.cylance.optics.powershell | edr.cylance.optics.powershell |
edr.cylance.optics.wmi | edr.cylance.optics.wmi |
How is the data sent to Devo?
Logs generated by Cylance must be sent to the Devo platform via the Devo Relay to secure communication.
Once your Relay is receiving Syslog messages (in our case through port 13006), the relay will be able to forward these logs to the right Devo tables by configuring the following relay rules:
Log samples
The following are sample logs sent to each of the edr.cylance data tables. Also, find how the information will be parsed in your data table under each sample log.
| Note | ||
|---|---|---|
| ||
Fields marked as Extra in the table below are not shown by default in data tables and need to be explicitly requested in the query. You can find them marked as Extra when you perform a query so they can be easily identified. Learn more about this in Selecting unrevealed columns. |
We've divided the sample logs into 2 different groups:
| Anchor | ||||
|---|---|---|---|---|
|
-
| Anchor | ||||
|---|---|---|---|---|
|
-