cef0.cybereason
- Juan Tomás Alonso Nieto (Unlicensed)
Introduction
The tables cef0.cybereason.* identify events in CEF format generated by Cybereason services.
Tag structure
Events in CEF format don't have a specific tag structure, as explained in Technologies supported in CEF syslog format. They are always sent to a table with the structure cef0.deviceVendor.deviceProduct.
In this case, the valid data tables are:
| Tag | Data table |
|---|---|
cef0.cybereason.failedLogin | cef0.cybereason.failedLogin |
cef0.cybereason.sensorHealth | cef0.cybereason.sensorHealth |
cef0.cybereason.malop | cef0.cybereason.malop |
cef0.cybereason.malware | cef0.cybereason.malware |
cef0.cybereason.sensorAction | cef0.cybereason.sensorAction |
How is the data sent to Devo?
Learn more about CEF syslog format and how Devo tags these events in Technologies supported in CEF syslog format.
Log samples
The following are sample logs sent to some of the cef0.cybereason tables. Find how the information will be parsed in your data table under each sample log.
Extra columns
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.