The Check Point Log Exporter parser can parse Check Point log messages.

The messages of these devices often do not completely comply with the syslog RFCs, making them difficult to parse. The checkpoint-parser() of syslog-ng OSE solves this problem, and can separate these log messages to name-value pairs, extracting also the Cisco-specific values, for example, the mnemonic. For details on using value-pairs in syslog-ng OSE see Structuring macros, metadata, and other value-pairs.

The parser can parse messages in the following formats:

<PRI><VERSION> <YYYY-MM-DD> <HH-MM-SS> <PROGRAM> <PID> <MSGID> - [key1:value1; key2:value2; … ]

For example:

<134>1 2018-03-21 17:25:25 MDS-72 CheckPoint 13752 - [action:”Update”; flags:”150784”; ifdir:”inbound”; logid:”160571424”; loguid:”{0x5ab27965,0x0,0x5b20a8c0,0x7d5707b6}”;]

Splunk format:

time=1557767758 hostname=r80test product=Firewall layer_name=Network layer_uuid=c0264a80-1832-4fce-8a90-d0849dc4ba33 match_id=1 parent_rule=0 rule_action=Accept rule_uid=4420bdc0-19f3-4a3e-8954-03b742cd3aee action=Accept ifdir=inbound ifname=eth0 logid=0 loguid={0x5cd9a64e,0x0,0x5060a8c0,0xc0000001} origin=192.168.96.80 originsicname=cn=cp_mgmt,o=r80test..ymydp2 sequencenum=1 time=1557767758 version=5 dst=192.168.96.80 inzone=Internal outzone=Local proto=6 s_port=63945 service=443 service_id=https src=192.168.96.27

If you find a message that the checkpoint-parser() cannot properly parse, contact Support, so we can improve the parser.

By default, the Check Point-specific fields are extracted into name-value pairs prefixed with .checkpoint. For example, the action in the previous message becomes ${.checkpoint.action}. You can change the prefix using the prefix option of the parser.

Declaration

@version: 3.38
@include "scl.conf"
log {
    source { network(flags(no-parse)); };
    parser { checkpoint-parser(); };
    destination { ... };
};

Note that the parser expects that the entire incorrectly formatted syslog message (starting with its <PRI> value) is in ${MSG}, which you can achieve by using flags(no-parse) on the input driver.

The checkpoint-parser() is actually a reusable configuration snippet configured to parse Check Point messages. For details on using or writing such configuration snippets, see Reusing configuration blocks.
You can find the source of the Check Point configuration snippet on GitHub.

prefix()

Synopsis: prefix()

Description: Insert a prefix before the name part of the parsed name-value pairs to help further processing. For example:

  • To insert the my-parsed-data. prefix, use the prefix(my-parsed-data.) option.

  • To refer to a particular data that has a prefix, use the prefix in the name of the macro, for example, ${my-parsed-data.name}.

  • If you forward the parsed messages using the IETF-syslog protocol, you can insert all the parsed data into the SDATA part of the message using the prefix(.SDATA.my-parsed-data.) option.

Names starting with a dot (for example, .example) are reserved for use by syslog-ng OSE. If you use such a macro name as the name of a parsed value, it will attempt to replace the original value of the macro (note that only soft macros can be overwritten, see Hard versus soft macros. To avoid such problems, use a prefix when naming the parsed values, for example, prefix(my-parsed-data.)

By default, checkpoint-parser() uses the .checkpoint. prefix. To modify it, use the following format:

parser {
    checkpoint-parser(prefix("myprefix."));
};

Updated: