As part of the common event expression (CEE) effort, a list of field names has been published.
If log records from different log sources have to be correlated or reports have to be generated across different log sources, a common set of field names is needed. Take a firewall log example. Assume that you have two types of firewalls in your environment: Netscreen and PIX. Both devices write different types of log entries. Assume you have a parser that extracts fields from the two logs. Each of the parsers might call fields differently, making it either impossible, or really hard to correlate these two log files. Just think about reporting. How do you find the top source addresses across both logs? These are logs from each of the firewalls:
May 5 17:01:40 184.108.40.206 NOC-FWa: NetScreen device_id=NOC-FWa [Root] system-notification-00257(traffic): start_time="2006-05-05 17:01:40" duration=0 policy_id=52 service=tcp/port:26212 proto=6 src zone=backbone dst zone=noc-mgt action=Deny sent=0 rcvd=0 src=220.127.116.11dst=18.104.22.168 src_port=7000 dst_port=26212
Jan 18 12:43:50 192.168.1.1 %PIX-6-106015: Deny TCP (no connection) from 22.214.171.124/1062 to a.b.c.d/443 flags ACK
If you report on “src”, you won’t get the “from” from the PIX log. We need unified names.
It is not just important to have a common set of names, but also a common understanding of what individual fields mean. What is the semantics of a field? For example, how do you measure a duration? In seconds? Hours? Days? What is a destination host? Is it fully qualified or just the host name itself? The field list, which can be found in this post: CEE Fields List is a first step towards standardizing this.
Note that, for example, ArcSight’s CEF publishes a dictionary along with their log syntax. The CEE field list can be used to standardize the names across various log formats and can hopefully substitute and expand ArcSight’s dictionary.
By Raffael Marty