Introduction
The tables cef0.cisco.*
identify events in CEF format generated by Cisco.
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 | Devo tables |
---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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.
Table structure
These are the fields displayed in these tables:
cef0.cisco.firepower
Field | Type | Source field name | Extra fields |
---|---|---|---|
eventdate |
|
| |
hostname |
|
| |
priorityCode |
|
| |
cefTag |
|
| |
cefVersion |
|
| |
embDeviceVendor |
|
| |
embDeviceProduct |
|
| |
deviceVersion |
|
| |
signatureID |
|
| |
name |
|
| |
severity |
|
| |
_cefVer |
|
| |
act |
|
| |
app |
|
| |
cat |
|
| |
c6a2 |
|
| |
c6a3 |
|
| |
cn1Label |
|
| |
cn1 |
|
| |
cn2Label |
|
| |
cn2 |
|
| |
cs1Label |
|
| |
cs1 |
|
| |
cs2Label |
|
| |
cs2 |
|
| |
cs3Label |
|
| |
cs3 |
|
| |
cs4Label |
|
| |
cs4 |
|
| |
cs5Label |
|
| |
cs5 |
|
| |
cs6Label |
|
| |
cs6 |
|
| |
destinationDnsDomain |
|
| |
deviceDirection |
|
| |
deviceExternalId |
|
| |
deviceInboundInterface |
|
| |
deviceOutboundInterface |
|
| |
dst |
|
| |
dpt |
|
| |
dvchost |
|
| |
dvcpid |
|
| |
end |
|
| |
external_id |
|
| |
fileHash |
|
| |
fileType |
|
| |
fname |
|
| |
proto |
|
| |
reason |
|
| |
requestClientApplication |
|
| |
request |
|
| |
rt |
|
| |
src |
|
| |
spt |
|
| |
start |
|
| |
suser |
|
| |
bytesIn |
|
| |
bytesOut |
|
| |
hostchain |
|
| ✓ |
tag |
| cefTag | ✓ |
rawMessage |
|
| ✓ |