/
cef0.arcsight

cef0.arcsight

Introduction

The tags beginning wirthcef0.arcsight identify events in CEF format generated by ArcSight.

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:

Tags

Data tables

Tags

Data tables

cef0.arcsight.arcsight

cef0.arcsight.arcsight

cef0.arcsight.cpmiClient

cef0.arcsight.cpmiClient

cef0.arcsight.firewall

cef0.arcsight.firewall

cef0.arcsight.logger

cef0.arcsight.logger

cef0.arcsight.panOs

cef0.arcsight.panOs

cef0.arcsight.smartdashboard

cef0.arcsight.smartdashboard

cef0.arcsight.smartdefense

cef0.arcsight.smartdefense

cef0.arcsight.smartviewTracker

cef0.arcsight.smartviewTracker

cef0.arcsight.unityone

cef0.arcsight.unityone

cef0.arcsight.vpn1Firewall1

cef0.arcsight.vpn1Firewall1

How is the data sent to Devo?

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 Technologies supported in CEF syslog format.

Table structure

These are the fields displayed in these tables:

Related content

cef0.arcsight.logger
cef0.arcsight.logger
More like this
cef0.fireeye
cef0.fireeye
More like this
cef0.forescoutTechnologies
cef0.forescoutTechnologies
More like this
cef0.stonesoft
cef0.stonesoft
More like this
cef0.anubisnetworks
cef0.anubisnetworks
More like this
cef0.fortinet
cef0.fortinet
More like this