Skip to main content

Check Point

Check Point provides hardware and software products for IT security, including network security, endpoint security, cloud security, mobile security, data security and security management. This integration allows you to send Check Point logs to your Logz.io SIEM account.

Configuration on Linux​

Before you begin, you'll need:

Configure Check Point Log Exporter​

Configure your Check Point Log Exporter to send logs to your Filebeat server.

note

For complete details on configuring Log Exporter, see Check Point Log Export from Check Point.

Option 1: Export logs for all domains​

cp_log_export add name logzio_filebeat_exporter \
target-server <<FILEBEAT-IP-ADDRESS>> \
target-port 514 \
protocol udp \
format syslog \
--apply-now

Option 2: Export logs for a specific domain​

cp_log_export add name logzio_filebeat_exporter \
domain-server <<YOUR-DOMAIN>> \
target-server <<FILEBEAT-IP-ADDRESS>> \
target-port 514 \
protocol udp \
format syslog \
--apply-now
note

If you restart the management server, you'll need to run cp_log_export again to restart the exporter.

Download the Logz.io public certificate​

For HTTPS shipping, download the Logz.io public certificate to your certificate authority folder.

sudo curl https://raw.githubusercontent.com/logzio/public-certificates/master/AAACertificateServices.crt --create-dirs -o /etc/pki/tls/certs/COMODORSADomainValidationSecureServerCA.crt

Add UDP traffic as an input​

In the Filebeat configuration file (/etc/filebeat/filebeat.yml), add UDP to the filebeat.inputs section.

Replace <<LOG-SHIPPING-TOKEN>> with the token of the account you want to ship to.

note

Filebeat requires a file extension specified for the log input.

# ...
filebeat.inputs:
- type: udp
  max_message_size: 10MiB
  host: "0.0.0.0:514"

  fields:
    logzio_codec: plain

    # Your Logz.io account token. You can find your token at
    #  https://app.logz.io/#/dashboard/settings/manage-accounts
    token: <<LOG-SHIPPING-TOKEN>>
    type: checkpoint
  fields_under_root: true
  encoding: utf-8
  ignore_older: 3h

If you're running Filebeat 7, paste this code block. Otherwise, you can leave it out.

# ... For Filebeat 7 only ...
filebeat.registry.path: /var/lib/filebeat
processors:
- rename:
    fields:
    - from: "agent"
      to: "filebeat_agent"
    ignore_missing: true
- rename:
    fields:
    - from: "log.file.path"
      to: "source"
    ignore_missing: true

If you're running Filebeat 6, paste this code block.

# ... For Filebeat 6 only ...
registry_file: /var/lib/filebeat/registry

Set Logz.io as the output​

If Logz.io is not an output, add it now. Remove all other outputs.

Replace <<LISTENER-HOST>> with the host for your region. 

# ...
output.logstash:
  hosts: ["<<LISTENER-HOST>>:5015"]
  ssl:
    certificate_authorities: ['/etc/pki/tls/certs/COMODORSADomainValidationSecureServerCA.crt']

Start Filebeat​

Start or restart Filebeat for the changes to take effect.

Check Logz.io for your logs​

Give your logs some time to get from your system to ours, and then open Open Search Dashboards.

If you still don't see your logs, see Filebeat troubleshooting.

Configuration on Windows​

Before you begin, you'll need:

note

While support for Filebeat 6.3 and later versions is available, Logz.io recommends that you use the latest stable version

Configure Check Point Log Exporter​

Configure your Check Point Log Exporter to send logs to your Filebeat server.

note

For complete details on configuring Log Exporter, see Check Point Log Export from Check Point.

Option 1: Export logs for all domains​

cp_log_export add name logzio_filebeat_exporter \
target-server <<FILEBEAT-IP-ADDRESS>> \
target-port 514 \
protocol udp \
format syslog \
--apply-now

Option 2: Export logs for a specific domain​

cp_log_export add name logzio_filebeat_exporter \
domain-server <<YOUR-DOMAIN>> \
target-server <<FILEBEAT-IP-ADDRESS>> \
target-port 514 \
protocol udp \
format syslog \
--apply-now
note

If you restart the management server, you'll need to run cp_log_export again to restart the exporter.

Download the Logz.io public certificate​

For HTTPS shipping, download the Logz.io public certificate to your certificate authority folder.

sudo curl https://raw.githubusercontent.com/logzio/public-certificates/master/AAACertificateServices.crt --create-dirs -o /etc/pki/tls/certs/COMODORSADomainValidationSecureServerCA.crt

Download the Logz.io public certificate​

For HTTPS shipping, download the Logz.io public certificate to your certificate authority folder.

Download the Logz.io public certificate to C:\ProgramData\Filebeat\Logzio.crt on your machine.

Configure Filebeat using the dedicated Logz.io configuration wizard​

note

Filebeat requires a file extension specified for the log input.

Log in to Logz.io and navigate to the Filebeat log shipping page.

Adding log sources to the configuration file​

  • Select your operating system - Linux or Windows.
  • Specify the full log Path.
  • Select a log Type from the list or select Other to create and specify a custom log type.
  • Select the log format - Plaintext or Json.
  • (Optional) Enable the Multiline option if your log messages span multiple lines. You’ll need to give a regex that identifies the beginning line of each log.
  • (Optional) Add a custom field. Click + Add a field to add additional fields.
note

The wizard makes it simple to add multiple log types to a single configuration file. So to add additional sources, click + Add a log type to fill in the details for another log type. Repeat as necessary.

Filebeat 8.1+​

If you're running Filebeat 8.1+, there are some adjustment you need to make in the config file:

  1. Change type of the filebeat.inputs to filestream instead of logs:
filebeat.inputs:
- type: filestream
  paths:
    - /var/log/*.log
  1. To configure multiline nest the multiline settings under parsers:
- type: filestream
  paths:
    - /var/log/*.log
  parsers:
  - multiline:
      type: pattern
      pattern: '^\d{4}-'
      negate: true
      match: after

Download and validate confiuration​

When you're done adding your sources, click Make the config file to download it.

You can compare it to our sample configuration if you have questions.

Validate the file using a YAML validator tool, such as (Yamllint.com.

Move the configuration file to the Filebeat folder​

Move the configuration file to C:\Program Files\Filebeat\filebeat.yml.

Add UDP traffic as an input​

In the Filebeat configuration file (/etc/filebeat/filebeat.yml), add UDP to the filebeat.inputs section.

Replace <<LOG-SHIPPING-TOKEN>> with the token of the account you want to ship to.

note

Filebeat requires a file extension specified for the log input.

# ...
filebeat.inputs:
- type: udp
  max_message_size: 10MiB
  host: "0.0.0.0:514"

  fields:
    logzio_codec: plain

    # Your Logz.io account token. You can find your token at
    #  https://app.logz.io/#/dashboard/settings/manage-accounts
    token: <<LOG-SHIPPING-TOKEN>>
    type: checkpoint
  fields_under_root: true
  encoding: utf-8
  ignore_older: 3h

If you're running Filebeat 7, paste this code block. Otherwise, you can leave it out.

# ... For Filebeat 7 only ...
filebeat.registry.path: C:\ProgramData\filebeat\registry
processors:
- rename:
    fields:
    - from: "agent"
      to: "filebeat_agent"
    ignore_missing: true
- rename:
    fields:
    - from: "log.file.path"
      to: "source"
    ignore_missing: true

If you're running Filebeat 6, paste this code block.

# ... For Filebeat 6 only ...
registry_file: C:\ProgramData\filebeat\registry

Set Logz.io as the output​

If Logz.io is not an output, add it now. Remove all other outputs.

Replace <<LISTENER-HOST>> with the host for your region. The required port depends whether HTTP or HTTPS is used: HTTP = 8070, HTTPS = 8071. 

# ...
output.logstash:
  hosts: ["<<LISTENER-HOST>>:5015"]
  ssl:
    certificate_authorities: ['C:\ProgramData\Filebeat\Logzio.crt']

Restart Filebeat​

PS C:\Program Files\Filebeat> Restart-Service filebeat

Check Logz.io for your logs​

Give your logs some time to get from your system to ours, and then open Open Search Dashboards.

If you still don't see your logs, see Filebeat's troubleshooting guide.