[
...
| maxLevel | 2 |
|---|---|
| type | flat |
Introduction
The table cef0.forescoutTechnologies.counteract identifies events in CEF format generated by Forescout CounterACT v8.1.Introduction ] [ Tag structure ] [ How is the data sent to Devo? ] [ Table structure ]
Introduction
The tags beginning with cef0.forescounttechnologies identify events in CEF format generated by Forescout.
| Note |
|---|
For version 6.3.4 or before, you might need to query the table |
Tag structure
Events in CEF format don't have a specific tag structure, as explained in in Technologies supported in CEF syslog format. They are always sent to a table with the structure structure cef0.deviceVendor.deviceProduct.
In this case, the valid data tables are:
Tags | Data tables |
|---|---|
|
|
How is the data sent to Devo?
Logs generated by Forescout CounterACT v8.1 are sent to the Devo platform via Relay to secure communication and no rule needs to be specified to effectively perform this data transfer.
CEF data can be sent directly to Devo or by using a relay. To use the CEF default relay rule, send to the relay’s port 13000. Learn more about CEF syslog format and how Devo tags these events in in Technologies supported in CEF syslog format.
Table structure
These are the fields displayed in this table:
cef0.forescoutTechnologies.counteract
Field | Type | Extra field | Source field name |
|---|---|---|---|
eventdate |
| ||
rawMessage |
| ✓ | |
hostchain |
| ✓ | |
priorityCode |
| ||
cefTag |
| ||
cefVersion |
| ||
embDeviceVendor |
| ||
embDeviceProduct |
| ||
deviceVersion |
| ||
signatureID |
| ||
name |
| ||
severity |
| ||
cs1Label |
| ||
cs1 |
| ||
cs2Label |
| ||
cs2 |
| ||
cs3Label |
| ||
cs3 |
| ||
cs4Label |
| ||
cs4 |
| ||
dhost |
| ||
dmac |
| ||
dntdom |
| ||
dst |
| ||
duser |
| ||
dvchost |
| ||
dvc |
| ||
rt |
| ||
tag |
| ✓ | cefTag |