ON THIS PAGE
Integrating Syslog for Check Point Multi-Domain Management (Provider-1)
Syslog Log Source Parameters for Check Point Multi-Domain Management (Provider-1)
Configuring OPSEC for Check Point Multi-Domain Management (Provider-1)
OPSEC/LEA Log Source Pparameters for Check Point Multi-Domain Management (Provider-1)
Check Point Multi-Domain Management (Provider-1) Sample Event Messages
Check Point Multi-Domain Management (Provider-1)
You can configure JSA to integrate with a Check Point Multi-Domain Management (Provider-1) device.
All events from Check Point Multi-Domain Management (Provider-1) are parsed by using the Check Point DSM. You can integrate Check Point Multi-Domain Management (Provider-1) using one of the following methods:
Integrating Syslog for Check Point Multi-Domain Management (Provider-1)
Configuring OPSEC for Check Point Multi-Domain Management (Provider-1)
Depending on your Operating System, the procedures for using the Check Point Multi-Domain Management (Provider-1) device can vary. The following procedures are based on the Check Point SecurePlatform operating system.
Integrating Syslog for Check Point Multi-Domain Management (Provider-1)
This method ensures that the Check Point Multi-Domain Management (Provider-1) DSM for JSA accepts Check Point Multi-Domain Management (Provider-1) events by using syslog.
JSA records all relevant Check Point Multi-Domain Management (Provider-1) events.
Configure syslog on your Check Point Multi-Domain Management (Provider-1) device:
Type the following command to access the console as an expert user:
expert
A password prompt is displayed.
Type your expert console password. Press the Enter key.
Type the following command:
csh
Select the wanted customer logs:
mdsenv <customer name>
Input the following command:
# nohup $FWDIR/bin/fw log -ftn | /usr/bin/logger -p <facility>.<priority> 2>&1 &
Where:
<facility> is a syslog facility, for example, local3.
<priority> is a syslog priority, for example, info.
You are now ready to configure the log source in JSA.
The configuration is complete. The log source is added to JSA as the Check Point Multi-Domain Management Provider-1 syslog events are automatically discovered. Events that are forwarded to JSA are displayed on the Log Activity tab.
Syslog Log Source Parameters for Check Point Multi-Domain Management (Provider-1)
If JSA does not automatically detect the log source, add a Check Point Multi-Domain Management (Provider-1) log source on the JSA Console by using the syslog protocol.
When using the syslog protocol, there are specific parameters that you must use.
The following table describes the parameters that require specific values to collect syslog events from Check Point Multi-Domain Management (Provider-1):
Parameter |
Value |
---|---|
Log Source type |
Check Point |
Protocol Configuration |
Syslog |
Log Source Identifier |
Type the IP address or host name for your Check Point Multi-Domain Management (Provider-1) appliance. |
Configuring OPSEC for Check Point Multi-Domain Management (Provider-1)
This method ensures that the JSA Check Point FireWall-1 DSM accepts Check Point Multi-Domain Management (Provider-1) events by using OPSEC.
In the Check Point Multi-Domain Management (Provider-1) Management Domain GUI (MDG), create a host object that represents the JSA. The leapipe is the connection between the Check Point Multi-Domain Management (Provider-1) and JSA.
To reconfigure the Check Point Multi-Domain Management (Provider-1) SmartCenter (MDG):
To create a host object, open the Check Point SmartDashboard user interface and select Manage >Network Objects >New >Node >Host.
Type the Name, IP address, and write comments if needed.
Click OK.
Select Close.
To create the OPSEC connection, select Manage >Servers and OPSEC Applications >New >OPSEC Application Properties.
Type a Name, and write comments if needed.
The Name that you enter must be different than the name used in Step 2.
From the Host drop-down menu, select the JSA host object that you created.
From Application Properties, select User Defined as the Vendor type.
From Client Entries, select LEA.
Select OK and then Close.
To install the Policy on your firewall, select Policy >Install >OK.
OPSEC/LEA Log Source Pparameters for Check Point Multi-Domain Management (Provider-1)
If JSA does not automatically detect the log source, add a Check Point Multi-Domain Management (Provider-1) log source on the JSA Console by using the OPSEC/LEA protocol
When using the syslog protocol, there are specific parameters that you must use.
The following table describes the parameters that require specific values to collect OPSEC/LEA events from Check Point Multi-Domain Management (Provider-1):
Parameter |
Value |
---|---|
Log Source type |
Check Point |
Protocol Configuration |
OPSEC/LEA |
Log Source Identifier |
Type the IP address for the log source. This value must match the value that you typed in the Server IP parameter. |
Check Point Multi-Domain Management (Provider-1) Sample Event Messages
Use these sample event messages to verify a successful integration with JSA.
Due to formatting issues, paste the message format into a text editor and then remove any carriage return or line feed characters.
Check Point Multi-Domain Management (Provider-1) sample messages when you use the LEEF protocol
Sample 1: The following sample event message shows an informational event that was generated by the clock daemon.
LEEF:2.0|Check Point|Syslog|1.0|Check Point Log|cat=Syslog devTime=1537528801 ifdir=inbound loguid={0x0,0x0,0x0,0x0} origin=172.16.150.106 sequencenum=1 version=5 default_device_message=<78>crond[30156]: (root) CMD (/usr/lib/sa/sa1 1 1) facility=clock daemon syslog_severity=Informational
Sample 2: The following sample event message shows an application control event that contains specific details about the application; such as the category, name, description, ID, and properties of the application. This sample also contains rules that determine who can access the application and the matched category that is matched by the rule base.
LEEF:2.0|Check Point|Application Control|1.0|Allow|cat=Application Control devTime=1393855342 srcPort=35275 sev=8 ifdir=outbound ifname=eth1-05 loguid={0x54f411c8,0x9,0xbd0317ac,0x187a} origin=10.1.76.67 version=1 app_category=Network Protocols app_desc=Telnet is a network protocol used on the Internet or local area networks to provide a bidirectional interactive text-oriented communications facility using a virtual terminal connection. User data is interspersed in-band with Telnet control information in an 8-bit byte oriented data connection over the Transmission Control Protocol (TCP). Supported from: R75. app_id=60095597 app_properties=Allows remote connect, High Risk, Network Protocols app_rule_id={C54A11A6-BDE9-11DF-9B35- C21D241F6A6A} app_rule_name=Any Allow Log app_sig_id=60095597:1 appi_name=Telnet Protocol dst=10.9.240.147 matched_category=Network Protocols origin_sic_name=CN\ \=ny1,O\\=ny..8ye75g product=Application Control proto=6 proxy_src_ip=10.0.36.27 service=50008 src=10.0.36.27