Check Point Firewall
Check Point Security Gateways are enterprise next-generation firewalls whose logs are collected centrally by a Security Management Server rather than written on each gateway. Beyond connection accept and drop decisions, the software blades layer on threat prevention telemetry (IPS, Anti-Bot, Anti-Virus and Threat Emulation verdicts) plus identity awareness records that attach a user name to traffic, VPN session activity and an audit trail of administrative policy changes. Forwarding that log stream gives the platform the perimeter's view of what connected to what, who it was, and what the gateway decided to do about it.
Device-side setup
Configure the device to forward syslog to the listener described below, following the vendor's own documentation for its syslog export. Nothing has to be built on the platform side beyond installing the template below: it supplies the parser and wires the pipeline.
Syslog configuration
The gateway or management server sends to a syslog listener: either the cloud syslog endpoint or a local collector appliance. The two destinations use different ports. The cloud endpoint has a per-tenant domain and a block of ports allocated to your account: Configuration → Syslog Ports (v1: Platform → Administration → Syslog Ports) shows the domain, the port range, and which protocol listens on which port; read the numbers off that page rather than assuming a standard one. A collector appliance listens on UDP/514 and TCP/514 by default; a TLS listener (usually 6514 for TLS, 7514 for TLS RFC 6587) is one you add on its Syslog Ports tab and open in the collector's firewall, and each of its listeners can carry a Customer Tag that attributes the records arriving on it. See Syslog Import for the protocol options and Syslog Ports for the listener configuration.
Install the Application
- v2 interface
- Classic v1 interface
In the navigation rail, open Applications and click Install Application, then choose Check Point Firewall Syslog from the On-Premise IT category of the Application Catalog.
Go to Platform → Applications → Install Application From Template and choose Check Point Firewall Syslog from the On-Premise IT category.
The template supplies the parser and builds the pipeline: there is no source to add, no processor to attach, and no sink to wire by hand. Both parameters are required:
| Parameter | Notes |
|---|---|
| datalake | Pre-filled managed. |
| datalake index name | Pre-filled Checkpoint. Two applications writing to the same index name in the same lake will collide, and the second one aborts. |
- v2 interface
- Classic v1 interface
Both sit in the collapsed Advanced configuration section (the form has no Configuration section), so click its heading to reach them. The defaults are usually right; change the index name when something else on the platform already writes to Checkpoint.
Click Install Application. The Applications page opens with the notice Default is launching., and the new application is listed with a green Running badge once the pipeline is up.
Both sit in the collapsed Advanced Configurations row below the Parameters heading, which is otherwise empty; expand the row to reach them. The defaults are usually right; change the index name when something else on the platform already writes to Checkpoint.
Press Install. The application then appears in the Installed Applications view, where its badge reads Running once the pipeline is up.
Related
- On-Prem / Syslog: other syslog devices.
- Syslog Import and Syslog Ports: the transport and listener.
- Parser cookbooks: the template ships a working parser, so a cookbook is only needed if you want to customise the parsing; start here if you do.