Skip Navigation
  1. BlackBerry Docs
  2. Cylance Endpoint Security
  3. Cylance Syslog Guide
  4. CylanceOPTICS detection events
  5. CylanceOPTICS memory-based detection events

CylanceOPTICS
 memory-based detection events

These events occur when a detection event that includes a
macOS
 memory event is triggered (for example, changing an area of memory marked as read/write to execute). Note that some fields will include command line values that can include commas and colons.
BlackBerry
 recommends that you review and test the parsing of these values by your SIEM or syslog server.
Field
Value
Description
Description
[varies]
This is the name of the detection rule that was triggered.
Detection Rule Id
[varies]
This is the unique detection rule ID.
Device Id
[varies]
This is the unique ID of the device.
Device Last Reported Users
[varies]
These are the last reported device users.
Device Name
[varies]
This is the name of the device that the detection event occurred on.
Event Id
[varies]
This is the unique ID of the detection event.
Event Name
OpticsCaeMemoryEvent
This is the detection event involved in a memory event.
Event Received Timestamp
[varies]
This is the timestamp of when the event was received by
CylanceOPTICS
.
Event Timestamp
[varies]
This is the timestamp of the event that occurred on the device.
Event Type
OpticsCaeMemoryEvent
This is the detection event involved a memory event.
Instigating Process Command Line
[varies]
This is the command line that was used to start the instigating process.
Instigating Process File Path
[varies]
This is the file path of the instigating process executable.
Instigating Process ImageFileSha256
[varies]
This is the SHA256 hash of the process that instigated the action.
Instigating Process Name
[varies]
This is the name of the process that instigated the action.
Instigating Process Owner
[varies]
This is the user who owns the process that instigated the action.
Severity
[varies]
The severity of the event:
  • High: A malicious event that requires immediate attention
  • Medium: A suspicious event that should be reviewed
  • Low: An important event that may not be malicious
  • Info: An observed event
Zone Ids
[varies]
This is a list of zone IDs that the device belonged to at the time of the event.
Zone Names
[varies]
These are the zones that the device belongs to.

Example message for memory-based detection events

Event Type: OpticsCaeMemoryEvent, Event Name: OpticsCaeMemoryEvent, Device Name: SECURITYSERVER3, Zone Name: (JeffTesting,Jeff_3.0), Event Id: c4e7d4e1-8739-4996-83a3-19d9ba583882, Severity: Medium, Description: Looking for a protect memory event, Instigating Process Name: AttackTest32.exe, Instigating Process Owner: PENTEST/Administrator, Instigating Process ImageFileSha256: 2762CB5818C67BDD28DFE88FB528EF06B0C1AB5C175E2206B49C85BB8672C2EC, Event Timestamp: 2022-07-21T12:55:02.277Z, Event Received Timestamp: 2022-07-21T12:55:25Z,
Device Last Reported Users: PENTEST\Administrator, Zone Ids: (F568A8A8E401470282C1FE98FDD1703C,161EB91D79D6466A80182CF685FA7CAA), Detection Rule Id: edf530c6-6b0e-4be2-aeb6-d3f8001fce05, Instigating Process Command Line: AttackTest32.exe -p:8000, Instigating Process File Path: c:\users\administrator.pentest\downloads\attacktest\attacktest32.exe, Device Id: e378dacb-9324-453a-b8c6-5a8406952195