Content Comparison

[

...

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 `cef0.forescout.counteract`

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
`cef0.forescoutTechnologies.counteract`	`cef0.forescoutTechnologies.counteract`

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.

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	`timestamp`
rawMessage	`str`	✓
hostchain	`str`	✓
priorityCode	`str`
cefTag	`str`
cefVersion	`str`
embDeviceVendor	`str`
embDeviceProduct	`str`
deviceVersion	`str`
signatureID	`str`
name	`str`
severity	`str`
cs1Label	`str`
cs1	`str`
cs2Label	`str`
cs2	`str`
cs3Label	`str`
cs3	`str`
cs4Label	`str`
cs4	`str`
dhost	`str`
dmac	`str`
dntdom	`str`
dst	`ip4`
duser	`str`
dvchost	`str`
dvc	`ip4`
rt	`timestamp`
tag	`str`	✓	cefTag

Version	Old Version 3	New Version 4
Changes made by	Former user	Former user
Saved on	Dec 22, 2022	Oct 10, 2023

Versions Compared

Key

Introduction

Introduction

Tag structure

How is the data sent to Devo?

Table structure

cef0.forescoutTechnologies.counteract