Checkpoint Next Generation Firewall

Monitor Check Point Next Generation Firewall for suspicious activity more efficiently by correlating Checkpoint Next Generation Firewall logs across vendors and correlate firewall data with endpoint data to identify patterns that could be early indicators of an attack.

Breaking Changes

This update includes parser changes, which means that data ingested after upgrade will not be backwards compatible with logs ingested with the previous version.

Updating to version 1.0.0 or newer will therefore result in issues with existing queries in for example dashboards or alerts created prior to this version.

See CrowdStrike Parsing Standard (CPS) 1.0 for more details on the new parser schema.

Follow the CPS Migration to update your queries to use the fields and tags that are available in data parsed with version 1.0.0.

Installing the Package in LogScale

Find the repository where you want to send the Next Generation Firewall logs, or create a new one.

  1. Navigate to your repository in the LogScale interface, click Settings and then Packages on the left.

  2. Click Marketplace and install the LogScale package for Checkpoint (i.e. checkpoint/ngfw).

  3. When the package has finished installing, click Ingest tokens on the left still under the Settings.

  4. In the right panel, click + Add Token to create a new token. Give the token an appropriate name (e.g. the name of the server the token is ingesting logs for), and either leave the parser unassigned (instead of setting the parser in the log collector configuration later on), or assign the checkpoint-ngfw parser to it.

    Ingest token

    Figure 17. Ingest Token

    Before leaving this page, view the ingest token and copy it to your clipboard — to save it temporarily elsewhere.

  5. Now that you have a repository set up in LogScale along with an ingest token you're ready to send events to LogScale.

Configurations and Sending the logs to LogScale

First you need to configure Check Point Log Exporter to send all logs types to the syslog server.

Next, configure the Falcon LogScale Collector to ship the logs from your syslog server into LogScale. Follow LogScale Collector Install LogScale Collector and Configure LogScale Collector. LogScale Collector documentation also provides an example of how you can configure your syslog datasource.

Verify Data is Arriving in LogScale

Once you have completed the above steps the checkpoint data should be arriving in your LogScale repository.

You can verify this by doing a simple search for #Vendor = "checkpoint" | #event.module = "ngfw" to see the events.

Package Contents Explained

This package parses incoming data, and normalizing the data as part of that parsing. The parser normalizes the data to CrowdStrike Parsing Standard (CPS) 1.0 schema based on OpenTelemetry standards, while still preserving the original data.

If you want to search using the original field names and values, you can access those in the fields whose names are prefixed with the word "Vendor". Fields which are not prefixed with "Vendor" are standard fields which are either based on the schema (e.g. source.ip) or on LogScale conventions (e.g. @rawstring).

The fields which the parser currently maps the data to, are chosen based on what seems the most relevant, and will potentially be expanded in the future. But the parser won't necessarily normalize every field that has potential to be normalized.

Event Categorisation

As part of the schema, events are categorized by four different fields:

  • event.category

  • event.kind

  • event.type

  • #event.outcome

event.category is an array, so it needs to be searched like so:

array:contains("event.category[]", value="network")

Normalized Fields

Here are some of the normalized fields which are being set by this parser:

  • dns.* (e.g,, dns.question.type, dns.type)

  • ecs.* (e.g. ecs.version)

  • related.* (e.g. related.ip, related.hosts, related.user)

  • file.* (e.g, file.size, file.inode, file.type, file.hash.sha,

  • destination.* (e.g, destination.nat.ip, destination.packets, destination.nat.port,, destination.ip, destination.port, destination.mac,, destination.geo, destination.bytes, destination.domain)

  • network.* (e.g, network.iana,, network.bytes, network.direction, network.packets, network.transport, network.application)

  • observer.* (e.g, observer.type,, observer.vendor,, observer.product,, observer.mac, observer.version,, observer.ip)

  • rule.* (e.g rule.category,, rule.ruleset, rule.uuid, rule.description,

  • host.* (e.g, host.os.version)

  • os.* (e.g, os.version)

  • vulnerability.* (e.g

  • user.* (e.g,,,

  • user_agent.* (e.g, user_agent.original)

  • process.* (e.g,,,

  • network.* (e.g, network.iana,, network.bytes, network.direction, network.packets, network.transport, network.application)

  • log.* (e.g log.syslog.appname, log.syslog.priority, log.syslog.msgid, log.syslog.procid, log.syslog.hostname, log.syslog.version, log.syslog.structured))

  • server.* (e.g,,,, server.type, server.product, server.ip, server.vendor,, server.version, server.mac)

  • hash.* (e.g hash.sha,

  • service.* (e.g service,name)

  • related.* (e.g. related.ip, related.hosts, related.user)

  • source.* (e.g source.domain,, source.nat.ip,, source.geo, source.packets, source.mac,, source.ip,, source.bytes, source.port, source.nat.port)

  • email.* (e.g email.message,, email.from.address, email.bcc.address,, email.local, email.subject,

  • event.* (e.g event.severity, event.risk, event.outcome, event.kind, event.start, event.type,, event.category, event.module, event.url, event.end, event.action, event.sequence)

Next steps and use cases

You can get actionable insights from your Next Generation Firewall data by hunting for suspicious activity in LogScale using the Searching Data, Dashboards & Widgets or Automation.