This quick start guide will help Accenture Security customers configure Check Point® LEA server to allow log collection from the Log Collection Platform (LCP).
This document includes the following topics:
A list of supported versions is available in the Accenture Security Supported Products List document (Accenture_MSS_Supported_Products_List.xlsx) which can be found at
Accenture Portal - https://mss.accenture.com/PortalNextGen/Reports/Documents
Check Point Firewall (FW), Customer Management Add-on (CMA), and Check Point Log Manager (CLM) all reside
on the same server.
FW, CMA, and CLM reside on different servers.
Two configuration options are available:
Note: The LCP will be configured based on the deployment technique implemented on your network. Please provide the Check Point architecture to the MSS Onboarding team for reference.
|LCP||CMA||18210||Check Point Internal CA Pull Certificate Service|
|LCP||CLM||18184||Check Point OPSEC Log Export API|
To configure the CMA to allow the LCP to collect logs, follow the steps below.
Create a network object for the LCP.
Login to Check Point SmartDashboard as Administrator.
On the SmartDashboard, click the Network Objects icon, right-click Nodes, and then go to Node > Host.
Figure 1-1: The Check Point SmartDashboard.
In the Host Node - General Properties window:
In the Name text box, type the LCP's host name.
In the IPv4 Address text box, type the IP address of the LCP.
Figure 1-2: The Host Node - General Properties window.
Click File > Save.
Create a new OPSEC application on the CMA.
Login to Check Point SmartDashboard as Administrator.
On the bottom-left pane, click the Servers and OPSEC icon, right-click OPSEC Applications and select New OPSEC Application....
Figure 1-3: The Check Point SmartDashboard.
In the OPSEC Application Properties dialog box, on the General tab, do the following:
In the Name text box, specify a name for the OPSEC application.
In the Host drop-down list, select the IP address or hostname of the LCP (created as a network object in configuration step I).
In the Client Entities section, select LEA.
Figure 1-4: The OPSEC application properties dialog box.
In the Secure Internal Communication section, click the Communication button.
In the Communication dialog box, type and confirm the one-time password. This password is the activation key that the LCP uses to establish Secure Internal Communication (SIC).
Figure 1-5: The Communication dialog box.
Make a note of this password.
To initialize SIC, click Initialize.
On the bottom-left pane, click the Servers and OPSEC icon and double-click the newly created OPSEC Application.
On the General tab, in the DN: section, copy the application SIC DN string. For example, CN=symantec-lcp,O=cma1..mssfr8
In the Secure Internal Communication section, click the Communication button. The Trust State text value should be "Initialized but trust not yet established".
Click the LEA Permissions tab, select Show all log fields, and then click OK.
Click Close and then click OK.
Figure 1-6: The Check Point SmartDashboard main screen.
Check the text boxes next to the required Installation Targets and then click OK.
Figure 1-7: The Install policy window.
After successful policy installation, select Policy > Install Database…. When the dialog box appears, click OK.
Figure 1-8: The Install database window.
Note: Both Accept and Deny logs play an important part in the analysis of traffic seen at the firewall. To receive the maximum benefit from a firewall logging to MSS, all rules that make up the installed firewall policy including an Explicit Deny All (also known as Clean-Up ) rule should be configured to log.
|LEA OPSEC Application Name||Custom Value||
Name of the OPSEC application (created in step II).
|LEA OPSEC Application Password||Custom Value||
One-time password/activation key (created in step II).
|LEA Server IP Address||Custom Value||
IP address of the CLM.
|LEA Server Auth Port||18184||
Authentication port on the Check Point LEA server.
|LEA Server Auth Type||
|Authentication type for LEA communication.|
|LEA Server Port||0||
Communication port for the LEA server.
|Cert Server IP Address||Custom Value||IP address of the CMA.|
|LEA Server OPSEC Entity SIC Name||Custom Value||
SIC name of the LEA server. The default value is CN=cp_mgmt,O=(sic_name_of_lea_server).
Note: The SIC name of the LEA server will vary based on the Check Point deployment.
Please refer to the vendor document for the SIC name of the LEA server.
|OPSEC SIC Name||Custom Value||
SIC name of the OPSEC application (created in step II).
|Opsec keep alive(In seconds)||180||Defalut value for Opsec keep alive connection time.|
Copyright © 2020 Accenture. All rights reserved.
Accenture, the Accenture Logo, and DeepSight Intelligence are trademarks or registered trademarks of Accenture in the U.S. and other countries. Other names may be trademarks of their respective owners.
The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation/reverse engineering. No part of this document may be reproduced in any form by any means without prior written authorization of Accenture and its licensors, if any.
THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. ACCENTURE SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.
The Licensed Software and Documentation are deemed to be commercial computer software as defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19 "Commercial Computer Software - Restricted Rights" and DFARS 227.7202, et seq. "Commercial Computer Software and Commercial Computer Software Documentation," as applicable, and any successor regulations, whether delivered by Accenture as on premises or hosted services. Any use, modification, reproduction release, performance, display or disclosure of the Licensed Software and Documentation by the U.S. Government shall be solely in accordance with the terms of this Agreement.