• R80.20

Log Exporter is already integrated in R80.20. There is no need to install in it a dedicated package.

Note: In order to preserve the Log Exporter configuration before upgrading to R80.20, please follow sk127653 - How to backup and restore Log Exporter configuration on upgrade to R80.20

Note: In order to support exporting logs in Splunk format, please install R80.20 Jumbo Hotfix Take 5 and above.

• R80.10

Install this release on a R80.10 Multi-Domain Server, Multi-Domain Log Server, Security Management Server, Log Server or SmartEvent Server.
Note: Log Exporter can be installed on top of R80.10 Jumbo Hotfix Take 56 and above.

Note: It is currently not supported to install the Log Exporter on top of R80.10 With Jumbo HF Take_169. A solution will be provided before the end of month.

Note: This hotfix must be installed after the Jumbo, and will need to be uninstalled to upgrade to a higher Jumbo take, and then reinstalled after the newer Jumbo is in place.



• R77.30

Install this release on a R77.30 Multi-Domain Server, Multi-Domain Log Server, Security Management Server, Log Server or SmartEvent Server.
Note: Log Exporter can be installed on top of R77.30 Jumbo Hotfix Take 292 and above. 

**This hotfix must be installed after the Jumbo, and will need to be uninstalled to upgrade to a higher Jumbo take, and then reinstalled after the newer Jumbo is in place. 

 

Version	Date	CPUSE Online Identifier	CPUSE offline package
R80.10	06 November 2018	Check_Point_R80.10_Log_Exporter_T41_sk122323_FULL.tgz	(TGZ)
R77.30	06 November 2018	Check_Point_R77.30_Log_Exporter_T30_sk122323_FULL.tgz	(TGZ)

Install the hotfix using CPUSE, see sk92449.

Multi-Domain Security Management - Uninstalling the package does not remove the configuration files, in order to uninstall and completely remove all configurations, do the following:

In order to configure a new target for the logs do the following on the log server:

cp_log_export add name <name> [domain-server <domain-server>] target-server <target-server IP address> target-port <target-port> protocol <(udp|tcp)> format <(syslog)|(cef)|(splunk)(generic)> [optional arguments]

• On MDS/MLM: domain-server argument is mandatory, you can use 'mds' as the value for domain-server in order to export mds level audit logs
• This will create a new target directory with the unique name specified in the –n parameter under $EXPORTERDIR/targets/<deployment_name>, and set the target configuration parameters with the connection details: IP Address, port, protocol, format and read-mode.
• The recommended read-mode for splunk format is semi-unified which ensures you will get a complete data.
• Note the above deployment will export the logs in clear text.
• The new log exporter does not start automatically. To start it run: cp_log_export restart

If you wish to send the logs over an encrypted connection, please refer to the "TLS Configuration" section.

Usage

cp_log_export <command-name> [command-arguments]

In order to understand a specific command usage run:
cp_log_export <command-name> help

Commands

Parameters

The only allowed authentication method via TLS is mutual authentication. For mutual authentication log exporter will need the following certificates:

• A pem Certificate Authority (CA) certificate (should contain only the certificate of CA that signed the client/server certificates, not the parent CA).
• A .p12 format client certificate.

If you don’t already have the required certificates, you can follow the procedure below.

The following procedure is an example of creating the required certificates. You have alternative procedures for achieving this.

Important Note: The below openssl commands need to be run on a 3rd party CA server. (Not on the Log Exporter machine)
The commands are not supported on a Check Point Security Management server/MDM server.

Note: CA server needs to be routable from log exporter device.

Create Self Signed CA

Run this in case you don’t already have a trusted CA pem:

1. Generate the root CA key – Do not pass to anyone:

    openssl genrsa -out RootCA.key 2048

2. Generate the root CA pem:

    openssl req -x509 -new -nodes -key RootCA.key -days 2048 -out RootCA.pem

    you will be prompted to provide information regarding the certificate. This information is known as a Distinguished Name (DN). An important field in the DN is the Common Name(CN), which should be the exact Fully Qualified Domain Name (FQDN) of the host that you intend to use the certificate with. Apart from the Common Name all other fields are optional and can be skipped. If you are purchasing an SSL certificate from a certificate authority, it is often required that these additional fields, such as "Organization", accurately reflect your organization's details.

Here is an example of what the prompt will look like:

---

Country Name (2 letter code) [AU]:US

State or Province Name (full name) [Some-State]:New York

Locality Name (eg, city) []:MyCity

Organization Name (eg, company) [Internet Widgits Pty Ltd]:MyCompany

Organizational Unit Name (eg, section) []:MyDepartment

Common Name (e.g. server FQDN or YOUR name) []:www.company.com

Email Address []:

Note: It is recommended to use the device IP address as the Common Name.

Create Client (log_exporter) .p12 Certificate File

1. Generate client key - Do not pass to anyone:

    openssl genrsa -out log_exporter.key 2048

2. Generate client certificate sign request:

    openssl req -new -key log_exporter.key -out log_exporter.csr

3. Sign the certificate using the CA files:

    openssl x509 -req -in log_exporter.csr -CA RootCA.pem -CAkey RootCA.key -CAcreateserial -out log_exporter.crt -days 2048 -sha256

4. Convert to p12 format

    openssl pkcs12 -inkey log_exporter.key -in log_exporter.crt -export -out log_exporter.p12

Note: The challenge phrase used in this conversion is required in the log_exporter TLS configuration.

After creating the required certificates, you should update the security parameters on the Check Point exporting server:

1. If running on MDS/MLM switch to the required domain by running:
    mdsenv <domain server name or ip>

2. Go to the deployment directory:
    cd $EXPORTERDIR/targets/<deployment name>

3. Create a directory for the certificates:
    mkdir certs

4. Copy RootCA.pem, and log_exporter.p12 to certs directory.

   Important: RootCA.key should NOT be published.

5. Give the RootCA.pem and log_exporter.p12 read permissions:
    chmod +r RootCA.pem
    chmod +r log_exporter.p12

6. Update the secured target using:
    cp_log_export set name <name> domain-server <domain-server> encrypted true ca-cert <path_to_CA_pem> client-cert <path_to_p12_certificate> client-secret <challenge_phrase_for _p12>

Create Server (target) Certificate

1. Generate server key – Do not pass to anyone:

    openssl genrsa -out syslogServer.key 2048

2. Generate server certificate sign request:

    openssl req -new -key syslogServer.key -out syslogServer.csr

3. Sign the certificate using the CA files:

    openssl x509 -req -in syslogServer.csr -CA RootCA.pem -CAkey RootCA.key -CAcreateserial -out syslogServer.crt -days 2048 -sha256

After deploying a new instance of log exporter, all related files to that deployment can be found under $EXPORTERDIR/targets/<deployment name>

On an MDS/MLM server, EXPORTERDIR environment variable is per domain, and its value is changed automatically when switching between domain server contexts with the mdsenv command.

Target Configuration XML

The target configuration file, located under each deployment folder: $EXPORTERDIR/targets//targetConfiguration.xml

Note: You must restart the log exporter process for the new setting to take effect.

Listed below are some of the configuration options:

Destination Parameters

Security Parameters

Discussed in more detail in the "TLS Configuration" section.

Source Parameters

Resolver Parameters

Format Parameters

Filters Parameters

The Log Exporter solution supports several filtering options, as detailed in the section above. In this section, we will go over each option.

Filters logs based on blade

In the current release, we have a limited blade related filtering. This functionality will be expanded upon in future releases.

You can filter out firewall connection logs ('Firewall-1 & VPN-1', 'HTTPS Inspection' and 'Security Gateway/Management').

Note: Firewall session logs will still be exported (Generated by tracking a firewall rule by per Session).  

          Limitation: HTTPS inspection logs, Non-rulebase generated Firewall logs & a few Firewall NAT update logs will still be exported.

Format Configuration XML

Body

Header

Field Mapping Configuration XML

Rsyslog

Rsyslog is not configured to use RFC5424 timestamp format by default, therefore you should manually change Rsyslog setting for it to be compliant with Log Exporter output format.

On the syslog server:

1. Open /etc/rsyslog.conf

2. If there’s an uncommented line: “$ActionFileDefaultTemplate RSYSLOG_TraditionalFileFormat”, comment it.

3. Add the following line: $ActionFileDefaultTemplate RSYSLOG_SyslogProtocol23Format

4. Save and close the file.

5.Restart Rsyslog:
  service rsyslog restart

ArcSight

It is recommended by ArcSight to name the certificate 'syslog-ng'

1. Convert the key to p12 format:
    openssl pkcs12 -inkey syslogServer.key -in syslogServer.crt -export -out syslog-ng.p12 -name "syslogng-alias" -password pass:changeit

2. make sure the environment variable ARCSIGHT_HOME to be the connector install directory:

• Run the certificates manager on the Linux KDE console: ARCSIGHT_HOME/current/bin/arcsight agent keytoolgui
• From the File menu open the keystore: $ARCSIGHT_HOME/current/jre/lib/security/cacerts (password "changeit").
• From the menu select "Import Trusted Certificate"
• From the file dialog, select ca.pem and save it.
• Save and close the certificate manager.
• Edit the agent.properties file to enable mutual authentication by:

         vi $ARCSIGHT_HOME//current/user/agent/agent.properties

         1. Change this value to True:

             syslogng.mutual.auth.enabled=false -> true

         2. Add these line to the bottom:

             syslogng.tls.keystore.file=user/agent/syslog-ng.p12

             syslogng.tls.keystore.alias=syslogng-alias

• run /etc/init.d/arc_connector_name restart

Splunk

It is recommended to use Check Point App for Splunk when exporting logs to Splunk server.

For more information about installation and deployment, please see the Check Point App for Splunk User Guide.

In addition, in order to configure an encrypted connection, do the following:

1. Generate server pem file:
    cat syslogServer.crt syslogServer.key RootCA.pem > splunk.pem

2. Update the inputs.conf file on the Splunk server
    vi /opt/splunk/etc/apps/search/local/inputs.conf

    [SSL]
    serverCert = /etc/ssl/my-certs/splunk.pem
    sslPassword = <challenge password>
    requireClientCert = true

    [tcp-ssl://<port>]
    index = <index>

3. Update the server.conf file on the Splunk server
    vi /opt/splunk/etc/system/local/server.conf

    [sslConfig]
    sslRootCAPath = /etc/ssl/my-certs/RootCA.pem

4. Restart Splunk
    /opt/splunk/bin/splunk restart

QRadar

1. On the Authentication Mode field choose "TLS And Client Authentication"

    When using Client Authentication you need to provide the absolute path to the client certificate.

2. Upload the Check Point certificate and private key to QRadar and provide the absolute path to those under the "Provide Certificate" option.

1. Delete OPSEC application object from the GUI, if it is the only use for the OPSEC application, or alternatively remove the LEA client entity from it if it’s not :

2. If this is the only OPSEC LEA client ( otherwise skip this step) - Configure $FWDIR/conf/fwopsec.conf to not allow LEA:
    Comment out those lines:

3. Install the log exporter according to the installation guide above.

1. Uninstall the CPLogToSyslog package using CPUSE. see instructions in sk92449 section 4-C
2. Install the log exporter according to the installation guide above.

If you want to change this environment, you must first consult with your Check Point partner or vendor. This release is built for the specific environment. Upgrades or other changes can overwrite Hotfix functionality and environment customizations.