cef0.pcysys

[ 1 Introduction ] [ 2 Tag structure ] [ 3 How is the data sent to Devo? ] [ 4 Table structure ]

Introduction

The tags beginning with cef0.pcysys identify events in CEF format generated by Pentera (formerly Pcysys).

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.pcysys.pentera`	`cef0.pcysys.pentera`

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 this table:

cef0.pcysys.pentera

Field	Type	Field transformation	Source field name	Extra fields

Field	Type	Field transformation	Source field name	Extra fields
eventdate	`timestamp`
hostname	`str`
priority_code	`str`
cef_tag	`str`
cef_version	`str`
emb_device_vendor	`str`
emb_device_product	`str`
device_version	`str`
signature_id	`str`
name	`str`
severity	`str`
destination_ip	`ip4`
destination_username	`str`
event_outcome	`str`
source_ip	`ip4`
categories	`str`	`join(categories_array, ',')`	categories_array
duration	`str`
param_dnsserver	`str`	`join(param_dnsserver_array, ',')`	param_dnsserver_array
param_domainname	`str`
param_is_cloud	`str`
param_is_linux_thin_enumeration	`str`
param_is_windows_thin_enumeration	`str`
param_lst	`str`	`join(param_lst_array, ',')`	param_lst_array
param_num_enumeration_threads	`str`
param_run_rdp_enum	`str`
param_run_windows_control_services_port_scan	`str`
pen_tera_user	`str`
task_id	`str`
techniques	`str`		techniques_array
template_name	`str`
type	`str`
hostchain	`str`			✓
tag	`str`		cef_tag	✓
rawMessage	`str`			✓