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: 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 by default on UDP/514, TCP/514, TLS on 6514 and TLS RFC 6587 on 7514, 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. Either TLS listener presents a certificate the sending device has to trust: the Download CA (ca.crt) button on the Syslog Ports page supplies it, and without it the handshake fails with nothing logged on the platform side.
Install the Application
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. |
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.
- No parser cookbook exists yet for Check Point. The template ships a working parser, so one is only needed if you want to customise the parsing; the parser cookbooks are the starting point if you do.