CP R81 Quantum SecurityGateway AdminGuide

27 October 2023
QUANTUM SECURITY
GATEWAY
R81
Administration Guide
Check Point Copyright Notice
© 2020 - 2023 Check Point Software Technologies Ltd.
All rights reserved. This product and related documentation are protected by copyright and distributed under
licensing restricting their use, copying, distribution, and decompilation. No part of this product or related
documentation may be reproduced in any form or by any means without prior written authorization of Check
Point. While every precaution has been taken in the preparation of this book, Check Point assumes no
responsibility for errors or omissions. This publication and features described herein are subject to change
without notice.
RESTRICTED RIGHTS LEGEND:

Use, duplication, or disclosure by the government is subject to restrictions as set forth in subparagraph (c)
(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 and FAR
52.227-19.
TRADEMARKS:
Refer to the Copyright page for a list of our trademarks.
Refer to the Third Party copyright notices for a list of relevant copyrights and third-party licenses.
Important Information
Latest Software
We recommend that you install the most recent software release to stay up-to-date with the
latest functional improvements, stability fixes, security enhancements and protection against
new and evolving attacks.
Certifications
For third party independent certification of Check Point products, see the Check Point
Certifications page.
Check Point R81

For more about this release, see the R81 home page.
Latest Version of this Document in English

Open the latest version of this document in a Web browser.
Download the latest version of this document in PDF format.
Feedback
Check Point is engaged in a continuous effort to improve its documentation.
Please help us by sending your comments.
Quantum Security Gateway R81 Administration Guide | 3

Revision History
Date Description
26 October Updated:
2023
n "Command Line Reference" on page 164 - removed all commands from this chapter
(refer to the R81 CLI Reference Guide)
23 October Updated:
2022
n "Generic Workflow for HSM" on page 50
n "Working with FutureX HSM" on page 67
n "Disabling Communication from the Security Gateway to the HSM Server" on
page 81
n "SecureXL Kernel Parameters" on page 190
n "Kernel Debug Procedure" on page 215
n "Kernel Debug Modules and Debug Flags" on page 224
14 July Updated:
2021
n "Controlling ISP Redundancy from CLI" on page 117
17 April Updated:
2021
n "Firewall Kernel Parameters" on page 167
13 October First release of this document

2020

Table of Contents
Table of Contents
Check Point Quantum Security Gateway Solution 10
Security Policy 11
Access Control Policy 11
Threat Prevention Policy 15
HTTPS Inspection Policy 16
Data Loss Prevention Policy 17
Geo Policy 18
Mobile Access Policy 19
Firewall Software Blade 20
IPsec VPN Software Blade 21
Remote Access VPN 22
Threat Prevention 23
Anti-Bot Software Blade 24
Anti-Virus Software Blade 25
Threat Extraction Software Blade 26
Threat Emulation Software Blade 27
Mail Transfer Agent (MTA) 28
IPS Software Blade 29
Identity Awareness Software Blade 30
Content Awareness Software Blade 31
Mobile Access Software Blade 32
Application Control Software Blade 33
URL Filtering Software Blade 34
Data Loss Prevention Software Blade 35
Anti-Spam & Email Security Software Blade 36
UserCheck 37
ClusterXL Software Blade 38
QoS Software Blade 39
VSX 40
Example Physical Network Topology 40
Example VSX Virtual Network Topology 41
SecureXL 42
CoreXL 43

Table of Contents
Multi-Queue 44
ICAP 45
HTTPS Inspection 46
HTTP/HTTPS Proxy 47
Hardware Security Module (HSM) 48
Why Use an HSM? 48
The Check Point Environment with an HSM 49
Generic Workflow for HSM 50
Workflow for Configuring a Check Point Security Gateway to Work with HSM 50
Workflow for Configuring an HSM Client Workstation 54
Working with Gemalto HSM 55
Configuration Steps 55
Additional Actions for a Gemalto HSM Server 65
Working with FutureX HSM 67
Prerequisites 67
Disabling Communication from the Security Gateway to the HSM Server 81
Monitoring HTTPS Inspection When Security Gateway Works with HSM 82
Monitoring HTTPS Inspection with HSM in SmartConsole Logs 83
Monitoring HTTPS Inspection with HSM over SNMP 87
Monitoring HTTPS Inspection with HSM in CLI 96
ISP Redundancy on a Security Gateway 104
Introduction 104
ISP Redundancy Modes 108
Outgoing Connections 109
Incoming Connections 110
Configuring ISP Redundancy on a Security Gateway 111
ISP Redundancy and VPN 116
Controlling ISP Redundancy from CLI 117
Force ISP Link State 117
The ISP Redundancy Script 117
Mirror and Decrypt 118
Mirror and Decrypt Requirements 120
Configuring Mirror and Decrypt in Gateway mode 121
Preparing the Security Gateway or each Cluster Member 122

Table of Contents
Configuring Mirror and Decrypt in SmartConsole for Gateway Mode 123

Configuring Mirror and Decrypt in VSX mode 128
Preparing the VSX Gateway or each VSX Cluster Member 131
Configuring Mirror and Decrypt in SmartConsole for One Virtual System 132
Configuring Mirror and Decrypt in SmartConsole for Several Virtual Systems 137
Mirror and Decrypt Logs 142
ConnectControl - Server Load Balancing 143
ConnectControl Packet Flow 143
Configuring ConnectControl 144
Monitoring Software Blade 148
Cloud Security 149
Advanced Routing 150
SNMP 151
Deploying a Single Security Gateway in Monitor Mode 152
Introduction to Monitor Mode 152
Example Topology for Monitor Mode 153
For More About Monitor Mode 153
Deploying a Single Security Gateway or ClusterXL in Bridge Mode 154
Introduction to Bridge Mode 154
Example Topology for a single Security Gateway in Bridge Mode 155
For More About Bridge Mode 155
Security Before Firewall Activation 156
Boot Security 157
The Initial Policy 162
Troubleshooting: Cannot Complete Reboot 163
Command Line Reference 164
Working with Kernel Parameters on Security Gateway 165
Introduction to Kernel Parameters 166
Firewall Kernel Parameters 167
Working with Integer Kernel Parameters 168
Working with String Kernel Parameters 177
SecureXL Kernel Parameters 190
Working with Integer Kernel Parameters 191
Working with String Kernel Parameters 196
Kernel Debug on Security Gateway 202

Table of Contents
Kernel Debug Syntax 203

Kernel Debug Filters 210
Kernel Debug Procedure 215
Kernel Debug Procedure with Connection Life Cycle 219
Kernel Debug Modules and Debug Flags 224
Module 'accel_apps' (Accelerated Applications) 226
Module 'accel_pm_mgr' (Accelerated Pattern Match Manager) 227
Module 'APPI' (Application Control Inspection) 228
Module 'BOA' (Boolean Analyzer for Web Intelligence) 230
Module 'CI' (Content Inspection) 231
Module 'cluster' (ClusterXL) 233
Module 'cmi_loader' (Context Management Interface / Infrastructure Loader) 236
Module 'CPAS' (Check Point Active Streaming) 238
Module 'cpcode' (Data Loss Prevention - CPcode) 239
Module 'CPSSH' (SSH Inspection) 240
Module 'crypto' (SSL Inspection) 242
Module 'dlpda' (Data Loss Prevention - Download Agent for Content Awareness) 243
Module 'dlpk' (Data Loss Prevention - Kernel Space) 245
Module 'dlpuk' (Data Loss Prevention - User Space) 246
Module 'DOMO' (Domain Objects) 247
Module 'fg' (FloodGate-1 - QoS) 248
Module 'FILE_SECURITY' (File Inspection) 250
Module 'FILEAPP' (File Application) 251
Module 'fw' (Firewall) 252
Module 'gtp' (GPRS Tunneling Protocol) 258
Module 'h323' (VoIP H.323) 260
Module 'ICAP_CLIENT' (Internet Content Adaptation Protocol Client) 261
Module 'IDAPI' (Identity Awareness API) 263
Module 'kiss' (Kernel Infrastructure) 264
Module 'kissflow' (Kernel Infrastructure Flow) 267
Module 'MALWARE' (Threat Prevention) 268
Module 'multik' (Multi-Kernel Inspection - CoreXL) 269
Module 'MUX' (Multiplexer for Applications Traffic) 271
Module 'NRB' (Next Rule Base) 273
Module 'PSL' (Passive Streaming Library) 275

Table of Contents
Module 'RAD_KERNEL' (Resource Advisor - Kernel Space) 276

Module 'RTM' (Real Time Monitoring) 277
Module 'seqvalid' (TCP Sequence Validator and Translator) 279
Module 'SFT' (Stream File Type) 280
Module 'SGEN' (Struct Generator) 281
Module 'synatk' (Accelerated SYN Defender) 282
Module 'TPUTILS' (Threat Prevention Utilities) 283
Module 'UC' (UserCheck) 284
Module 'UP' (Unified Policy) 285
Module 'upconv' (Unified Policy Conversion) 287
Module 'UPIS' (Unified Policy Infrastructure) 288
Module 'VPN' (Site-to-Site VPN and Remote Access VPN) 290
Module 'WS' (Web Intelligence) 293
Module 'WS_SIP' (Web Intelligence VoIP SIP Parser) 296
Module 'WSIS' (Web Intelligence Infrastructure) 298
Glossary 299

Check Point Quantum Security Gateway Solution
Check Point Quantum Security

Gateway Solution
Item Description
1 SmartConsole
2 Security Management Server
3 Internet and external networks
4 Security Gateway (or Cluster)
5 Internal network
These are the primary components of a Check Point Firewall solution:

n Security Gateway (or Cluster) - The engine that enforces the organization's security policy, is an
entry point to the LAN, and is managed by the Security Management Server.
n Security Management Server- The application that manages, stores, and distributes the security
policy to Security Gateways.
n SmartConsole - A Check Point GUI application that manages security policies, monitor products and
events, install updates, provision new devices and appliances, and manage a multi-domain
environment.
Notes:
n For information about Cluster, see the R81 ClusterXL Administration Guide.
n For information about Security Management Server and SmartConsole, see the R81
Security Management Administration Guide.

Security Policy
Security Policy
In This Section:
Access Control Policy 11

Threat Prevention Policy 15
HTTPS Inspection Policy 16
Data Loss Prevention Policy 17
Geo Policy 18
Mobile Access Policy 19
Security Policy is a collection of rules and settings that control network traffic and enforce organization
guidelines for data protection and access to resources with packet inspection.
Check Point solution provides several types of Security Policies.
Access Control Policy

Description
Access Control Policy consists of these parts:

Security Policy
n Access Control Rule Base
For more information, see the R81 Security Management Administration Guide.
In addition, see sk120964 - ATRG: Unified Policy.
Contains unified simple and granular rules to control access from specified sources to specified
destinations over specified protocols.
If you enable Identity Awareness Software Blade on your Security Gateways, you can also use
Access Role objects as the source and destination in a rule. This lets you easily make rules for
individuals or different groups of users.
How to get there:

1. Connect with SmartConsole to the Management Server.
2. From the left navigation panel, click Security Policies.
3. In the Access Control section, click Policy.
Rule structure:
Services
Nam Sourc Destinat & Actio Tim Insta
No VPN Track
e e ion Applicati n e ll On
ons
# Your Specific Specific Specific or Specific or All Accept Any Log Policy
Rule Source Destination All VPN Service objects or or (with Target
Name objects objects Communit Specific or All Drop Specifi Account s
ies Application or c Time ing)
objects Reject object or
or Alert
User or
Auth None
or
Client
Auth

Security Policy
n NAT Rule Base
Contains automatic and manual rules for Network Address Translation (NAT).
How to get there:

3. In the Access Control section, click NAT.
Rule structure:
Origin Origin Translat Translat

Original Translat
al al ed ed Insta Comme
No Destinat ed
Sourc Servic Destinat Service ll On nts
ion Source
e es ion s
Automatic Generated Rules
NAT Rules for X (Y-Z)
# Specific Specific Specific or = Original = Original = Original Policy Your

Source Destination All Service or or or Targe Comment
objects objects objects Specific Specific Specific ts
object object object or
Specific
Security
Gatewa
y and
Cluster
objects

Security Policy
n Desktop Rule Base
For more information, see the SmartDashboard Help (press F1).
Prerequisites:
1. In the Security Gateway (Cluster) object, enable the IPsec VPN and the Policy Server
Software Blades.
2. In the Policy Package, enable the Desktop Security.
This policy is installed on the Security Management Server. Remote Access Clients download
this policy when a VPN Site update is performed. Once downloaded, this policy determines
access control on the Remote Access Client machines.
The Desktop Policy consists of two Rule Bases:

l Inbound Rules - Control connections directed at the client machine
l Outbound Rules - Control connections initiated by the client machine
How to get there:

3. In the Access Control section, click Desktop.
4. Click Open Desktop Policy in SmartDashboard.
5. From the top, click the Desktop tab.
Rule structure:
No Source Desktop Service Action Track Comment
# Any All Users@Any Any Accept None Your Comment

or or or or or
Specific Source Specific User Group Specific Service Block Log
objects objects objects or or
Encrypt Alert

Security Policy
Threat Prevention Policy

Description
For more information, see the R81 Threat Prevention Administration Guide.
Determines how the system inspects connections for bots and viruses. The primary component of the
policy is the Rule Base. The rules use the Malware database and network objects.
If you enable Identity Awareness Software Blade on your Security Gateways, you can also use Access
Role objects as the scope in a rule. This lets you easily make rules for individuals or different groups of
users.
How to get there:

3. In the Threat Prevention section, click Policy.
Rule structure:
Protecti
Protec on/ Inst
N Na Sour Destina Servic Actio Comme
ted Site/ Track all
o me ce tion es n nts
Scope File/ On
Blade
# Your Specific Specific Specific N/A Any Basic None Polic Your
Rule objects Source Destination (or your or or or y Comment
Name objects objects specific Specific Optimi Log Targe
objects in an Service zed or ts
exception objects or Alert or
rule) Strict In Specifi
or addition: c
Your Packet Securit
Profile Captur y
e Gatew
Forens ay and
ics Cluster
objects

Security Policy
HTTPS Inspection Policy

Description
Lets you inspect the HTTP / HTTPS traffic on these Software Blades:
n Anti-Bot
n Anti-Virus
n Application Control
n Content Awareness (Data Awareness)
n Data Loss Prevention
n IPS
n Threat Emulation
n URL Filtering
Security Gateways cannot inspect HTTPS traffic because it is encrypted. You can enable the HTTPS
Inspection feature to let the Security Gateways create new SSL connections with the external site or
server. The Security Gateways are then able to decrypt and inspect HTTPS traffic that uses the new SSL
connections.
How to get there:

3. In the HTTPS Inspection section, click Policy.
Note - In addition, in the HTTPS Tools section, click Additional Settings.
Rule structure:
Catego
ry/
Inst
N Na Sour Destin Servi Custo Acti Tra Bla Certifi Comm
all
o me ce ation ces m on ck de cate ent
On
Applic
ation
# Your Any APPI_ TLS Any Inspe None All Polic Outbound Your
Rule global_ default or ct or or y TLS Certific Comment
Name obj_ service Specific or Log Specifi Targe ate
Internet s objects Bypas or c ts or
or or s Alert Blade or Your
Specific Specific Specifi Certificate
Destination Service c for Inbound
objects objects Securit Inspection
y
Gatew
ay and
Cluster
objects

Security Policy
Data Loss Prevention Policy

Description
For more information, see the R81 Data Loss Prevention Administration Guide.
Prevents unintentional data leaks by catching protected data before it leaves your organization.
How to get there:

2. From the left navigation panel, click Manage & Settings.
3. From the left tree, click Blades.
4. In the Data Loss Prevention section, click Configure in SmartDashboard.
5. From the top, click the Data Loss Prevention tab.
6. From the left tree, click Policy.
Rule structure:
D Desti Exce Tr Ins Ti

Fla Na Sour Prot Acti Sev Cate Com
at natio ption ac tall m
g me ce ocol on erity gory ment
a n s k On e
Category Name(Y-Z)
No Your Spe My Outside Any Shows: Dete Ema Low DLP Any None Your
Flag Rule cific Organi My Org or none ct il or Bla or Comme
or Nam Dat zation or E- or or or Mediu des Specific nt
Foll e a or Specific mail The Info Log m Catego
ow Typ Specific Destinati or number rm or or ry
Up e Source on FTP of User Ale High
or objects objects or exceptio or rt or
Impr HTTP ns added Ask and Criti
ove for this User how cal
Accu rule or to
racy (double- Prev store
click this ent an
cell) or incid
Wate ent
rmar
k

Security Policy
Geo Policy
Description
Creates a policy for traffic to or from specific geographical or political locations.
How to get there:

3. In the Access Control section, click Policy.
4. Follow sk126172 to use Updatable Objects in the Source and Destination columns.
For additional information, see the SmartConsole Online Help (press F1).
Important - From R81, Security Gateways no longer support Geo Policy configured in
SmartConsole > Security Policies view > Shared Policies section > Geo Policy (Known
Limitation PMTR-56212).
Rule structure:
Country Direction Action Track Comments
Specific Country object From and To Country Accept None Your Comment
or or or
From Country Drop Log
or or
To Country Alert

Security Policy
Mobile Access Policy

Description
For more information, see the R81 Mobile Access Administration Guide.
Controls which user groups have access to which applications, when connecting through a Mobile
Access Security Gateway.
How to get there:

2. From the left navigation panel, click Manage & Settings.
3. From the left tree, click Blades.
4. In the Mobile Access section, click Configure in SmartDashboard.
5. From the top, click the Mobile Access tab.
6. From the left tree, click Policy.
Rule structure:
No Users Applications Install On Comment
# All Users Any Any Your Comment

or or or
Specific User objects Specific Custom Application objects Specific Security Gateway objects

Firewall Software Blade
Firewall Software Blade

This is the main Software Blade that enforces the Access Control and NAT policies on Security Gateways
and Cluster Members

IPsec VPN Software Blade
IPsec VPN Software Blade

This Software Blade lets the Security Gateways and Cluster Members encrypt and decrypt traffic to and
from other Security Gateways and clients.
For more information, see:
n R81 Site to Site VPN Administration Guide
n sk104760 - ATRG: VPN Core (requires Advanced access to Check Point Support Center)
n sk108600 - VPN Site-to-Site with 3rd party (requires Advanced access to Check Point Support
Center)
Policy Server Software Blade

This Software Blade lets you configure a Desktop Security Policy for Remote Access Clients.
This policy controls how the Firewall Software Blade on Remote Access Clients inspects the traffic.
n "Security Policy" on page 11 > Section Access Control Policy > Section Desktop Rule Base
n R81 Remote Access VPN Administration Guide

Remote Access VPN
Remote Access VPN

If employees remotely access sensitive information from different locations and devices, system
administrators must make sure that this access does not become a security vulnerability.
n Check Point's Remote Access VPN solutions let you create a VPN tunnel between a remote user and
the internal network.
For more information, see the R81 Remote Access VPN Administration Guide.
n The Mobile Access Software Blade extends the functionality of Remote Access solutions to include
many clients and deployments.
For more information, see the R81 Mobile Access Administration Guide.

Threat Prevention
Threat Prevention
To challenge today's malware landscape, Check Point's comprehensive Threat Prevention solution offers a
multi-layered, pre- and post-infection defense approach and a consolidated platform that enables enterprise
security to detect and block modern malware.
These Software Blades provide Threat Prevention:
n "Anti-Bot Software Blade" on page 24
n "Anti-Virus Software Blade" on page 25
n "Threat Extraction Software Blade" on page 26
n "Threat Emulation Software Blade" on page 27
n "IPS Software Blade" on page 29

Anti-Bot Software Blade
Anti-Bot Software Blade

This Software Blade discovers infections by correlating multiple detection methods:
n Performs post-infection detection of bots on hosts.
n Prevents bot damages by blocking bot C&C (Command and Control) communications.
n Is continuously updated from ThreatCloud, a collaborative network to fight cybercrime.
n R81 Threat Prevention Administration Guide
n sk92264 - ATRG: Anti-Bot and Anti-Virus (requires Advanced access to Check Point Support Center)
In addition, see "UserCheck" on page 37.

Anti-Virus Software Blade
Anti-Virus Software Blade

This Software Blade:
n Performs pre-infection detection and blocking of malware at the Security Gateway (by correlating
multiple detection engines before users are affected).
n Is continuously updated from ThreatCloud.
n sk92264 - ATRG: Anti-Bot and Anti-Virus (requires Advanced access to Check Point Support Center)

Threat Extraction Software Blade
Threat Extraction Software Blade

Part of the SandBlast suite.
n Provides protection against incoming malicious content.
n Removes exploitable content, including active content and embedded objects, reconstructs files to
eliminate potential threats, and promptly delivers sanitized content to users to maintain business flow.
To remove possible threats, creates a safe copy of the file, while the inspects the original file for
potential threats.
n sk114807 - ATRG: Threat Extraction

Threat Emulation Software Blade
Threat Emulation Software Blade

Part of the SandBlast suite.
This Software Blade quickly inspects files and runs them in a virtual sandbox to discover malicious behavior.
Discovered malware is prevented from entering the network.
The emulation service reports and automatically shares the newly identified threat information with other
customers.
n sk114806 - ATRG: Threat Emulation (requires Advanced access to Check Point Support Center)

Mail Transfer Agent (MTA)
Mail Transfer Agent (MTA)

The Threat Emulation Software Blade requires this feature to inspect SMTP traffic.
n sk109699 - ATRG: Mail Transfer Agent (MTA) (requires Advanced access to Check Point Support
Center)

IPS Software Blade
IPS Software Blade

n Delivers complete and proactive intrusion prevention.
n Delivers thousands of signatures, behavioral and preemptive protections.
n Gives another layer of security on top of Check Point Firewall technology.
n Protects both clients and servers, and lets you control the network usage of certain applications.
The hybrid detection engine provides multiple defense layers, which allows it excellent detection and
prevention capabilities of known threats and in many cases future attacks as well. It also allows unparalleled
deployment and configuration flexibility and excellent performance.
n sk95193 - ATRG: IPS (requires Advanced access to Check Point Support Center)

Identity Awareness Software Blade
Identity Awareness Software Blade

Traditionally, firewalls use IP addresses to monitor traffic, and are unaware of the user and computer
identities behind IP addresses. Identity Awareness maps users and computer identities. This lets you
enforce Access Control policy rules and audit data based on identity.
Identity Awareness is an easy to deploy and scalable solution. It works for both Active Directory and non-
Active Directory based networks, and also for employees and guest users.
Identity Awareness uses the Source and Destination IP addresses of network traffic to identify users and
computers.
You can use these elements as matching criteria in the Source and Destination fields of the Access
Control policy rules:
n The identity of users or user groups
n The identity of computers or computer groups
With Identity Awareness, you define policy rules for specified users, who send traffic from specified
computers or from any computer. Likewise, you can create policy rules for any user on specified computers.
Identity Awareness gets identities from the configured identity sources.
n R81 Identity Awareness Administration Guide
n sk86441 - ATRG: Identity Awareness

Content Awareness Software Blade
Content Awareness Software Blade

This Software Blade provides data visibility and enforcement in unified Access Control Policy.
You can set the direction of the data in the Access Control Policy to one of these:
n Download Traffic - Into the organization
n Upload Traffic - Out of the organization
n Any Direction
You can set Data Types in the Access Control Policy to one of these:
n Content Types - Classified by analyzing the file content (for example: PCI - credit card numbers,
International Bank Account Numbers - IBAN)
n File Types - Classified by analyzing the file ID (for example: Viewer File - PDF, Executable file,
Presentation file)
You can select one of these services:
n CheckPointExchangeAgent
n ftp
n http
n https
n HTTP_proxy
n HTTPS_proxy
n smtp
n Squid_NTLM
For more information, see the:

n R81 Security Management Administration Guide
n SmartConsole Online Help
n sk119715 - ATRG: Content Awareness (CTNT) (requires Advanced access to Check Point Support
Center)
Note - Content Awareness and Data Loss Prevention (see "Data Loss Prevention Software
Blade" on page 35) both use Data Types in the Access Control Policy. However, they have
different features and capabilities. They work independently, and the Security Gateway enforces
them separately.

Mobile Access Software Blade
Mobile Access Software Blade

Check Point Mobile Remote Access VPN Software Blade is the safe and easy solution to connect to
corporate applications over the internet with your mobile device or PC. The solution provides enterprise-
grade remote access with both Layer 3 VPN and SSL VPN. It gives you simple, safe and secure connectivity
to your email, calendar, contacts and corporate applications. At the same time, it protects networks and
endpoint computers from threats.
The Mobile Access Portal lets mobile and remote workers connect easily and securely to critical resources
over the internet.
Check Point Mobile Apps enables secure encrypted communication from unmanaged smartphones and
tablets to your corporate resources.
n R81 Mobile Access Administration Guide
n sk104577 - ATRG: Mobile Access Blade

Application Control Software Blade
Application Control Software Blade

This Software Blade detects or blocks traffic for applications:
n Granular Application Control: Identifies, allows, or blocks thousands of applications. This provides
protection against the increasing threat vectors and malware introduced by internet applications.
n Largest application library with AppWiki: Comprehensive application control that uses the industry's
largest application library. It scans for and detects more than 4,500 applications and more than
100,000 Web 2.0 widgets. Check Point database is updated frequently with worldwide Apps and
Widgets.
n sk112249 - Best Practices - Application Control
n sk73220 - ATRG: Application Control (requires Advanced access to Check Point Support Center)

URL Filtering Software Blade
URL Filtering Software Blade

This Software Blade lets you control access to web sites and applications based on their categorization.
n sk92743 - ATRG: URL Filtering (requires Advanced access to Check Point Support Center)

Data Loss Prevention Software Blade
Data Loss Prevention Software

Blade
This Software Blade prevents unintentional data leaks by catching protected data before it leaves your
organization.
This Software Blade identifies, monitors, and protects data transfer through deep content inspection and
analysis of transaction parameters (such as source, destination, data object, and protocol), with a
centralized management framework. In short, DLP detects and prevents the unauthorized transmission of
confidential information.
Note - Data Loss Prevention is also known as Data Leak Prevention, Information Leak Detection
and Prevention, Information Leak Prevention, Content Monitoring and Filtering, and Extrusion
Prevention.
For more information, see the:
n R81 Data Loss Prevention Administration Guide
n SmartConsole Online Help.
n sk73660 - ATRG: Data Loss Prevention (DLP) (requires Advanced access to Check Point Support
Center)
Note - Data Loss Prevention and Content Awareness (see "Content Awareness Software Blade"
on page 31) both use Data Types in the Access Control Policy. However, they have different
features and capabilities. They work independently, and the Security Gateway enforces them
separately.

Anti-Spam & Email Security Software Blade
Anti-Spam & Email Security

Software Blade
This Software Blade enforces Anti-Spam:
n Based on content fingerprint - Identifies spam by analyzing known and emerging distribution
patterns. By avoiding a search for keywords and phrases that might classify a legitimate email as
spam and instead focusing on other message characteristics, this solution offers a high spam
detection rate with a low number of false positives.
n Based on IP Reputation - Blocks known spammers.
n Based on user defined IP addresses and Sender / Domains - Blocks senders identified by either
name, domain, or IP address.
You can configure:
n Directional scanning for SMTP traffic
n Directional scanning for POP3 traffic
n Network exceptions
n List of allowed email senders
n SmartDashboard built-in help

UserCheck
UserCheck
This feature gives users a warning when there is a potential risk of data loss or security violation.
This helps users to prevent security incidents and to learn about the organizational security policy.
These Software Blades require the UserCheck feature:
n "Threat Emulation Software Blade" on page 27
n "Threat Extraction Software Blade" on page 26
n "Anti-Bot Software Blade" on page 24
n "Anti-Virus Software Blade" on page 25
n "Data Loss Prevention Software Blade" on page 35
n "Application Control Software Blade" on page 33
n "URL Filtering Software Blade" on page 34
n The R81 Security Management Administration Guide > Chapter Creating an Access Control Policy >
Section The Columns of the Access Control Rule Base
n sk83700 - How to customize and localize the UserCheck portal

ClusterXL Software Blade
ClusterXL Software Blade

ClusterXL is a Check Point software-based cluster solution for Security Gateway redundancy and Load
Sharing. A ClusterXL Security Cluster contains identical Check Point Security Gateways.
n A High Availability Security Cluster ensures Security Gateway and VPN connection redundancy by
providing transparent failover to a backup Security Gateway in the event of failure.
n A Load Sharing Security Cluster provides reliability and also increases performance, as all members
are active.
Item Description
1 Internal network
2 Switch for internal network
3 Security Gateways with ClusterXL Software Blade
4 Switch for external networks
5 Internet
For more information, see the R81 ClusterXL Administration Guide.

QoS Software Blade
QoS Software Blade

QoS is a policy based bandwidth management solution that lets you:
n Prioritize business-critical traffic, such as ERP, database and Web services traffic, over lower priority
traffic.
n Guarantee bandwidth and control latency for streaming applications, such as Voice over IP (VoIP)
and video conferencing.
n Give guaranteed or priority access to specified employees, even if they are remotely accessing
network resources.
You deploy QoS with the Security Gateway.
QoS is enabled for both encrypted and unencrypted traffic.
Item Description
1 SmartConsole
2 Security Management Server
3 QoS Policy
4 Security Gateway with QoS Software Blade
5 Internet
6 Internal network
QoS leverages the industry's most advanced traffic inspection and bandwidth control technologies. Check
Point patented Stateful Inspection technology captures and dynamically updates detailed state information
on all network traffic. This state information is used to classify traffic by service or application. After traffic
has been classified, QoS applies an innovative, hierarchical, Weighted Fair Queuing (WFQ) algorithm to
accurately control bandwidth allocation.
For more information, see the R81 QoS Administration Guide.

VSX
VSX
Virtual System eXtension product runs several virtual firewalls on the same hardware.
Each Virtual System works as a Security Gateway, typically protecting a specified network. When packets
arrive at the VSX Gateway, it sends traffic to the Virtual System protecting the destination network. The
Virtual System inspects all traffic and allows or rejects it according to rules defined in the security policy.
In order to better understand how virtual networks work, it is important to compare physical network
environments with their virtual (VSX) counterparts. While physical networks consist of many hardware
components, VSX virtual networks reside on a single configurable VSX Gateway or cluster that defines and
protects multiple independent networks, together with their virtual components.
Example Physical Network Topology

In a typical deployment with multiple Security Gateways, each protects a separate network.
Each physical Security Gateway has interfaces to the perimeter router and to the network it protects.
Item Description
1 Internet
2 Router
3 Security Gateways
4 Network

VSX
Example VSX Virtual Network Topology

Deploy one VSX Gateway with four Virtual Systems to protect multiple networks.
Item Description
1 Internet
2 Router
3 VSX Gateway.
Each Virtual System in a VSX environment is a Security Gateway, with the same security and
networking functionality as a physical gateway.
Each handles packet traffic to and from the one network it protects.
4 Warp Links.
Virtual interfaces and network cables connect the Virtual Systems and the Virtual Switch.
5 Virtual Switch.
Connects all the Virtual Systems to the Internet router.
6 Networks
For more information, see the R81 VSX Administration Guide.

SecureXL
SecureXL
This feature accelerates traffic that passes through a Security Gateway.
n R81 Performance Tuning Administration Guide
n sk153832 - ATRG: SecureXL for R80.20 and above (requires Advanced access to Check Point
Support Center)
n sk98348 - Best Practices - Security Gateway Performance

CoreXL
CoreXL
CoreXL is a performance-enhancing technology for Security Gateways on multi-core platforms.
CoreXL makes it possible for the CPU cores to perform multiple tasks concurrently. This enhances the
Security Gateway performance.
CoreXL provides almost linear scalability of performance, according to the number of processing cores on a
single machine. The increase in performance does not require changes to management or to network
topology.
On a Security Gateway with CoreXL enabled, the Firewall kernel is replicated multiple times.
Each replicated copy of the Firewall kernel, or CoreXL Firewall instance, runs on one CPU core.
These CoreXL Firewall instances handle traffic concurrently, and each CoreXL Firewall instance is a
complete and independent Firewall inspection kernel. When CoreXL is enabled, all the Firewall kernel
instances in the Security Gateway process traffic through the same interfaces and apply the same security
policy.
CoreXL Firewall instances work with SecureXL instances.
For more information. see:
n sk98737 - ATRG: CoreXL (requires Advanced access to Check Point Support Center)

Multi-Queue
Multi-Queue
By default, each network interface has one traffic queue handled by one CPU.
You cannot use more CPU cores for acceleration than the number of interfaces handling traffic.
Multi-Queue configures more than one traffic queue for each network interface.
For each interface, more than one CPU core is used for acceleration.
Note - Multi-Queue is applicable only if SecureXL is enabled (this is the default).


ICAP
ICAP
The Internet Content Adaptation Protocol (ICAP) is a lightweight HTTP-like protocol (request and
response protocol), which is used to extend transparent proxy servers. This frees up resources and
standardizes the way in which new features are implemented. ICAP is usually used to implement virus
scanning and content filters in transparent HTTP proxy caches.
The ICAP allows ICAP Clients to pass HTTP / HTTPS messages to ICAP Servers for content adaptation.
The ICAP Server executes its transformation service on these HTTP / HTTPS messages and sends
responses to the ICAP Client, usually with modified HTTP / HTTPS messages. The adapted HTTP / HTTPS
messages can be HTTP / HTTPS requests, or HTTP / HTTPS responses.
You can configure a Check Point Security Gateway as:
n ICAP Client - To send the HTTP / HTTPS messages to ICAP Servers for content adaptation.
n ICAP Server - To perform content adaptation in the HTTP / HTTPS messages received from ICAP
Clients.
n Both ICAP Client and ICAP Server at the same time.
Check Point Security Gateway configured for ICAP can work with third party ICAP devices without changing
the network topology.

HTTPS Inspection
HTTPS Inspection
Lets you inspect the HTTP / HTTPS traffic on these Software Blades:
n Anti-Bot
n Anti-Virus
n Application Control
n Content Awareness (Data Awareness)
n Data Loss Prevention
n IPS
n Threat Emulation
n URL Filtering
Security Gateways cannot inspect HTTPS traffic because it is encrypted. You can enable the HTTPS
Inspection feature to let the Security Gateways create new SSL connections with the external site or server.
The Security Gateways are then able to decrypt and inspect HTTPS traffic that uses the new SSL
connections.
n R81 Threat Prevention Administration Guide > Chapter HTTPS Inspection.
n sk108202 - Best Practices - HTTPS Inspection
n sk65123 - HTTPS Inspection FAQ

HTTP/HTTPS Proxy
HTTP/HTTPS Proxy
You can configure a Security Gateway to act as an HTTP/HTTPS Proxy on your network.
In such configuration, the Security Gateway becomes an intermediary between hosts that communicate with
each other through the Security Gateway. It does not allow a direct connection between these hosts.
Each successful connection creates two different connections:
n One connection between the client in the organization and the proxy (Security Gateway).
n One connection between the proxy (Security Gateway) and the actual destination.
These proxy modes are supported:
n Transparent - All HTTP traffic on specified ports and interfaces is intercepted and processed by the
Proxy code in the Security Gateway. No configuration is required on the clients.
n Non Transparent - All HTTP/HTTPS traffic on specified ports and interfaces is intercepted and
processed by the Proxy code in the Security Gateway. Configuration of the proxy address and port is
required on client machines.
n SmartDashboard built-in help
n sk110013 - How to configure Check Point Security Gateway as HTTP/HTTPS Proxy (requires
Advanced access to Check Point Support Center)
n sk92482 - Performance impact from enabling HTTP/HTTPS Proxy functionality (requires Advanced
access to Check Point Support Center)

Hardware Security Module (HSM)

In This Section:
Why Use an HSM? 48

The Check Point Environment with an HSM 49
Why Use an HSM?

Hardware Security Module (HSM) is a device that stores cryptographic keys.
HSM adds an additional layer of security to the network. HSM is designed to provide dedicated
cryptographic functionality.
When Check Point Security Gateway uses an HSM, the HSM holds these objects for outbound HTTPS
Inspection:
1. The Certificate Authority (CA) certificate (the certificate buffer and the key pair).
The administrator creates the CA certificate and the key pair before you configure the Security
Gateway to work with an HSM.
2. Two to three RSA key pairs for fake certificates.
These keys are created during the initialization of the HTTPS Inspection daemon on the Security
Gateway with 1024-bit, 2048-bit, or 4096-bit length.
You can use these HSM solutions to work with the Check Point Security Gateway:
n Gemalto Luna SP SafeNet HSM
See "Working with Gemalto HSM" on page 55.
n FutureX
See "Working with FutureX HSM" on page 67.
Note - For other HSM vendors that use PKCS#11 API, contact Check Point Solution Center
through a local Check Point Office.

The Check Point Environment with an HSM
Item Description
1 Internal computers that connect to HTTPS web sites through the Check Point Security
Gateway.
2 Check Point Security Gateway with HTTPS Inspection enabled.
3 HTTPS web sites on the Internet.
4 Check Point Security Management Server that manages the Check Point Security Gateway.
5 Interconnecting Network.
6 HSM Server that stores and serves the SSL keys and certificates to the Check Point Security
Gateway.
7 HSM Client workstation used to create a Certificate Authority (CA) certificate on the HSM
Server.
Note - Check Point Security Gateway uses the HSM Server only for outbound HTTPS Inspection.

Generic Workflow for HSM

In This Section:
Workflow for Configuring a Check Point Security Gateway to Work with HSM 50
Workflow for Configuring an HSM Client Workstation 54
This section contains generic workflows for an HSM environment.
Workflow for Configuring a Check Point Security Gateway to

Work with HSM
Follow the steps below on the Security Gateway and Cluster Members that must work with an HSM.
Note - Instructions for specific HSM vendors are located in the corresponding sections.
Generic Step 1 of 3: Configure the HTTPS Inspection to work without the HSM Server
Important:
n In a Cluster, you must configure all the Cluster Members in the same way.
n In a VSX environment, you must perform this step in the context of each Virtual System
(on the VSX Gateway or each VSX Cluster Member).
Step Instructions
1 In SmartConsole, configure the HTTPS Inspection.

See the R81 Security Management Administration Guide > Chapter HTTPS Inspection.
2 On the Security Gateway / each Cluster Member, disable the HSM in the
$FWDIR/conf/hsm_configuration.C file.
a. Connect to the command line.
b. Log in to the Expert mode.
c. Edit the file:
vi $FWDIR/conf/hsm_configuration.C
d. Configure the value "no" for the parameter "enabled":
:enabled ("no")
e. Save the changes in the file and exit the editor.
3 On the Security Gateway / each Cluster Member / Security Group, restart Check Point
services:
cprestart
Important - Traffic does not flow through until the services start.

Step Instructions
4 Make sure that HTTPS Inspection works correctly without the HSM Server:
a. From an internal computer, connect to any HTTPS web site.
b. On the internal computer, in the web browser, you must receive the signed CA
certificate from the Security Gateway (Cluster).
Generic Step 2 of 3: Install and configure the PKCS#11 library supplied by the HSM vendor
Important:
n In a VSX environment, you must perform this step in the context of the VSX Gateway or
each VSX Cluster Member (context of VS 0).
n You must get the HSM Client package from the HSM vendor.
Step Instructions
1 Unpack and install the HSM Client package supplied by the HSM vendor.
2 Transfer the required PKCS#11 library file to the /usr/lib/hsm_client/ directory.

Important - For security reasons, only the root user has permissions to access this
directory.
You must transfer the physical file into this directory. Do not create a symbolic link.
3 Transfer other tools or files supplied by the HSM vendor that are required to configure the
PKCS#11 library.
4 Configure the required connection or trust between with the HSM Server.
5 Optional: Make sure there is a trusted link with the HSM Server that is based on the
PKCS#11 library.
Note - Use the applicable tool supplied by the HSM vendor. You can also examine the
trust with the Check Point command "cpstat").
Generic Step 3 of 3: Configure the HTTPS Inspection to work with the HSM Server for Outbound
HTTPS Inspection
Important:
n In a VSX environment, you must perform this step in the context of each Virtual System
(on the VSX Gateway or each VSX Cluster Member).

Notes:
n In this step, you configure the $FWDIR/conf/hsm_configuration.C file on the
Security Gateway / each Cluster Member.
n After you apply the HSM configuration for the first time, you can get an HSM connection
error.
Most common scenario is when you configure several Security Gateways (Cluster
Members) to use the same HSM Server, and they access it at the same time.
In this case:
a. Run the "cprestart" command on the Security Gateway / Cluster Member /
Security Group that has an HSM connection issue.
In a VSX environment, run this command in the context of the problematic VSX
Virtual System.
b. When you see "HSM on" on the screen, continue to configure the next Security
Gateway, Cluster Member, or VSX Virtual System.
n After any change in the $FWDIR/conf/hsm_configuration.C file, you must do one
of these:
l Fetch the local policy with the "fw fetch local" command.
l In SmartConsole install the policy on the Security Gateway / Cluster / VSX Virtual
System object.
n If the HSM Server is not available when you fetch the local policy or install the policy in
SmartConsole, the HTTPS Inspection cannot inspect the Outbound HTTPS traffic. As a
result, internal computers behind the Security Gateway / Cluster / VSX Virtual System
cannot access HTTPS web sites.
In addition, see "Disabling Communication from the Security Gateway to the HSM
Server" on page 81.
Configuration steps:
Step Instructions
1 Connect to the command line on the Security Gateway / each Cluster Member.
2 Log in to the Expert mode.
3 Back up the $FWDIR/conf/hsm_configuration.C file.
4 Edit the $FWDIR/conf/hsm_configuration.C file.
5 Configure the required values for these attributes

(see the corresponding sections for HSM vendors):
(:enabled ("no") # "yes" / "no"

:hsm_vendor_name ("")
:lib_filename ("")
:CA_cert_public_key_handle (0)
:CA_cert_private_key_handle (0)
:CA_cert_buffer_handle (0)
:token_id ("")
)

Step Instructions
Notes:
n The ":enabled ()" attribute must have the value of either "yes" (to enable the
HSM), or "no" (to disable the HSM).
n The ":hsm_vendor_name ()" attribute must contain the required name of the
HSM vendor.
n The ":lib_filename ()" attribute must contain the name of the PKCS#11 library
of your HSM vendor (located in the /usr/lib/hsm_client/ directory).
n The ":CA_cert_<XXX> ()" attributes must have the required values of handles.
n The ":token_id ()" attribute must contain the password for the partition on the
HSM Server.
Example:
(:enabled ("yes")
:hsm_vendor_name ("FutureX HSM")
:lib_filename ("libfxpkcs11.so")
:token_id ("safest")
)
6 To apply the new configuration, restart all Check Point services with this command:
cprestart
Important - This blocks all traffic until all services restart. In a cluster, this can cause a
failover.
7 Make sure that the Security Gateway / each Cluster Member can connect to the HSM
Server and that HTTPS Inspection is activated successfully on the outbound traffic.
Run this command:
cpstat https_inspection -f all
The output must show:
n HSM partition access (Accessible/Not Accessible): Accessible
n Outbound status (HSM on/HSM off/HSM error): HSM on
For more information, see "Monitoring HTTPS Inspection with HSM in CLI" on page 96.
8 Make that HTTPS Inspection is activated successfully on the outbound traffic:

certificate from the HSM Server.

Workflow for Configuring an HSM Client Workstation

HSM Client workstation is an external computer, on which you install the HSM Client software of your HSM
vendor.
HSM Client workstation can run on Windows, Linux, or other operating system, as required by the HSM
vendor.
You use the HSM Client workstation to:
n Create a CA Certificate on the HSM Server.
Check Point Security Gateways / Cluster Members use this CA Certificate for HTTPS Inspection
when it needs to store and access SSL keys on the HSM Server.
n Manage keys for a fake certificate created by the Check Point Security Gateway / Cluster Members.
Important - You must get the HSM Client package from the HSM vendor.

Working with Gemalto HSM

In This Section:
Additional Actions for a Gemalto HSM Server 65
Configuration Steps
Use this workflow to configure a Check Point Security Gateway / ClusterXL to work with the Gemalto HSM
Server.
Step 1 of 5: Extracting the Gemalto Help Package
Use the Gemalto configuration documents to configure the Gemalto HSM environment.
Step Instructions
1 Download this package:

Gemalto SafeNet HSM Help package
(007-011136-012_Net_HSM_6.2.2_Help_RevA)
Note - Software Subscription or Active Support plan is required to
download this package.
2 Use a Windows-based computer.
3 Extract the Gemalto HSM Help package to some folder.
4 Open the extracted Gemalto HSM Help folder.
5 Double-click the START_HERE.html file.

The Gemalto SafeNet Network HSM 6.2.2 Product Documentation opens.

Step 2 of 5: Configuring the Gemalto HSM Server to Work with Security Gateway / ClusterXL
Use the Gemalto Help documents to install and configure the Gemalto HSM Server.
Step Instructions
1 Install the Gemalto HSM Appliance.

From the Gemalto SafeNet Network HSM 6.2.2 Product Documentation, go to the
Installation Guide > SafeNet Network HSM Hardware Installation.
2 Do the initial configuration of the Gemalto HSM Appliance and the Gemalto HSM Server.
Configuration Guide > follow from [Step 1] to [Step 6].
3 Run the "sysconf recenCert" command in LunaSH to generate a new certificate for the
Gemalto HSM Server (server.pem).
Configuration Guide > [Step 7] Create a trusted link and register Client and Appliance with
each other.
4 Complete the configuration of the Gemalto HSM Server to work with the Check Point
Security Gateway / ClusterXL:
a. Set the applicable partition to be active and auto-activated.
Run these commands in LunaSH:
lunash:> partition showPolicies -partition <Partition
Name>
lunash:> partition changePolicy -partition <Partition

Name> -policy 22 -value 1
lunash:> partition changePolicy -partition <Partition

Name> -policy 23 -value 1
lunash:> partition showPolicies -partition <Partition

Name>
Note - If you do not set the partition to stay auto-activated, the partition does
not stay activated when the machine is shut down for more than two hours.
b. Disable the validation of the client source IP address by NTLS upon an NTLA client
connection.
Run this command in LunaSH:
lunash:> ntls ipcheck disable
Note - This allows the HSM Server to accept traffic from Check Point Cluster
Members that hide this traffic behind a Cluster VIP address, and from a Check
Point Security Gateway hidden behind NAT.

Step 3 of 5: Configuring the Gemalto HSM Client workstation
You use the Gemalto HSM Client workstation to create a CA Certificate on the Gemalto HSM Server.
Check Point Security Gateway / ClusterXL uses this CA Certificate for HTTPS Inspection to store and to
access SSL keys on the Gemalto HSM Server.
Note - You can also use Check Point Security Gateway / ClusterXL with the installed HSM
Client package as an HSM Client workstation.
Step Instructions
1 Get this HSM Client package from the Gemalto vendor:

610-012382-017_SW_Client_HSM_6.2.2_RevA
2 Install a Windows-based or Linux-based computer to use as a Gemalto HSM Client

Workstation.
3 Install the HSM Client package on the computer:

Installation Guide > SafeNet HSM Client Software Installation.
4 Establish a Trust Link between the Gemalto HSM Client Workstation and the Gemalto
HSM Server.
Configuration Guide > [Step 7] Create a trusted link and register Client and Appliance with
each other.
On the Gemalto HSM Client Workstation, run in LunaCM:
lunacm:> clientconfig deploy -c <IP Address of HSM Client
Workstation> -n <IP Address of HSM Server> -par <Partition
Name> -pw <Partition Password>

Step 4 of 5: Creating the CA Certificate on the Gemalto HSM Server
Step Instructions
1 On the Gemalto HSM Client workstation, open a command prompt or a terminal window.
2 Use the "cmu generatekeypair" command to create a key pair.

From the Gemalto SafeNet Network HSM 6.2.2 Product Documentation, go to the Utilities
Reference Guide > Certificate Management Utility (CMU) > cmu generatekeypair.
Example:
# cd /usr/safenet/lunaclient/bin
# ./cmu generatekeypair -modulusBits=2048 -publicExponent=65537
-labelPublic="CAPublicKeyPairLabel" -
labelPrivate="CAPrivateKeyPairLabel" -sign=T -verify=T
3 When prompted, enter the password for the partition on Gemalto HSM Server (you
configured it in "Step 2 of 5: Configuring the Gemalto HSM Server to Work with Security
Gateway / ClusterXL" on page 56).
Example:
Enter a password for the token in slot 0:
4 Select the RSA mechanism by entering the corresponding number:

[1] PKCS [2] FIPS 186-3 Only Primes [3] FIPS 186-3 Auxiliary
Primes
5 View the handles of the key pair you created.

Reference Guide > Certificate Management Utility (CMU) > cmu list.
# ./cmu list
Example output:
Enter password for token in slot 0 : <Password for the
Partition>
handle=17 label=CAPrivateKeyPairLabel
handle=18 label=CAPublicKeyPairLabel
6 Use the handle numbers from the previous step to create the CA certificate.
Reference Guide > Certificate Management Utility (CMU) > cmu selfsigncertificate
Example:
# ./cmu selfsigncertificate -privatehandle=17
CN="www.gemltoHSM.cp" -sha256WithRSA -startDate 20190720 -
endDate 20240720 -serialNum=111aaa -keyusage
digitalsignature,keycertsign,crlsign -
basicconstraints=critical,ca:true

Step Instructions
7 View the handles of the CA certificate you created.

# ./cmu list
Example output:
Enter password for token in slot 0 : <Password for the
Partition>
handle=13 label=www.myhsm.cp
handle=17 label=CAPrivateKeyPairLabel
handle=18 label=CAPublicKeyPairLabel
Important - You use the numbers of these three handles later when you configure the
$FWDIR/conf/hsm_configuration.C file on the Check Point Security Gateway /
each Cluster Member.
8 Export the CA certificate to a file.

Reference Guide > Certificate Management Utility (CMU) > cmu export
# ./cmu export -handle=<Handle Number> -outputfile=<Name of
Output File>

Step 5 of 5: Configuring the Security Gateway / ClusterXL to Work with the Gemalto HSM Server
This step has three sub-steps.

Sub-Step 5-A: Configuring HTTPS Inspection on the Security Gateway / Cluster Members to
work without the Gemalto HSM Server
Important:
n In a VSX environment, you must perform this step in the context of each Virtual
System (on the VSX Gateway or each VSX Cluster Member).
Step Instructions
1 In SmartConsole, enable and configure the HTTPS Inspection.

2 On the Security Gateway (each Cluster Member), disable the HSM in the
c. Edit the file:
:enabled ("no")
3 In SmartConsole, install the applicable Access Control Policy on the Security Gateway /
ClusterXL object.
b. On the internal computer, in the web browser, you should receive the signed CA
certificate from the Security Gateway / ClusterXL.

Sub-Step 5-B: Installing the Gemalto HSM Simplified Client Software Packages on the
Security Gateway (Cluster Members)
Important:
n In a VSX environment, you must perform this step in the context of the VSX Gateway
or each VSX Cluster Member (context of VS 0).
Notes:
n For more information, see the Gemalto SafeNet Network HSM 6.2.2 Product
Documentation.
For information about establishing a Trust Link, go to the Appliance Administration
Guide > Configuration without One-step NTLS > [Step 7] Create a Network Trust Link
Between the Client and the Appliance.
n If you need to establish new Trust Link, you have to delete the current Trust Link.
See "Deleting a Trust Link with the HSM Server" on page 65.
Step Instructions
1 Open the Gemalto HSM Client package you received from Gemalto:
610-012382-017_SW_Client_HSM_6.2.2_RevA
Go to this directory: linux > 32
2 Install the HSM Client package.

Installation Guide > SafeNet HSM Client Software Installation.
3 In the Expert mode, copy the libCryptoki2.so file to the /usr/lib/hsm_client/ directory:
cp -v /usr/safenet/lunaclient/lib/libCryptoki2.so
/usr/lib/hsm_client/
Important - For security reasons, only the root user has permissions to access this
directory.
You must copy the physical file into this directory. Do not create a symbolic link.
4 Establish a Trust Link between the Gemalto HSM Client on the Security Gateway / each
Cluster Member and the Gemalto HSM Server.
Configuration Guide > [Step 7] Create a trusted link and register Client and Appliance
with each other.
On the Security Gateway / each Cluster Member, run in LunaCM:
lunacm:> clientconfig deploy -c <IP Address of Security
Gateway or Cluster Member> -n <IP Address of HSM Server> -par
<Partition Name> -pw <Partition Password>
5 Examine the partition access on the Security Gateway / each Cluster Member:
# /usr/safenet/lunaclient/bin/vtl verify

Sub-Step 5-C: Configuring HTTPS Inspection on the Security Gateway / Cluster Members to
work with the Gemalto HSM Server
Important:
Notes:
n After you apply the HSM configuration for the first time, you may get an HSM
connection error.
Most common scenario is when you configure several Security Gateways (Cluster
Members) to use the same HSM Server, and they access it at the same time.
In this case:
a. Run the "fw fetch local" command on the Security Gateway (Cluster
Member) that has an HSM connection issue.
In a VSX environment, run this command in the context of the problematic
VSX Virtual System.
b. Wait until you see "HSM on".
c. Continue to configure the next Security Gateway, Cluster Member, or VSX
Virtual System.
n After any change in the $FWDIR/conf/hsm_configuration.C file, you must do
one of these:
l Fetch the local policy with the "fw fetch local" command
l In SmartConsole, install the policy on the Security Gateway / ClusterXL / VSX
Virtual System object.

n If the HSM Server is not available when you fetch the local policy or install the policy
in SmartConsole, the HTTPS Inspection cannot inspect the Outbound HTTPS traffic.
As a result, internal computers behind the Security Gateway / ClusterXL / VSX Virtual
System cannot to access HTTPS web sites.
Server" on page 81.
Step Instructions
3 Back up the $FWDIR/conf/hsm_configuration.C file:

cp -v $FWDIR/conf/hsm_configuration.C{,_BKP}
4 Edit the $FWDIR/conf/hsm_configuration.C file:


Step Instructions
5 Configure the required values for these attributes:

(
:enabled ("yes")
:hsm_vendor_name ("Luna Gemalto HSM")
:lib_filename ("libCryptoki2.so")
:CA_cert_public_key_handle (<Number of "Public" Handle for CA
certificate>)
:CA_cert_private_key_handle (<Number of "Private" Handle for
CA certificate>)
:CA_cert_buffer_handle (<Number of Handle for CA
certificate>)
:token_id ("<Password for Partition on Gemalto HSM Server>")
)
Notes:
n The ":hsm_vendor_name ()" attribute must contain the string "Luna
Gemalto HSM" (or must be empty).
n The ":lib_filename ()" attribute must contain the name of the PKCS#11
library of the Gemalto HSM vendor (located in the /usr/lib/hsm_client/
directory on the Security Gateway / each Cluster Member.
n The ":CA_cert_<XXX> ()" attributes must have the required values of
handles from the output of the "cmu list" command on the Gemalto HSM
Server.
See "Step 4 of 5: Creating the CA Certificate on the Gemalto HSM Server"
on page 58.
n The ":token_id ()" attribute must have the contain the password for the
partition on the Gemalto HSM Server.
See "Step 2 of 5: Configuring the Gemalto HSM Server to Work with
Security Gateway / ClusterXL" on page 56.
Example:
(
:enabled ("yes")
:hsm_vendor_name ("Gemalto HSM")
:lib_filename ("libCryptoki2.so")
:token_id ("p@ssw0rd")
)

Step Instructions
6 Apply the new configuration.

n If you explicitly defined (or changed) the value of the ":hsm_vendor_name ()"
attribute the string "Gemalto HSM", then restart all Check Point services with this
command:
cprestart
Important - This blocks all traffic until all services restart. In a cluster, this
can cause a failover.
n If you did not define the value of the ":hsm_vendor_name ()" attribute (it is
empty), then fetch the local policy with this command:
fw fetch local
Run this command:
n HSM partition access (Accessible/Not Accessible):
Accessible

b. On the internal computer, in the web browser, you should receive the signed CA

Additional Actions for a Gemalto HSM Server

Deleting a Trust Link with the HSM Server
If you need to establish new Trust Link between a Check Point Security Gateway and an HSM Server,
you have to delete the current Trust Link.
Use Case: When you replace or reconfigure a Check Point Security Gateway, or an HSM Server.
Step Instructions
1 Delete the current Trust Link on the Check Point Security Gateway / each Cluster Member:
c. Go to the SafeNet HSM Simplified Client installation directory:
cd /usr/safenet/lunaclient/bin/
d. Delete the old Trust Link:
./vtl deleteServer -n <IP Address of HSM Server>
2 Delete the current Trust Link on the HSM Appliance:

a. Connect to the HSM Appliance over SSH.
b. Examine the list of configured HSM Client Workstations:
lunash:> client list
c. Delete the Check Point HSM Client Workstation:
lunash:> client delete -client <Name of HSM Client>
Note - For more information, see the Gemalto SafeNet Network HSM 6.2.2 Product
Documentation.

Configuring a Second Interface on a Gemalto HSM Appliance for NTLS
Step Instructions
1 Connect to the HSM Appliance over SSH.
2 Examine all the configured interfaces:

lunash:> network show
3 Add a new interface:

lunash:> network interface -device <Name of
Interface> -ip <IP Address> -netmask
<NetMask> [-gateway <IP Address>]
4 Enable Network Trust Link Service (NTLS) on all the interfaces.
Note - For more information, see the Gemalto SafeNet Network HSM 6.2.2 Product
Documentation > LunaSH Command Reference Guide > LunaSH Commands.

Working with FutureX HSM

Use this workflow to configure a Check Point Security Gateway / ClusterXL to work with the FutureX HSM
Server.
Prerequisites
FutureX Software Packages
The FutureX vendor supplies all these packages.
Package Files Description
FutureX n fxpkcs11- Contains the FutureX PKCS #11 Library.

PKCS11 windows-4.20- Install on the:
Library 4afd.zip
n fxpkcs11-
n FutureX HSM Client Workstation
redhat-4.20- n Check Point Security Gateway / each Cluster
4afd.tar Member.
n fxpkcs11-
linux-4.20-
4afd.tar
n fxpkcs11-mac-
4.20-4afd.tar
FutureX CLI n fxcl-hsm- Contains the FutureX CLI Utility to manage keys and
Utility windows- certificates.
1.2.4.2- Install on the FutureX HSM Client Workstation.
37a8.zip
n fxcl-hsm-
redhat-
1.2.4.2-
37a8.tar
n fxcl-hsm-
linux-1.2.4.2-
37a8.tar
n fxcl-hsm-mac-
1.2.4.2-
37a8.tar
n fxcli-hsm-
commands.txt
FutureX FutureX certificates for trust between the FutureX HSM

Certificates Client Workstation and the FutureX HSM Server.
Configuration Steps
Use this workflow to configure a Check Point Security Gateway / ClusterXL to work with the FutureX HSM
Server.

Step 1 of 3: Configuring the FutureX HSM Client Workstation
You use the FutureX HSM Client Workstation to:

n Create a CA Certificate on the FutureX HSM Server. The Check Point Security Gateway uses this
CA Certificate for HTTPS Inspection to store and access SSL keys on the FutureX HSM Server.
n Manage keys for fake certificate the Check Point Security Gateway / ClusterXLcreated.
Step Instructions
1 Install a computer to use as a FutureX HSM Client Workstation.

Get the applicable HSM Client package from the FutureX vendor.
A FutureX HSM Client Workstation can run these operating systems (for more information,
contact the FutureX vendor):
n Windows (contact FutureX vendor to download and install the “FXTools” package
from the FutureX portal).
n Red Hat Linux
n Ubuntu Linux
n Debian Linux
n macOS
2 Transfer the applicable FutureX PKCS #11 Library package to the FutureX HSM Client
Workstation.
n For Windows OS:
fxpkcs11-windows-<BUILD>.zip
n For Red Hat Linux OS:
fxpkcs11-redhat-<BUILD>.tar
n For Ubuntu and Debian Linux OS:
fxpkcs11-linux-<BUILD>.tar
n For macOS:
fxpkcs11-mac-<BUILD>.tar
Important - Make sure to transfer the file in the binary mode.
3 Extract the contents of the FutureX PKCS #11 Library package to some directory on the
FutureX HSM Client Workstation.
In the instructions below, we show this directory as: <PKCS#11 Dir>.
Important:
n The FutureX PKCS #11 Library package (fxpkcs11-<OS>-<BUILD>) contains
the nested directory called "fxpkcs11".
You must extract the contents of this nested directory "fxpkcs11" into the
<PKCS#11 Dir> directory.
n The nested directory "fxpkcs11" contains the nested directories called "x64"
(for 64-bit OS) and "x86" (for 32-bit OS).
You must extract the contents of the applicable nested directory "x64" or "x86"
into the <PKCS#11 Dir> directory.
4 Transfer the certificates you received from the FutureX vendor to some directory on the
FutureX HSM Client Workstation.

Step Instructions
5 Prepare the HSM Client to work with the PKCS#11 manager:

a. On a Linux-based HSM Client, install the OpenSSL package:
n On Ubuntu and Debian Linux, run:
sudo apt-get install openssl

n On Red Hat Linux, run:
sudo yum install openssl
b. Make sure this FutureX PKCS #11 Library file is located in the <PKCS#11 Dir>
directory:
n On Linux OS:
libfxpkcs11.so
n On Windows OS:
fxpkcs11.dll
c. Make sure the configuration file fxpkcs11.cfg is located in the applicable directory:
n On Linux OS:
Transfer this file from the <PKCS#11 Dir> directory to the /etc/ directory
(you must edit the copied file in the /etc/ directory).
n On Windows OS:
Keep this file in the <PKCS#11 Dir> directory.

d. Configure these settings in the file fxpkcs11.cfg:
n <LOG-FILE>
Set the path to the log file in this attribute.

n <ADDRESS>
Set the IP address of the FutureX HSM Server in this attribute.

n <PROD-PORT>
Set the port on the FutureX HSM Server in this attribute.

You can use the default port 9100, or configure a different port.
If you use a Cloud FutureX HSM, get the port number from the FutureX
Support.
Additional related attributes:
n <PROD-TLS-CA>
Contains the path to the Certificate Authority certificate file.

This attribute can appear multiple times.
You can put all the certificates of the CA chain.
n <PROD-TLS-CERT>
Contains the path to the client certificate file.

n <PROD-TLS-KEY>
Contains the path to the client private key file.

Step Instructions
6 Test the PKCS#11 Library:

a. To test the configuration, run the tool configTest from the <PKCS#11 Dir> directory.
b. To manage keys, run the tool PKCS11Manager from the <PKCS#11 Dir> directory.
c. Examine the log file you configured in the <LOG-FILE> attribute in the fxpkcs11.cfg
file.
Important - If you have problems with the location of the configuration file or the
PKCS #11 Library file, you can set these environmental variables:
n FXPKCS11_CFG to contain the full path to the configuration file fxpkcs11.cfg
n FXPKCS11_MODULE to contain the full path to the PKCS #11 Library file
To set an environmental variable:
n On Linux OS, use this command:
export VARIABLE=VALUE
Example:
export FXPKCS11_CFG=/home/user/fxpkcs11.cfg
n On Windows OS, use this command:
set VARIABLE=VALUE
Example:
set FXPKCS11_CFG=C:\Users\Futurex\Desktop\fxpkcs11.cfg
7 For more information about the configuration of PKCS#11 on the FutureX HSM Client
Workstation:
a. Log in to the FutureX portal.
b. Go to:
DEVELOPER DOCUMENTATION >
GENERAL PURPOSE >
General Purpose Technical Reference >
PKCS #11 Technical Reference
8 Transfer the applicable FutureX CLI Utility package to the FutureX HSM Client
Workstation.
n For Windows OS:
fxcl-hsm-windows-<BUILD>.zip
n For Red Hat Linux OS:
fxcl-hsm-redhat-<BUILD>.tar
n For Ubuntu and Debian Linux OS:
fxcl-hsm-linux-<BUILD>.tar
n For macOS:
fxcl-hsm-mac-<BUILD>.tar
Important - Make sure to transfer the file in the binary mode.

Step Instructions
9 Extract the contents of the FutureX CLI Utility package to some directory on the FutureX
HSM Client Workstation.
In the instructions below, we show this directory as: <CLI Dir>.
Important:
n The FutureX CLI Utility package (fxcl-hsm-<OS>-<BUILD>) contains the
nested directory called "fxcl".
n The nested directory fxcl contains the nested directories called "x64" (for 64-bit
OS) and "x86" (for 32-bit OS).
n The nested directories x64 and x86 contain the nested directories called
"OpenSSL-1.0.x" and "OpenSSL-1.1.x".
You must extract the contents of the applicable nested directory "OpenSSL-
1.0.x" or "OpenSSL-1.1.x" into the <CLI Dir> directory.
Administrator decides, which version of the OpenSSL to use (for more
information, contact the FutureX vendor).
10 Transfer these certificates to the <CLI Dir> directory on the FutureX HSM Client
Workstation:
n The Client certificate (denoted below as <Client Certificate>)
n The CA certificate (denoted below as <CA Certificate>)
11 Establish a connection between the FutureX HSM Client and the FutureX HSM Server:
a. Go to the <CLI Dir> directory.
b. Start the shell:
fxcli-hsm
c. Run these commands in the order they are listed:
tls pki -f <Client Certificate> -p safest
tls ca -f <CA Certificate>
connect tcp -c <IP Address of URL of HSM Server>:<Port on

HSM Server>
login user -u <Username> -p <Password (default is

"safest")>
exit

Step Instructions
12 You can use these tools on the FutureX HSM Client Workstation to manage keys and
certificates that are stored on the FutureX HSM Server:
a. PKCS11Manager
n Run this command from the <PKCS#11 Dir> directory.
n This tool can create keys and browse the content of the HSM partition (that
stores keys and certificates).
n Follow the tool's menu to see the available options.
b. fxcli-hsm
n Run this command from the <CLI Dir> directory.
n To see all available commands in this shell, run: help
n To see all available options for a command in this shell, either run only the
command, or the command with the "-h" option.
Step 2 of 3: Creating the CA Certificate on the FutureX HSM Server
Step Instructions
1 On the FutureX HSM Client Workstation, open the FutureX CLI utility.
2 Get the list of available slots.

Run one of these commands:
keytable list
keytable reload
3 Generate the key pair for the CA certificate:

generate -a rsa -b 2048 --slot <Slot or Label of CA
Certificate> --name <Name of CA Certificate Private Key File> -
-tpk-slot <Slot or Label of CA Certificate Public Key> --tpk-
name <Name of CA Certificate Public Key File> -u sign,verify
Example:
generate -a RSA -b 2048 --slot 0 --name CAPrivateKey --tpk-slot
1 --tpk-name CAPublicKey -u sign,verify
Important - Do not use the "... slot next" option, because it can override keys
for a fake certificate the Check Point Security Gateway / ClusterXL created.

Step Instructions
4 Generate the CA certificate:

x509 sign --private-slot <Slot or Label of Private Key> --dn
"<Distinguished Name of CA Certificate>" --ca 1 --key-usage
DigitalSignature --key-usage CrlSign --key-usage KeyCertSign --
save-slot <Slot to Save the CA Certificate> --save-name <Label
of CA Certificate File> -o <Full Path and Name of CA
Certificate File>.cer --validity-period '<Period>'
Example:
x509 sign --private-slot 0 --dn "CN=www.futurexhsm.cp" --ca 1 -
-key-usage DigitalSignature --key-usage KeyCertSign --key-usage
CrlSign --save-slot 2 --save-name CACert -o Z:\FutureXhsm.cer -
-validity-period '5 years'
Important - Do not use the "... slot next" option, because it can override keys
for a fake certificate the Check Point Security Gateway / ClusterXL created.
5 Get the list of slots used for the CA certificate and CA certificate's key pair.
Run one of these commands:
keytable list
keytable reload
Note - The command "keytable list" shows the slot numbers as the PKCS#11
handles plus one. For example, it shows slot 0 as handle 1, slot 1 as handle 2, and so
on.
6 Write down the handles of the:

n CA certificate
n CA certificate public key
n CA certificate private key
Example:
CAPublicKey (1)
CAPrivateKey (2)
CACert (3)
Important - You use the numbers of these three handles when you configure the
$FWDIR/conf/hsm_configuration.C file on the Check Point Security Gateway /
ClusterXL.

Step 3 of 3: Configuring the Security Gateway / ClusterXL to Work with the FutureX HSM Server
This step has four sub-steps.

Sub-Step 3-A: Configuring HTTPS Inspection on the Security Gateway / Cluster Members to
work without the FutureX HSM Server
Important:
n In a VSX environment, you must perform this step in the context of each Virtual
System (on the VSX Gateway or each VSX Cluster Member).
Step Instructions
1 In SmartConsole, configure the HTTPS Inspection.

2 On the Security Gateway / each Cluster Member, disable the HSM in the
c. Edit the file:
:enabled ("no")
3 In SmartConsole, install the applicable Access Control Policy on the Security Gateway /
ClusterXL object.
certificate from the Security Gateway / ClusterXL.

Sub-Step 3-B: Installing the required software packages on the Security Gateway (Cluster
Members)
Important:
Step Instructions
1 Transfer the FutureX PKCS #11 binary files to the Security Gateway / each Cluster
Member:
a. Open the FutureX PKCS#11 Library package.
b. Go to this folder:
fxpkcs11-linux-<BUILD> > fxpkcs11 > x86 > OpenSSL-1.1.x
c. Transfer these files to the Security Gateway (each Cluster Member) to the
/usr/lib/hsm_client/ directory:
n libfxpkcs11.so
n configTest
Important - Make sure to transfer the files in the binary mode.
2 Transfer the FutureX PKCS #11 configuration file to the Security Gateway / each
Cluster Member:
a. Open the FutureX PKCS#11 Library package.
b. Go to this folder:
fxpkcs11-linux-<BUILD> > fxpkcs11
c. Transfer this file to the Security Gateway / each Cluster Member to the /etc/
directory:
fxpkcs11.cfg

Sub-Step 3-C: Configuring a connection between the Security Gateway / Cluster Members
and the FutureX HSM Server
To establish a connection between a Check PointSecurity Gateway (HSM client) to a FutureX HSM
server, you must create certificate files for the TLS authentication between the Check PointSecurity
Gateway and the FutureX HSM server. These are the options to create the required certificate files:
n Create the certificates on the HSM (the most common method).
n Get the certificates from the FutureX vendor.
n Enabling the "Anonymous" setting on the HSM server, so that mutual authentication is not
required (see the FutureX Integration Guide).
Important:
Step Instructions
1 Transfer the FutureX certificate files you received from the FutureX vendor to the
Security Gateway / each Cluster Member to the /usr/futurex/ directory.
4 Back up the configuration file /etc/fxpkcs11.cfg:

cp -v /etc/fxpkcs11.cfg{,_BKP}
5 Edit the configuration file /etc/fxpkcs11.cfg:

vi /etc/fxpkcs11.cfg

Step Instructions
6 Configure these attribute values:

Attribute Attribute Value
<LOG-FILE> /var/log/fxpkcs11.log
<ADDRESS> The IP address (or URL) of the FutureX HSM Server.
<PROD-PORT> The port on the FutureX HSM Server.

You can use the default port 9100, or configure a different
port.
<PROD-TLS-CA> The path to the Certificate Authority certificate file.

This attribute can appear multiple times.
<PROD-TLS- The path to the client certificate file.

CERT>
<PROD-TLS-KEY> The path to the client private key file.
7 Save the changes in the file and exit the editor.
8 Create the required symbolic link:

ln -s /var/log/fxpkcs11.log /tmp/fxpkcs11.log
Sub-Step 3-D: Configuring HTTPS Inspection on the Security Gateway / Cluster Members to
work with the FutureX HSM Server
Important:

Notes:
n After you apply the HSM configuration for the first time, you can get an HSM
connection error.
Most common scenario is when you configure several Security Gateways / Cluster
Members to use the same HSM Server, and they access it at the same time.
In this case:
a. Run the "fw fetch local" command on the Security Gateway / Cluster
Member that has an HSM connection issue.
In a VSX environment, run this command in the context of the problematic
VSX Virtual System.
b. When you see "HSM on" on the screen, continue to configure the next Security
Gateway / each Cluster Member / VSX Virtual System.
n After any change in the $FWDIR/conf/hsm_configuration.C file, you must do
one of these:
l Fetch the local policy with the "fw fetch local" command
l In SmartConsole, install the policy on the Security Gateway / ClusterXL / VSX
Virtual System object.

n If the HSM Server is not available when you fetch the local policy or install the policy
in SmartConsole, the HTTPS Inspection cannot inspect the Outbound HTTPS traffic.
As a result, internal computers behind the Security Gateway / ClusterXL / VSX Virtual
System cannot access HTTPS web sites.
Server" on page 81.
Step Instructions
3 Back up the $FWDIR/conf/hsm_configuration.C file:

cp -v $FWDIR/conf/hsm_configuration.C{,_BKP}


Step Instructions
5 Configure the required values for these attributes:

(
:enabled ("yes")
:lib_filename ("")
:CA_cert_public_key_handle (<Number of "CAPublicKey" Handle
for CA certificate>)
:CA_cert_private_key_handle (<Number of "CAPrivateKey" Handle
for CA certificate>)
:CA_cert_buffer_handle (<Number of "CACert" Handle for CA
certificate>)
:token_id ("<Password for Partition on FutureX HSM Server>")
)
Notes:
n The ":hsm_vendor_name ()" attribute must contain the string "FutureX
HSM".
n The ":lib_filename ()" attribute must contain the full path to the file
libfxpkcs11.so (from the FutureX PKCS #11 Library) on the Security
Gateway / each Cluster Member.
You must configure this full path explicitly, if this file is not located at the
default path: /usr/lib/libfxpkcs11.so
n The ":CA_cert_<XXX> ()" attributes must have the required values of
handles from the output of the "keytable" command on the FutureX HSM
Server.
See "Step 2 of 3: Creating the CA Certificate on the FutureX HSM Server"
on page 72.
n The ":token_id ()" attribute must have the contain the password for the
partition on the FutureX HSM Server.
Example:
(:enabled ("yes")
:lib_filename ("")
:token_id ("p@ssw0rd")
)

Step Instructions
6 Apply the new configuration.

n If you explicitly defined (or changed) the value of the ":hsm_vendor_name ()"
attribute to the string "FutureX HSM", then restart all Check Point services with
this command:
cprestart
Important - This blocks all traffic until all services restart. In a cluster, this
can cause a failover.
n If the value of the ":hsm_vendor_name ()" attribute already contained the string
"FutureX HSM", then fetch the local policy with this command:
fw fetch local
Run this command:
n HSM partition access (Accessible/Not Accessible):
Accessible

Note - If there is a connectivity issue from the Check Point Security Gateway / Cluster
Member to the FutureX HSM Server, then perform these steps on the Security Gateway /
Cluster Member:
1. Examine the /var/log/fxpkcs11.log file.
If you do not see a root cause in this log file, continue to the next step to configure
verbose logs.
2. Configure these logging settings in the /etc/fxpkcs11.cfg file to see more information
in the log file:
n LOG-TRAFFIC: YES
n LOG-MODE: INFO
or
LOG-MODE: ERROR

Disabling Communication from the Security Gateway to the HSM Server
Disabling Communication from the Security

Gateway to the HSM Server
You can disable communication from the Check Point Security Gateway / Cluster Members to an HSM
Server. For example, when the HSM Server is under maintenance.
Important:
n In a VSX environment, you must perform this step in the context of each Virtual System (on
the VSX Gateway or each VSX Cluster Member).
Step Instructions

4 Configure the value "no" for the parameter "enabled":

:enabled ("no")
6 On the Security Gateway / each Cluster Member / Security Group, restart Check Point
services:
cprestart
Important - Traffic does not flow through until the services start.

Monitoring HTTPS Inspection When Security Gateway Works with HSM
Monitoring HTTPS Inspection When Security

Gateway Works with HSM
When HTTPS Inspection daemon wstlsd initializes on a Check Point Security Gateway / Cluster Member, it
checks whether this Security Gateway / Cluster Member is configured to work with an HSM Server.
n You can see the applicable logs in SmartConsole > Logs & Monitor > Logs tab.
See "Monitoring HTTPS Inspection with HSM in SmartConsole Logs" on page 83.
n You can query the HTTPS Inspection on the Security Gateway / Cluster Members over SNMP.
See "Monitoring HTTPS Inspection with HSM over SNMP" on page 87.
n You can run the "cpstat https_inspection" command on the Security Gateway / Cluster
Members.
See "Monitoring HTTPS Inspection with HSM in CLI" on page 96.
Note - To see detailed information about wstlsd initialization, follow sk105559: How to debug
WSTLSD daemon.

Monitoring HTTPS Inspection with HSM in SmartConsole Logs
Monitoring HTTPS Inspection with HSM in SmartConsole

Logs
To see the HTTPS Inspection logs about the Gemalto HSM Server in SmartConsole:
Step Instructions
1 From the left navigation panel, click Logs & Monitor > Logs.
2 In the search field, enter:

type:Control
3 Double-click the applicable log.
4 In the log, refer to the More section.
Possible logs are:
Log Additional
Log Description Explanation
Information
HSM is enabled n The value of the :enabled() attribute is

for outbound set to "yes" in the $FWDIR/conf/hsm_
HTTPS inspection configuration.C file on the Security
with <HSM Vendor> Gateway / Cluster Member.
n The <HSM Vendor> is the value of the
":hsm_vendor_name ()" attribute in the
$FWDIR/conf/hsm_
configuration.C file on the on the
Security Gateway / Cluster Member.

Log Additional
Information
HSM is disabled One of these:

for outbound
HTTPS inspection
n The HSM Client software packages are
not installed on the Security Gateway /
Cluster Member.
n The $FWDIR/conf/hsm_
configuration.C file does not exist
on the Security Gateway / Cluster
Member.
n The value of the :enabled() attribute is
set to "no" in the $FWDIR/conf/hsm_
configuration.C file on the Security
Gateway / Cluster Member.
n The :enabled() attribute is corrupted in
the $FWDIR/conf/hsm_
Important - In these cases, outbound
HTTPS Inspection works without the HSM
Server, and SSL keys are stored on the
Outbound HTTPS Gateway is All these conditions were met:

inspection works connected to HSM
with HSM 1. The value of the ":enabled()" attribute is
set to "yes" in the $FWDIR/conf/hsm_
2. Security Gateway / Cluster Member
could connect to the HSM Server.

Log Additional
Information
Outbound HTTPS One of these strings: See the section Log Additional Information in
inspection is off the log.
due to HSM error
n HSM
configuration
file is
corrupted
n Loading HSM
library failed
n There is no
trust or no
connectivity
with HSM server
n Login to HSM
partition
failed
n Error importing
CA certificate
from HSM server
n Error
generating key
pair on HSM
server

Example:

Monitoring HTTPS Inspection with HSM over SNMP

You can query the HTTPS Inspection status and the status of connection to the HSM Server on the Security
Gateway / Cluster Member over SNMP:
n Full OID is:
.iso.org.dod.internet.private.enterprises.checkpoint.products.httpsIns
pection
n Numerical OID is:
.1.3.6.1.4.1.2620.1.54
"HTTPS Inspection status"
To get the HTTPS Inspection status, query this SNMP object:
Returned
SNMP OID Explanation
strings
httpsInspectionStatus On HTTPS Inspection feature is configured on the

.1.3.6.1.4.1.2620.1.54.1
Off HTTPS Inspection feature is not configured on the
"HTTPS Inspection status description"
To get the HTTPS Inspection status description, query this SNMP object:
Returned
strings
httpsInspectionStatusDescription HTTPS HTTPS Inspection feature is

Inspection configured on the Security
.1.3.6.1.4.1.2620.1.54.2 is on Gateway / Cluster Member.
HTTPS HTTPS Inspection feature is not

Inspection configured on the Security
is off Gateway / Cluster Member.

"HSM configuration status"
To get the HSM configuration status, query this SNMP object:
Returned
strings
hsmStatus.hsmEnabled Enabled The value of the ":enabled()" attribute is set to

"yes" in the $FWDIR/conf/hsm_
.1.3.6.1.4.1.2620.1.54.3.1 configuration.C file on the Security Gateway /
Cluster Member.
Disabled One of these:

n The HSM Client software packages are not
installed on the Security Gateway / Cluster
Member.
configuration.C file does not exist on
the Security Gateway / Cluster Member.
n The value of the ":enabled()" attribute is set
to "no" in the $FWDIR/conf/hsm_
n The ":enabled()" attribute is corrupted in the
$FWDIR/conf/hsm_configuration.C
file on the Security Gateway / Cluster
Member.
Important - In these cases, outbound HTTPS
Inspection works without the HSM Server,
and SSL keys are stored on the Security

"HSM configuration status description"
To get the HSM configuration status description, query this SNMP object:
Returned
strings
hsmStatus.hsmEnabledDescription HSM is n The value of the :enabled

enabled for () attribute is set to "yes" in
.1.3.6.1.4.1.2620.1.54.3.2 HTTPS the $FWDIR/conf/hsm_
inspection configuration.C file
with <HSM on the Security Gateway /
Vendor> Cluster Member.
n The <HSM Vendor> is the
value of the ":hsm_
vendor_name ()" attribute
in the
$FWDIR/conf/hsm_
configuration.C file
on the Security Gateway /
Cluster Member.
HSM is One of these:

disabled for
HTTPS
n The HSM Client software
inspection packages are not installed
Cluster Member.
does not exist on the
Security Gateway / Cluster
Member.
n The HTTPS Inspection
daemon wstlsd could not
read the value of the
":enabled()" attribute in
Cluster Member.
n The ":enabled()" attribute
is corrupted in the
$FWDIR/conf/hsm_
Cluster Member.
Important - In these cases,

outbound HTTPS
Inspection works without
the HSM Server, and SSL
keys are stored on the
Member.

"HSM partition access status"
To get the HSM partition access status, query this SNMP object:
Returned
strings
hsmStatus.hsmPartitionAccess N/A Security Gateway / Cluster Member

could not check the access to its
.1.3.6.1.4.1.2620.1.54.3.3 partition on the HSM Server.
Most probably, because HSM
configuration is disabled on the
Accessible Security Gateway / Cluster Member

could access its partition on the HSM
Server.
Not Security Gateway / Cluster Member

Accessible could not access its partition on the
HSM Server because of an error.

"HSM partition access status description"
To get the HSM partition access status description, query this SNMP object:
Returned
strings
hsmStatus.hsmPartitionAccessDescriptio HSM Security Gateway /

n partition Cluster Member could
access not check the access to
.1.3.6.1.4.1.2620.1.54.3.4 cannot be its partition on the HSM
checked Server.
Gateway can Security Gateway /

access HSM Cluster Member could
partition access its partition on the
for HTTPS HSM Server.
inspection
Gateway Security Gateway /

cannot Cluster Member could
access HSM not access its partition on
partition the HSM Server because
for HTTPS of an error.
inspection: Possible error messages
<Error are:
Message>
n HSM
configuration
file is
corrupted
n Loading HSM
library
failed
n There is no
trust or no
connectivity
with HSM
server
n Login to HSM
partition
failed

"Outbound HTTPS Inspection status"
To get the Outbound HTTPS Inspection status, query this SNMP object:
Returned
strings
hsmStatus.outboundStatus N / A When the HTTPS Inspection daemon wstlsd

starts, it is necessary to wait for one minute or
.1.3.6.1.4.1.2620.1.54.3.5 less, until you can get the actual status.
HSM on All these conditions were met:

1. The value of the ":enabled()" attribute is
2. Security Gateway / Cluster Member
could connect to the HSM Server.
HSM off One of these:

n The HSM Client software packages are
not installed on the Security Gateway /
Cluster Member.
configuration.C file does not exist
on the Security Gateway / Cluster
Member.
n The value of the ":enabled()" attribute is
set to "no" in the $FWDIR/conf/hsm_
n The ":enabled()" attribute is corrupted in
Important - In these cases, outbound
HTTPS Inspection works without the
HSM Server, and SSL keys are stored on
HSM error All these conditions were met:

1. The value of the ":enabled()" attribute is
2. An error occurred.
Important - In this case, outbound
HTTPS Inspection does not work, and
HTTPS traffic does not pass through.

Note - The conditions for the returned strings are calculated on the Security Gateway / Cluster
Member during the start of the HTTPS Inspection daemon wstlsd, or during policy
installation. For example, you can get "hsmStatus.hsmEnabled = HSM enabled" and
"hsmStatus.outboundStatus = HSM off", because when the wstlsd daemon started,
or during last policy installation, the HSM configuration was disabled.
"Outbound HTTPS Inspection status description"
To get the Outbound HTTPS Inspection status description, query this SNMP object:
SNMP OID Returned strings Explanation
hsmStatus.outboundStatusDescripti Cannot get When the HTTPS

on HTTPS Inspection daemon wstlsd
inspection starts, it is necessary to wait
.1.3.6.1.4.1.2620.1.54.3.6 outbound for one minute or less, until
status. Process you can get the actual
may be under status.
initialization.
Please try
again in a
minute.
Outbound HTTPS All these conditions were

inspection met:
works with HSM
1. The value of the
":enabled()" attribute
is set to "yes" in the
$FWDIR/conf/hs
m_
configuration.C
file on the Security
Gateway / Cluster
Member.
2. Security Gateway /
Cluster Member
could connect to the
HSM Appliance
Server.
Outbound HTTPS The value of the ":enabled

inspection ()" attribute is set to "no" in
works without the $FWDIR/conf/hsm_
HSM configuration.C file on
the Security Gateway /
Cluster Member, or this file
does not exist.

SNMP OID Returned strings Explanation
Outbound HTTPS All these conditions were

inspection is met:
off due to HSM
error: <Error 1. The value of the
Message> ":enabled()" attribute
is set to "yes" in the
$FWDIR/conf/hs
m_
configuration.C
file on the Security
Gateway / Cluster
Member.
Important - In this
case, outbound
HTTPS Inspection
does not work, and
HTTPS traffic does not
pass through.
Possible error messages
are:
n HSM
configuration
file is
corrupted
n Loading HSM
library failed
n There is no
trust or no
connectivity
with HSM server
n Login to HSM
partition
failed
n Error importing
CA certificate
from HSM server
n Error
generating key
pair on HSM
server
installation. For example, you can get "hsmStatus.hsmEnabledDescription = HSM is
enabled for HTTPS inspection with <HSM Vendor>" and
"hsmStatus.outboundStatusDescription = Outbound HTTPS inspection
works without HSM", because when the wstlsd daemon started, or during last policy
installation, the HSM configuration was disabled.

Examples
# snmpwalk -m $CPDIR/lib/snmp/chkpnt.mib -On -v 2c -c public localhost 1.3.6.1.4.1.2620.1.54
.1.3.6.1.4.1.2620.1.54.1.0 = STRING: On
.1.3.6.1.4.1.2620.1.54.2.0 = STRING: HTTPS Inspection is on
.1.3.6.1.4.1.2620.1.54.3.1.0 = STRING: Enabled
.1.3.6.1.4.1.2620.1.54.3.2.0 = STRING: HSM is enabled for HTTPS inspection with Gemalto HSM
.1.3.6.1.4.1.2620.1.54.3.3.0 = STRING: Accessible
.1.3.6.1.4.1.2620.1.54.3.4.0 = STRING: Gateway can access HSM partition for HTTPS inspection
.1.3.6.1.4.1.2620.1.54.3.5.0 = STRING: HSM on
.1.3.6.1.4.1.2620.1.54.3.6.0 = STRING: Outbound HTTPS inspection works with HSM
# snmpwalk -m $CPDIR/lib/snmp/chkpnt.mib -Oa -v 2c -c public localhost 1.3.6.1.4.1.2620.1.54
CHECKPOINT-MIB::httpsInspectionStatus.0 = STRING: On
CHECKPOINT-MIB::httpsInspectionStatusDescription.0 = STRING: HTTPS Inspection is on
CHECKPOINT-MIB::hsmEnabled.0 = STRING: Enabled
CHECKPOINT-MIB::hsmEnabledDescription.0 = STRING: HSM is enabled for HTTPS inspection with Gemalto HSM
CHECKPOINT-MIB::hsmPartitionAccess.0 = STRING: Accessible
CHECKPOINT-MIB::hsmPartitionAccessDescription.0 = STRING: Gateway can access HSM partition for HTTPS
inspection
CHECKPOINT-MIB::outboundStatus.0 = STRING: HSM on
CHECKPOINT-MIB::outboundStatusDescription.0 = STRING: Outbound HTTPS inspection works with HSM
For more information about SNMP on Gaia OS, see the R81 Gaia Administration Guide > Chapter System
Management > Section SNMP.

Monitoring HTTPS Inspection with HSM in CLI

Run the "cpstat https_inspection" command on the Security Gateway / Cluster Member to see the HTTPS
Inspection status and the status of connection to the HSM Server.
Syntax
cpstat -h
cpstat https_inspection -f {default | hsm_status | all}
For more information about this command, see the R81 CLI Reference Guide > Chapter Security Gateway
Commands > Section cpstat.
Example outputs
[Expert@GW:0]# cpstat https_inspection -f default
HTTPS inspection status (On/Off): On

HTTPS inspection status description: HTTPS Inspection is on
[Expert@GW:0]#
[Expert@GW:0]# cpstat https_inspection -f hsm_status
HSM enabled (Enabled/Disabled): Enabled

HSM enabled description: HSM is enabled for HTTPS inspection with Gemalto HSM
HSM partition access (Accessible/Not Accessible): Accessible
HSM partition access description: Gateway can access to HSM partition for HTTPS inspection
Outbound status (HSM on/HSM off/HSM error): HSM on
Outbound status description: Outbound HTTPS inspection works with HSM
[Expert@GW:0]#
[Expert@GW:0]# cpstat https_inspection -f all
HTTPS inspection status (On/Off): On

HTTPS inspection status description: HTTPS Inspection is on
HSM enabled (Enabled/Disabled): Enabled
HSM enabled description: HSM is enabled for HTTPS inspection with Gemalto HSM
HSM partition access (Accessible/Not Accessible): Accessible
HSM partition access description: Gateway can access to HSM partition for HTTPS inspection
Outbound status (HSM on/HSM off/HSM error): HSM on
Outbound status description: Outbound HTTPS inspection works with HSM
[Expert@GW:0]#

Explanation about the "HTTPS Inspection status"
Possible
Item returned Explanation
strings
HTTPS inspection On HTTPS Inspection feature is configured on the

status (On/Off) Security Gateway / Cluster Member.
Off HTTPS Inspection feature is not configured on the

Explanation about the "HTTPS Inspection status description"
Possible
Item Explanation
returned strings
HTTPS inspection HTTPS HTTPS Inspection feature is configured on the

status description Inspection Security Gateway / Cluster Member.
is on
HTTPS HTTPS Inspection feature is not configured on the

Inspection Security Gateway / Cluster Member.
is off

Explanation about the "HSM configuration status"
Possible
strings
HSM enabled Enabled The value of the :enabled() attribute is set to "yes" in
(Enabled/Disabled) the $FWDIR/conf/hsm_configuration.C file on
Disabled One of these:

Member.
n The $FWDIR/conf/hsm_configuration.C
file does not exist on the Security Gateway /
Cluster Member.
n The value of the :enabled() attribute is set to
"no" in the $FWDIR/conf/hsm_
n The :enabled() attribute is corrupted in the
$FWDIR/conf/hsm_configuration.C file
on the Security Gateway / Cluster Member.
Inspection works without the HSM Server, and
SSL keys are stored on the Security Gateway
(Cluster Members).

Explanation about the "HSM configuration status description"
Possible returned
Item Explanation
strings
HSM enabled HSM is enabled n The value of the :enabled() attribute is set to
description for HTTPS "yes" in the $FWDIR/conf/hsm_
inspection with configuration.C file on the Security Gateway
<HSM Vendor> / Cluster Member.
n The <HSM Vendor> is the value of the ":hsm_
vendor_name ()" attribute in the
$FWDIR/conf/hsm_configuration.C file on
HSM is disabled One of these:

for HTTPS
inspection
Member.
n The $FWDIR/conf/hsm_configuration.C
file does not exist on the Security Gateway /
Cluster Member.
n The HTTPS Inspection daemon wstlsd could not
read the value of the ":enabled()" attribute in the
Inspection works without the HSM Server, and SSL
keys are stored on the Security Gateway (Cluster
Members).
Explanation about the "HSM partition access status"
Possible
Item Explanation
returned strings
HSM partition access N/A Security Gateway / Cluster Member could not
(Accessible/Not check the access to its partition on the HSM
Accessible) Server.
Accessible Security Gateway / Cluster Member could

access its partition on the HSM Server.
Not Security Gateway / Cluster Member could not

Accessible access its partition on the HSM Server because
of an error.
Important - In this case, outbound HTTPS
Inspection does not work, and HTTPS
traffic does not pass through.

Explanation about the "HSM partition access status description"
Item Possible returned strings Explanation
HSM partition HSM partition access Security Gateway / Cluster Member could not
access cannot be checked check the access to its partition on the HSM
description Server.
Most probably, because HSM configuration is
disabled on the Security Gateway / Cluster
Member.
Gateway can access HSM Security Gateway / Cluster Member could

partition for HTTPS access its partition on the HSM Server.
inspection
Gateway cannot access Security Gateway / Cluster Member could not

HSM partition for access its partition on the HSM Server
HTTPS inspection: because of an error.
<Error Message> All these conditions were met:
1. The value of the :enabled() attribute is
Possible error messages are:
n HSM configuration file is
corrupted
n Loading HSM library failed
n There is no trust or no
connectivity with HSM server
n Login to HSM partition failed

HTTPS Inspection does not work, and
HTTPS traffic does not pass through.

Explanation about the "Outbound HTTPS Inspection status"
Possible
strings
Outbound status N / A When the HTTPS Inspection daemon wstlsd starts, it is

(HSM on/HSM necessary to wait for one minute or less, until you can get
off/HSM error) the actual status.
HSM on All these conditions were met:

1. The value of the :enabled() attribute is set to "yes" in
the $FWDIR/conf/hsm_configuration.C file on
2. Security Gateway / Cluster Member could connect to
the HSM Server.
HSM off One of these:

n The HSM Client software packages are not installed
on the Security Gateway / Cluster Member.
n The $FWDIR/conf/hsm_configuration.C file
does not exist on the Security Gateway / Cluster
Member.
n The value of the :enabled() attribute is set to "no" in
$FWDIR/conf/hsm_configuration.C file on the

Inspection works without the HSM Server, and SSL
keys are stored on the Security Gateway (Cluster
Members).
HSM All these conditions were met:

error
1. The value of the :enabled() attribute is set to "yes" in
Important - In this case, outbound HTTPS Inspection
does not work, and HTTPS traffic does not pass
through.
installation. For example, you can get "HSM enabled (Enabled/Disabled) = Enabled"
and "Outbound status (HSM on/HSM off/HSM error) = HSM off", because when
the wstlsd daemon started, or during last policy installation, the HSM configuration was
disabled.

Explanation about the "Outbound HTTPS Inspection status description"
Outbound Cannot get HTTPS When the HTTPS Inspection daemon

status inspection outbound wstlsd starts, it is necessary to wait for
description status. Process may be one minute or less, until you can get the
under initialization. actual status.
Please try again in a
minute.
Outbound HTTPS inspection All these conditions were met:

works with HSM
1. The value of the :enabled()
attribute is set to "yes" in the
$FWDIR/conf/hsm_
configuration.C file on the
Member.
2. Security Gateway / Cluster
Member could connect to the HSM
Server.
Outbound HTTPS inspection The value of the :enabled() attribute is

works without HSM set to "no" in the $FWDIR/conf/hsm_
Gateway / Cluster Member, or this file
does not exist.

Outbound HTTPS inspection All these conditions were met:

is off due to HSM error:
<Error Message> 1. The value of the :enabled()
attribute is set to "yes" in the
$FWDIR/conf/hsm_
configuration.C file on the
Member.
Possible error messages are:
n HSM configuration file is
corrupted
n Loading HSM library
failed
n There is no trust or no
connectivity with HSM
server
n Login to HSM partition
failed
n Error importing CA
certificate from HSM
server
n Error generating key pair
on HSM server

HTTPS Inspection does not work,
and HTTPS traffic does not pass
through.
installation. For example, you can get "HSM enabled (Enabled/Disabled) = Enabled"
and "Outbound status description = Outbound HTTPS inspection works
without HSM", because when the wstlsd daemon started, or during last policy installation,
the HSM configuration was disabled.

ISP Redundancy on a Security Gateway
ISP Redundancy on a Security

Gateway
In This Section:
Introduction 104
ISP Redundancy Modes 108
Outgoing Connections 109
Incoming Connections 110
Important - ISP Redundancy is not supported if Dynamic Routing is configured (Known Limitation
PMTR-68991).
Note - For information about ISP Redundancy on a Cluster, see the R81 ClusterXL Administration
Guide.
Introduction
ISP Redundancy connects a Security Gateway to the Internet through redundant Internet Service Provider
(ISP) links.
ISP Redundancy monitors the ISP links and chooses the best current link.
Notes:
n R81 supports two ISPs.
n ISP Redundancy is intended to traffic that originates on your internal networks and goes to
the Internet.

Example of a typical deployment with a single ISP link
Item Description
1 Internal network
2 Security Gateway
3 ISP
4 Internet

Example of a typical deployment with two dedicated physical interfaces for two ISP links
Best Practice - We recommend this deployment, because it is simpler than deployment with one
> dedicated physical interface.
Item Description
1 Internal network
2 Security Gateway
3 ISP A
4 ISP B
5 Internet

Example of a typical deployment with one dedicated physical interface for two ISP links
If only one external interface is available on the Security Gateway, you can configure two subnets on the
same external interface.
(See the R81 Gaia Administration Guide > Chapter Network Management > Section Network Interfaces >
Section Aliases.)
Both ISP links are then connected to the same Security Gateway interface, but to different next hop routers,
usually through a switch.
Item Description
1 Internal network
2 Security Gateway
3 Switch
4 ISP A
5 ISP B
6 Internet

ISP Redundancy Modes

ISP Redundancy configuration modes control the behavior of outgoing connections from internal clients to
the Internet:
Mode Description
Load Sharing Uses the two links to distribute load of connections.

Connections coming in are alternated.
You can configure best relative loads for the links (set a faster link to handle more
load).
New connections are randomly assigned to a link.
If one link fails, the other link takes the load.
In this mode, incoming connections can reach the application servers through
either ISP link because the Security Gateway can answer DNS requests for the IP
address of internal servers with IP addresses from both ISPs by alternating their
order.
Primary/Backup Uses one link for connections.

It switches to the Backup link if the Primary link fails.
When the Primary link is restored, new connections are assigned to it.
Existing connections continue on the Backup link until they are complete.
In this mode, incoming connections (from the Internet to application servers in the
DMZ or internal networks) also benefit, because the Security Gateway returns
packets using the same ISP Link, through which the connection was initiated.
Best Practice:
n If both ISPs are basically the same, use the Load Sharing mode to ensure that you are
making the best use of both ISPs.
n You may prefer to use one of your two ISPs that is more cost-effective in terms of price and
reliability. In that case, use Primary/Backup mode and set the more cost-effective ISP as
the Primary ISP link.

Outgoing Connections
n In ISP Redundancy Load Sharing mode, outgoing traffic that exits the Security Gateway on its way to
the Internet is distributed between the ISP Links. You can set a relative weight for how much you want
each of the ISP Links to be used.
For example, if one link is faster, it can be configured to route more traffic across that ISP link than the
other.
n In ISP Redundancy Primary/Backup mode, outgoing traffic uses an active primary link.
Hide NAT is used to change the source address of outgoing packets to the address of the interface,
through which the packet leaves the Security Gateway. This allows return packets to be automatically
routed through the same ISP link, because their destination address is the address of the correct link.
Hide NAT is configured by the administrator.

Incoming Connections
For external users to make incoming connections, the administrator must give each application server two
routable IP addresses, one for each ISP. The administrator must also configure Static NAT to translate the
routable addresses to the real server address.
If the servers handle different services (for example, HTTP and FTP), you can use NAT to employ only two
routable IP addresses for all the publicly available servers.
External clients use one of the two addresses. In order to connect, the clients must be able to resolve the
DNS name of the server to the correct IP address.
Note - In the following example, the subnets 172.16.0.0/24 and 192.168.0.0/24 represent public
routable addresses.
In the following example, the Web server www.example.com is assigned an IP address from each ISP:
n 192.168.1.2 from ISP A
n 172.16.2.2 from ISP B
If the ISP Link A is down, then IP address 192.168.1.2 becomes unavailable, and the clients must be able
to resolve the URL www.example.com to the IP address 172.16.2.2.
An incoming connection is established, based on this example, in the following sequence:
1. When an external client on the Internet contacts www.example.com, the client sends a DNS query
for the IP address of this URL.
The DNS query reaches the Security Gateway. The Security Gateway has a built-in mini-DNS server
that can be configured to intercept DNS queries (of Type A) for servers in its domain.
2. A DNS query arriving at an interface that belongs to one of the ISP links, is intercepted by the Security
Gateway.
3. If the Security Gateway recognizes the name of the host, it sends one of the following replies:
n In ISP Redundancy Primary/Backup mode, the Security Gateway replies only with the IP
addresses associated with the Primary ISP link, as long as the Primary ISP link is active.
n In ISP Redundancy Load Sharing mode, the Security Gateway replies with two IP addresses,
alternating their order.
4. If the Security Gateway is unable to handle DNS requests (for example, it may not recognize the host
name), it passes the DNS query to its original destination or the DNS server of the domain
example.com.
5. When the external client receives the reply to its DNS query, it opens a connection. Once the packets
reach the Security Gateway, the Security Gateway uses Static NAT to translate the destination IP
address 192.168.1.2 or 172.16.2.2 to the real server IP address 10.0.0.2.
6. The Security Gateway routes the reply packets from the server to the client through the same ISP link
that was used to initiate the connection.

Configuring ISP Redundancy on a Security Gateway
Configuring ISP Redundancy on a Security

Gateway
1. Connect with SmartConsole to the Security Management Server or Domain Management Server that
manages this Security Gateway.
2. From the left navigation panel, click Gateways & Servers.
3. Open the Security Gateway object.
4. Click Other > ISP Redundancy.
5. Select Support ISP Redundancy.
6. Select the redundancy mode - Load Sharing or Primary/Backup.
7. Configure the ISP Links.
Procedure
Make sure you have the ISP data - the speed of the link and next hop IP address.
Automatic vs Manual configuration:
n If the Security Gateway object has two interfaces with Topology "External" in the Network
Management page, you can configure the ISP links automatically.
Configuring ISP links automatically
a. Click Other > ISP Redundancy.

b. Click Set initial configuration.
The ISP Links are added automatically.
c. For Primary/Backup mode, make sure the Primary interface is first in the list. Use
the arrows on the right to change the order.
d. Click OK.

n If the Security Gateway object only one interface with Topology "External" in the Network
Management page, you must configure the ISP links manually.
Configuring ISP links manually

b. In the IPS Links section, click Add.
The ISP Link window opens.
c. Click the General tab.
d. In the Name field, enter a name of this link (desired text).
The name you enter here is used in the ISP Redundancy commands (see
"Controlling ISP Redundancy from CLI" on page 117).
e. Select the Interface of the Security Gateway for this ISP link.
l If the Security Gateway object has two interfaces with Topology "External"
in the Network Management page, set each ISP link to a different interface.
If one of the ISP links is the connection to a backup ISP, configure the ISP
Redundancy Script (see "Controlling ISP Redundancy from CLI" on
page 117).
l If the Security Gateway object only one interface with Topology "External" in
the Network Management page, set each ISP link to connect to this
interface.
f. Configure the Next Hop IP Address.
l If the Security Gateway object has two interfaces with Topology "External"
in the Network Management page, leave this field empty and click Get from
routing table. The next hop is the default gateway.
l If the Security Gateway object only one interface with Topology "External" in
the Network Management page, set each ISP link to a different next hop
router.
g. For ISP Redundancy in Load Sharing mode, enter the Weight value.
For equal traffic distribution between the two IPS link, enter 50 in each ISP link.
If one ISP link is faster, increase this value and decrease it for the other ISP link, so
that the sum of these two values is always equal 100.
h. Click the Advanced tab.
i. Define hosts to be monitored, to make sure the link is working.
Add the applicable objects to the Selected hosts section.
j. Click OK.
8. Configure the Security Gateway to be the DNS server.

Procedure
The Security Gateway, or a DNS server behind it, must respond to DNS queries.
It resolves IP addresses of servers in the DMZ (or another internal network).

Get a public IP address from each ISP.

If public IP addresses are not available, register the domain to make the DNS server accessible
from the Internet.
The Security Gateway intercepts DNS queries "Type A" for the web servers in its domain that
come from external hosts.
n If the Security Gateway recognizes the external host, it replies:
l In ISP Redundancy Load Sharing mode, the Security Gateway replies with two IP
addresses, alternating their order.
l In ISP Redundancy Primary/Backup mode, the Security Gateway replies with the IP
addresses of the active ISP link.
n If the Security Gateway does not recognize the host, it passes the DNS query on to the
original destination, or to the domain DNS server.
To enable the DNS server:

b. Select Enable DNS Proxy.
c. Click Configure.
d. Add your DMZ or Web servers. Give each server two public IP addresses - one from each
ISP.
e. In the DNS TTL, enter a number of seconds.
This sets a Time To Live for each DNS reply.
DNS servers in the Internet cannot cache your DNS data in the reply for longer than the
TTL.
f. Click OK.
g. Configure Static NAT to translate the public IP addresses to the real server's IP address.
External clients use one of the two IP addresses.
Note - If the servers use different services (for example, HTTP and FTP), you can
use NAT for only two public IP addresses.
h. Define an Access Control Policy rule:
Services &
Destinatio Install
Name Source VPN Application Action Track
n On
s
DNS Proxy Applicable Applicable DNS Any domain_udp Accept None Policy
sources Servers Targets

To register the domain and get IP addresses:

a. Register your domain with the two ISP.
b. Tell the ISP the two IP addresses of the DNS server that respond to DNS queries for the
domain.
c. For each server in the DMZ, get two public IP addresses, one from each ISP.
d. In SmartConsole, click Menu > Global properties.
e. From the left tree, click NAT - Network Address Translation.
f. In the Manual NAT rules section, select Translate destination on client side.
g. Click OK.
9. Configure the Access Control Policy for ISP Redundancy.

Procedure
The Access Control Policy must allow connections through the ISP links, with Automatic Hide NAT
on network objects that start outgoing connections.
a. In the properties of the object for an internal network, select NAT > Add Automatic Address
Translation Rules.
b. Select Hide behind the gateway.
c. Click OK.

d. Define rules for publicly reachable servers (Web servers, DNS servers, DMZ servers).
n If you have one public IP address from each ISP for the Security Gateway, define
Static NAT.
Allow specific services for specific servers.
For example, make NAT rules, so that incoming HTTP connections from the two ISPs
reach a Web server, and DNS traffic from the ISP reach the DNS server.
Example: Manual Static Rules for a Web Server and a DNS Server
Origi Origin Translat Transla

Original Transla Inst
nal al ed ted Comm
Destinat ted all
Sourc Servic Destinat Service ent
ion Source On
e es ion s
Any Host object http = S 50.50.50.2 = Polic Incoming

with IP Original Original y Web - ISP
address of Targe A
Web Server ts
Any Host object http = S 60.60.60.2 = Polic Incoming

with IP Original Original y Web - ISP
address of Targe B
Web Server ts
Any Host object domain_ = S 50.50.50.3 = Polic Incoming

with IP udp Original Original y DNS - ISP
address of Targe A
DNS Server ts
Any Host object domain_ = S 60.60.60.3 = Polic Incoming

with IP udp Original Original y DNS - ISP
address of Targe B
DNS Server ts
n If you have a public IP address from each ISP for each publicly reachable server (in
addition to the Security Gateway), define NAT rules:
i. Give each server a private IP address.
ii. Use the public IP addresses in the Original Destination.
iii. Use the private IP address in the Translated Destination.
iv. Select Any as the Original Service.
Note - If you use Manual NAT, then automatic ARP does not work for the IP addresses
behind NAT. You must configure the local.arp file as described in sk30197.
10. Install the Access Control Policy on this Security Gateway object.

ISP Redundancy and VPN
ISP Redundancy and VPN

Note - ISP Redundancy settings override the VPN Link Selection settings.
When ISP Redundancy is enabled, VPN encrypted connections survive a failure of an ISP link.
The settings in the ISP Redundancy page override settings in the IPsec VPN > Link Selection page.
Configuring ISP Redundancy for VPN with a Check Point peer
Step Instructions
1 Connect with SmartConsole to the Security Management Server or Domain Management

Server that manages this Security Gateway.
2 From the left navigation panel, click Gateways & Servers.
3 Open the Security Gateway object.
4 In the left navigation tree, go to Other > ISP Redundancy.
5 Select Apply settings to VPN traffic.
6 In the left navigation tree, go to IPsec VPN > Link Selection.
7 Make sure that Use ongoing probing. Link redundancy mode shows the mode of the ISP
Redundancy:
High Availability (for Primary/Backup) or Load Sharing.
The VPN Link Selection now only probes the ISP configured in ISP Redundancy.
Configuring ISP Redundancy for VPN with a third-party peer
If the VPN peer is not a Check Point Security Gateway, the VPN may fail, or the third-party device may
continue to encrypt traffic to a failed ISP link.
n Make sure the third-party VPN peer recognizes encrypted traffic from the secondary ISP link as
coming from the Check Point cluster.
n Change the configuration of ISP Redundancy to not use these Check Point technologies:
l Use Probing - Makes sure that Link Selection uses another option.
l The options Load Sharing, Service Based Link Selection, and Route based probing work
only on Check Point Security Gateways and Clusters.
If used, the Security Gateway or Cluster Members use one link to connect to the third-party
VPN peer.
The link with the highest prefix length and lowest metric is used.

Controlling ISP Redundancy from CLI
Controlling ISP Redundancy from CLI

You can control the ISP Redundancy behavior from CLI.
Force ISP Link State

Use the "fw isp_link" command to force the ISP link state to Up or Down.
Use this to test installation and deployment, or to force the Security Gateway to recognize the true link state
if it cannot (the ISP link is down but the gateway sees it as up).
n You can run this command on the Security Gateway:
fw isp_link <Name of ISP Link in SmartConsole> {up | down}
n You can run this command on the Security Management Server:
fw isp_link <Name of Security Gateway Object> <Name of ISP Link in

SmartConsole> {up | down}
For more information, see the R81 CLI Reference Guide > Chapter Security Gateway Commands - Section
fw - Section fw isp_link.
The ISP Redundancy Script

When the Security Gateway starts, or an ISP link state changes, the $FWDIR/bin/cpisp_update script
runs on the Security Gateway.
This script changes the default route of the Security Gateway.
Warning - We do not recommend that you make any changes in this script.

Mirror and Decrypt
Mirror and Decrypt

The Mirror and Decrypt feature performs these actions on your Security Gateway, or Cluster:
Action Description
Only mirror of all Your Security Gateway or Cluster clones all traffic (including HTTPS without
traffic decryption) that passes through it, and sends it out of the designated physical
interface.
Mirror and Your Security Gateway or Cluster clones all HTTPS traffic that passes through it,
Decrypt of decrypts it, and sends it in clear-text out of the designated physical interface.
HTTPS traffic Note - If you wish to decrypt the HTTPS traffic, you must enable and configure
the HTTPS Inspection on your Security Gateway, or Cluster.
You can add a third-party Recorder or Packet-Broker in your environment and forward to it the traffic that
passes through your Security Gateway, or Cluster.
This Recorder or Packet-Broker must work in monitor (promiscuous) mode to accept the decrypted and
mirrored traffic from your Security Gateway, or Cluster.
Security Gateway, or Cluster works only with one Recorder, which is directly connected to a designated
physical network interface (NIC) on the Check Point Gateway, or Cluster Members.
Example Topology and Traffic Flow:

Mirror and Decrypt
Item Description
1 First network that sends and receives traffic through the Security Gateway (2).
2 Security Gateway, through which networks (1) and (3) send and receive their traffic.
3 Second network that sends and receives traffic through the Security Gateway (2).
4 Designated physical interface on the Security Gateway (2).
5 Recorder, or Packet-Broker that works in a monitor (promiscuous) mode.
A Traffic flow between the first network (1) and the Security Gateway (2).
B Traffic flow between the second network (3) and the Security Gateway (2).
C Flow of the decrypted and mirrored traffic from the Security Gateway (2) to the Recorder, or
Packet-Broker (5).
Source MAC address of the decrypted and mirrored packets
Source MAC address of the decrypted

Traffic and mirrored packets the Security Gateway
and Cluster Members send
Mirror only of all traffic MAC address of the designated physical interface.
Mirror and Decrypt of HTTPS traffic 00:00:00:00:00:00:

Mirror and Decrypt Requirements
Mirror and Decrypt Requirements

Item Description
1 Designated network interface for Mirror and Decrypt:

a. Select a designated physical interface on your Security Gateway, or each cluster
member.
Important:
n On cluster members, you must select an interface with the same name (for
example, eth3 on each cluster member).
n Select an interface with the largest available throughput (for example, 10G,
40G), because this interface passes the combined traffic from all other
interfaces.
b. Assign a dummy IP address to the designated interface.
Important - This IP address cannot collide with other IP addresses used in your
environment. This IP address cannot belong to subnets used in your environment.
Make sure to configure the correct subnet mask. After you enable traffic mirroring
on this interface in SmartConsole, all other traffic that is routed to this interface is
dropped.
c. On cluster members, you must configure this designated physical interface in the
$FWDIR/conf/discntd.if file.
Note - This prevents the interfaces that are not used from sending Cluster Control
Protocol (CCP) packets that can overwhelm the Mirror and Decrypt recorders.
2 Maximum Transmission Unit (MTU) on the Mirror and Decrypt designated physical interface:
n MTU value has to be 1500 (default), or at least the maximum MTU value from other
interfaces on the Security Gateway.
3 HTTPS Inspection for decrypting the HTTPS traffic:

n You must enable the HTTPS Inspection in SmartConsole in the object of the Security
Gateway, Cluster, or VSX Virtual System.
n You must configure the HTTPS Inspection Rule Base.
4 Access Rules for traffic you wish to Mirror and Decrypt:

n You must create special rules in the Access Control Policy for the traffic you wish to
mirror and decrypt.

Configuring Mirror and Decrypt in Gateway mode
Configuring Mirror and Decrypt in Gateway

mode
Example topology:
Item Description
1 Security Gateway, through which your networks send and receive their traffic.
3 Flow of the decrypted and mirrored traffic from the Security Gateway (1) to the Recorder, or
Packet-Broker (2).
eth4 Designated physical interface on the Security Gateway (1).
Workflow for configuring Mirror and Decrypt in Gateway mode:
Step Instructions
1 Read and follow the "Mirror and Decrypt Requirements" on page 120.
2 Prepare the Security Gateway, or each cluster member.

See "Preparing the Security Gateway or each Cluster Member" on page 122.
3 Configure the Mirror and Decrypt in the Security Gateway, or Cluster object in SmartConsole.
See "Configuring Mirror and Decrypt in SmartConsole for Gateway Mode" on page 123.

Preparing the Security Gateway or each Cluster Member
Preparing the Security Gateway or each Cluster Member

Step Instructions
1 Select a designated physical interface for Mirror and Decrypt on the Security Gateway, or
each cluster member.
Important - On cluster members, you must select an interface with the same name (for
example, eth3 on each cluster member).
2 Configure a dummy IP address on this designated physical interface.

Important - This IP address cannot collide with other IP addresses used in your
environment. This IP address cannot belong to subnets used in your environment. Make
sure to configure the correct subnet mask. After you enable traffic mirroring on this
interface in SmartConsole, all other traffic that is routed to this interface is dropped.
For instructions about configuring an IP address on a physical interface, see the R81 Gaia
Administration Guide - Chapter Network Management - Section Network Interfaces - Section
Physical Interfaces.
3 Configure the required Maximum Transmission Unit (MTU) on this designated physical
interface.
MTU has to be the default 1500, or at least the maximal MTU value from other interfaces on
the Security Gateway.
For instructions about configuring an MTU on a physical interface, see the R81 Gaia
4 Important - On cluster members, you must configure this designated physical interface in
the $FWDIR/conf/discntd.if file on each Cluster Member.
a. Connect to the command line on each Cluster Member.

c. Create the $FWDIR/conf/discntd.if file:
touch $FWDIR/conf/discntd.if
d. Edit the $FWDIR/conf/discntd.if file in the Vi editor:
vi $FWDIR/conf/discntd.if
e. Write the name of the designated physical interface. After the interface name, you must
press Enter.
Note - Comments are not allowed in this file.
f. Save the changes in the file and exit the editor.
Note - To apply the configuration from the file and make it persistent, install an Access
Control Policy on the cluster object. You install the Access Control Policy later, after the
required configuration steps in the SmartConsole.

Configuring Mirror and Decrypt in SmartConsole for Gateway Mode
Configuring Mirror and Decrypt in SmartConsole for

Gateway Mode
Workflow for Security Gateway, or Cluster in Gateway mode:
1. Enable the HTTPS Inspection in the object of your Security Gateway, or Cluster (for decrypting the
HTTPS traffic).
Procedure
Step Instructions
a Connect with SmartConsole to the Management Server.
b From the left navigation panel, click Gateways & Servers.
c Open the object of the Security Gateway, or Cluster.
d From the navigation tree, click HTTPS Inspection.
e View and export the certificate.
f Check Enable HTTPS Inspection.
g Click OK.
2. Configure the HTTPS Inspection Rule Base (for decrypting the HTTPS traffic).
Procedure
Step Instructions
a From the left navigation panel, click Security Policies.
b From the left tree, click HTTPS Inspection.
d Configure the HTTPS Inspection Rule Base.

See R81 Security Management Administration Guide.
For more settings, in the HTTPS Tools section, click Additional Settings.
e Publish the SmartConsole session.
3. Activate the Mirror and Decrypt in the object of your Security Gateway, or Cluster.
Procedure
Step Instructions
a From the left navigation panel, click Gateways & Servers.
b Open the object of the Security Gateway, or Cluster.

Step Instructions
c From the left tree, click Network Management.
d From the top toolbar, click Get Interfaces Without Topology.
e Make sure the interface designated for Mirror and Decrypt is listed with the dummy
IP address.
f Select the interface designated for Mirror and Decrypt and click Edit.
g From the navigation tree, click General.
h In the General section:

In the Network Type field, select Private.
Note - This field shows only in Cluster objects.
i In the Topology section:

Click Modify. The Topology Settings window opens.
j In the Leads To section:

i. Select Override.
ii. Select This Network (Internal).
iii. Select Network defined by the interface IP and Net Mask.
k In the Security Zone section:

i. Select User defined.
ii. Do not check the Specify Security Zone.
l In the Anti-Spoofing section:

Clear the Perform Anti-Spoofing based on interface topology.
m Click OK to save the changes and close the Topology Settings window.
n From the navigation tree of the Security Gateway, or Cluster object:

Click the [+] near the Other and click Mirror and Decrypt.
o Check Mirror gateway traffic to interface.

The Mirror and Decrypt - User Disclaimer window opens.
i. Read the text carefully.
ii. Check I agree to the terms and conditions.
iii. Click OK to accept and close the disclaimer.
p In the Mirror gateway traffic to interface field, select the designated physical
interface.
q Click OK to save the changes and close the Security Gateway, or Cluster properties
window.
4. Configure the Mirror and Decrypt rules in the Access Control Policy for the traffic you wish to mirror
and decrypt.

Procedure
Best Practice - We recommend you to configure a new separate Access Control Layer
to contain Mirror and Decrypt rules. Alternatively, you can configure the Mirror and
>
Decrypt rules in the regular Rule Base.
Important - When you configure the Mirror and Decrypt rules, these limitations apply:
n In the Mirror and Decrypt rules, you must not select Content criteria, such as
Application, URL Filtering, Service matched by IP Protocol, Content Awareness.
n Above the Mirror and Decrypt rules, you must not configure other rules that
contain Content criteria, such as Application, URL Filtering, Service matched by
IP Protocol, Content Awareness.
n You must configure rules that contain an excluded source or an excluded
destination above the Mirror and Decrypt rules.
The Name column of these rules cannot contain these strings: <M&D>, <M&d>,
<m&D>, or <m&d>.
The procedure below describes how to configure the Mirror and Decrypt rules in a separate
Access Control Layer in SmartConsole:
Step Instructions
b Create a new Access Control Layer in the Access Control Policy.
c In SmartConsole top left corner, click Menu > Manage policies and layers.
d Select the existing policy and click Edit (the pencil icon).
Alternatively, create a new policy.
e From the navigation tree of the Policy window, click General.
f In the Policy Types section, make sure you select only the Access Control.
g In Access Control section, click on the + (plus) icon. A pop up window opens.
h In the top right corner of this pop up window, click New Layer.
The Layer Editor window opens.
i From the navigation tree of the Layer Editor window, click General.
j In the Blades section, make sure you select only the Firewall.
k On other pages of the Layer Editor window, configure additional applicable settings.
Click OK.
l In the Access Control section, you see the Network Layer and the new Access
Control Layer.
m Click OK to save the changes and close the Policy window.
n In SmartConsole, at the top, click the tab of the applicable policy.

Step Instructions
o In the Access Control section, click the new Access Control Layer.
In the default rule, you must change the Action column from Drop to Accept to
not affect the policy enforcement:
n Name - Your text
Important - You cannot use these strings:

<M&D>, <M&d>, <m&D>, or <m&d>
n Source - *Any
n Destination - *Any
n VPN - *Any
n Services & Applications - *Any
n Action - Must contain Accept
n Track - None
n Install On - *Policy Targets
p Above the existing Cleanup rule, add the applicable rules for the traffic you wish to
Mirror and Decrypt.
You must configure the Mirror and Decrypt rules as follows:
n Name - Must contain one of these strings (the angle brackets <> are
mandatory):
l <M&D>
l <M&d>
l <m&D>
l <m&d>
n Source - Select the applicable objects

n Destination - Select the applicable objects
n VPN - Must leave the default *Any
n Services & Applications - Select the applicable services (to decrypt the
HTTPS traffic, select the applicable HTTP, HTTPS, or Proxy services)
n Track - Select the applicable option (None, Log, or Alert)
n Install On - Must contain one of these objects:
l *Policy Targets (this is the default)
l The Security Gateway, or Cluster object, whose version is R80.20 or
higher
Important:
n In the Mirror and Decrypt rules, you must not select Content criteria,
such as Application, URL Filtering, Service matched by IP Protocol,
Content Awareness.
n Above the Mirror and Decrypt rules, you must not configure other rules
that contain Content criteria, such as Application, URL Filtering, Service
matched by IP Protocol, Content Awareness.
The Name column of these rules cannot contain these strings: <M&D>,
<M&d>, <m&D>, or <m&d>.
q Publish the SmartConsole session.

Step Instructions
r Install the Access Control Policy.
s If in a Mirror and Decrypt rule you set the Track to Log, then you can filter the logs for
this rule by the Access Rule Name, which contains the configured string:
<M&D>, <M&d>, <m&D>, or <m&d>.

Configuring Mirror and Decrypt in VSX mode

Example topology for one Virtual System:
Item Description
1 VSX Gateway.
3 Virtual System, through which your networks send and receive their traffic.
4 Flow of the decrypted and mirrored traffic from the VSX Gateway (1) to the Recorder, or
Packet-Broker (2).
eth4 Designated physical interface on the VSX Gateway (1).

Virtual System (3) connects directly to this physical interface.
wrp128 One of the virtual interfaces on the Virtual System (3).

Example topology for several Virtual Systems:

Note - This topology requires you to configure a VLAN Trunk on the Recorder or Packet-Broker.
The VLAN Trunk on the Recorder or Packet-Broker must accept all VLAN IDs that you configure
in the objects of the applicable Virtual Systems in SmartConsole.
Item Description
1 VSX Gateway.
2 First Virtual System, through which your networks send and receive their traffic.
3 Second Virtual System, through which your networks send and receive their traffic.
4 Flow of the decrypted and mirrored traffic from the VSX Gateway (1) to the Recorder, or
Packet-Broker (5).
5 Recorder, or Packet-Broker.
eth4 Designated physical interface on the VSX Gateway (1).

This interface is configured as VLAN Trunk in the VSX Gateway object in SmartConsole.
Virtual Systems (2 and 3) connect to this VLAN Trunk interface with VLAN interfaces.
eth4.55 VLAN interface on the first Virtual System (2).
eth4.66 VLAN interface on the second Virtual System (3).
wrp128 One of the virtual interfaces on the Virtual Systems (2 and 3).
Important - It is not supported to change the designated physical interface with the "vsx_util
change_interfaces" command. For information about this command, see the R81 VSX
Administration Guide.

Workflow for configuring Mirror and Decrypt in VSX mode:
Step Instructions
1 Read and follow the "Mirror and Decrypt Requirements" on page 120.
2 Prepare the VSX Gateway, or each VSX Cluster Member.

See "Preparing the VSX Gateway or each VSX Cluster Member" on page 131.
3 Configure the Mirror and Decrypt in the Virtual System object in SmartConsole.
See:
n "Configuring Mirror and Decrypt in SmartConsole for One Virtual System" on
page 132.
n "Configuring Mirror and Decrypt in SmartConsole for Several Virtual Systems" on
page 137.

Preparing the VSX Gateway or each VSX Cluster Member
Preparing the VSX Gateway or each VSX Cluster Member

Item Description
1 Select a designated physical interface for Mirror and Decrypt on the VSX Gateway, or each
VSX Cluster Member.
Important - On VSX Cluster Members, you must select an interface with the same name
(for example, eth3 on each VSX Cluster Member).
2 Do not configure an IP address on this designated physical interface.
3 Configure the required Maximum Transmission Unit (MTU) on this designated physical
interface.
MTU has to be the default 1500, or at least the maximal MTU value from other interfaces on
the VSX Gateway, or VSX Cluster Member.
For instructions about configuring an MTU on a physical interface, see R81 Gaia
4 Important - In VSX Cluster, you must configure this designated physical interface in the
$FWDIR/conf/discntd.if file on each VSX Cluster Member.

c. Go to the context of the Virtual System 0:
vsenv 0
Output shows:
Context is set to Virtual Device <Name of VSX Gateway> (ID
0).
d. Create the $FWDIR/conf/discntd.if file:
touch $FWDIR/conf/discntd.if
e. Edit the $FWDIR/conf/discntd.if file in the Vi editor:
vi $FWDIR/conf/discntd.if
f. Write the name of the designated physical interface. After the interface name, you must
press Enter.
Note - Comments are not allowed in this file.
g. Save the changes in the file and exit the Vi editor.
Note - To apply the configuration from the file and make it persistent, install an Access
Control Policy on the VSX Cluster object. You install the Access Control Policy later, after
the required configuration steps in the SmartConsole.

Configuring Mirror and Decrypt in SmartConsole for One Virtual System
Configuring Mirror and Decrypt in SmartConsole for One

Virtual System
Workflow for one Virtual System:
1. Enable the HTTPS Inspection in the object of the Virtual System (for decrypting the HTTPS traffic).
Procedure
Step Instructions
c Open the Virtual System object.
g Click OK.
Procedure
Step Instructions

3. Add the designated physical interface in the object of the Virtual System.
Procedure
Step Instructions
a In SmartConsole, open the Virtual System object.
b From the navigation tree, click Topology.

Step Instructions
c From the top toolbar, click New > Regular.
d On the General tab:

i. In the Interface field, select the designated physical interface.
ii. In the IPv4 Configuration section:
n In the IP Address field, enter a dummy IP address.
n In the Net Mask field, enter the applicable net mask.
Important - This IP address cannot collide with other IP

addresses used in your environment. This IP address
cannot belong to subnets used in your environment. Make
sure to configure the correct subnet mask. After you
enable traffic mirroring on this interface in SmartConsole,
all other traffic that is routed to this interface is dropped.
iii. Do not check the Propagate route to adjacent Virtual Devices
(IPv4).
iv. In the MTU field, enter the applicable MTU.
See "Mirror and Decrypt Requirements" on page 120.
v. In the Security Zone field, leave the default None.
vi. Click OK.
4. Activate the Mirror and Decrypt in the object of the Virtual System.
Procedure
Step Instructions
b Open the Virtual System object.
c From the left tree, click the [+] near the Other and click Mirror and Decrypt.
d Check Mirror gateway traffic to interface.

e In the Mirror gateway traffic to interface field, select the designated physical
interface.
f Click OK to save the changes and close the Virtual System properties window.
and decrypt.
Procedure
>

<m&D>, or <m&d>.
Step Instructions
Click OK.
Control Layer.

Step Instructions
n Name - Your text

<M&D>, <M&d>, <m&D>, or <m&d>
n Source - *Any
n VPN - *Any
n Track - None
Mirror and Decrypt.
mandatory):
l <M&D>
l <M&d>
l <m&D>
l <m&d>

higher
Important:
Content Awareness.
<M&d>, <m&D>, or <m&d>.

Step Instructions
<M&D>, <M&d>, <m&D>, or <m&d>.

Configuring Mirror and Decrypt in SmartConsole for Several Virtual Systems
Configuring Mirror and Decrypt in SmartConsole for Several

Virtual Systems
Workflow for several Virtual Systems:
1. Enable the HTTPS Inspection in the objects of applicable Virtual Systems (for decrypting the HTTPS
traffic).
Procedure
Step Instructions
c Open the Virtual System object.
g Click OK.
Procedure
Step Instructions

3. Define the designated physical interface as VLAN Trunk in the object of the VSX Gateway, or VSX
Cluster.
Procedure
Note - If the Recorder or Packet-Broker connects to the VSX Gateway, or VSX Cluster
members through a Switch, configure a VLAN Trunk on the applicable Switch port. The
VLAN Trunk port on the Switch must accept all VLAN IDs that you configure in the
applicable Virtual Systems.

Step Instructions
1 In SmartConsole, open the object of the VSX Gateway, or VSX Cluster.
2 From the navigation tree, click Physical Interfaces.
3 Check the box VLAN Trunk near the designated physical interface.
4 Click OK.
4. Add the designated physical interface in the object of each applicable Virtual System.
Procedure
Step Instructions
a In SmartConsole, open the Virtual System object.
b From the navigation tree, click Topology.
c From the top toolbar, click New > Regular.
d On the General tab:

i. In the Interface field, select the designated physical interface.
ii. In the IPv4 Configuration section:
n In the IP Address field, enter a dummy IP address.
n In the Net Mask field, enter the applicable net mask.
Important - This IP address cannot collide with other IP

addresses used in your environment. This IP address
cannot belong to subnets used in your environment. Make
sure to configure the correct subnet mask. After you
enable traffic mirroring on this interface in SmartConsole,
all other traffic that is routed to this interface is dropped.
iii. Do not check the Propagate route to adjacent Virtual Devices
(IPv4).
iv. In the MTU field, enter the applicable MTU.
See "Mirror and Decrypt Requirements" on page 120.
v. In the Security Zone field, leave the default None.
vi. Click OK.
5. Activate the Mirror and Decrypt in the object of each applicable Virtual System.
Procedure
Step Instructions
b Open the Virtual System object.
c From the left tree, click the [+] near the Other and click Mirror and Decrypt.

Step Instructions
d Check Mirror gateway traffic to interface.

e In the Mirror gateway traffic to interface field, select the designated physical
interface.
f Click OK to save the changes and close the Virtual System properties window.
and decrypt.
Procedure
>
<m&D>, or <m&d>.
Step Instructions

Step Instructions
Click OK.
Control Layer.
n Name - Your text

<M&D>, <M&d>, <m&D>, or <m&d>
n Source - *Any
n VPN - *Any
n Track - None

Step Instructions
Mirror and Decrypt.
mandatory):
l <M&D>
l <M&d>
l <m&D>
l <m&d>

higher
Important:
Content Awareness.
<M&d>, <m&D>, or <m&d>.
<M&D>, <M&d>, <m&D>, or <m&d>.

Mirror and Decrypt Logs
Mirror and Decrypt Logs

To Mirror and Decrypt the traffic, you create special rules in the Access Control Policy.
The Mirror and Decrypt feature adds the applicable information to the regular Security Gateway logs.
To see the Mirror and Decrypt logs in SmartConsole:
Item Description
1 Connect with SmartConsole to the Management Server.
2 From the left navigation panel, click Logs & Monitor > Logs.
3 In the search field, enter:

type:Control
4 Double-click on the log and refer to the More section.
The Mirror and Decrypt logs show this information in the More section > Mirror and Decrypt field:
Action Description
Mirror only Security Gateway only mirrored the traffic.
Decrypt and mirror Security Gateway decrypted and mirrored the HTTP / HTTPS traffic
Note - This can be the case even for a clear-text HTTP connection, because the
HTTPS Inspection inspects it first (example is all connections that use proxy
8080).
Partial mirroring Security Gateway started to decrypt the traffic, but stopped later due to a
(HTTPS inspection Bypass rule (for example, a rule with a Category).
Bypass) Therefore, the mirrored connection is not complete.

ConnectControl - Server Load Balancing
ConnectControl - Server Load

Balancing
ConnectControl is a Check Point solution for balancing the traffic that passes through Check Point Security
Gateway or Cluster towards servers behind the Check Point Security Gateway or Cluster.
ConnectControl does not consume more memory or CPU processing power on Security Gateway or Cluster
Members.
ConnectControl Packet Flow

Load-balanced servers are represented by one Virtual IP address.
In SmartConsole, you define a Logical Server object that represents a group of physical servers.
The Logical Server takes service requests for the load-balanced application and directs the requests to the
applicable physical server.
When a client requests access to an application that is load balanced by ConnectControl, the request goes
through the Security Gateway or Cluster.
Item Description
1 Client request - A client starts a connection with the logical IP address of the application
server (the address assigned to the Logical server).
2 Internet - The service request goes through the Internet.
3 Security Gateway - The service request arrives at the destination public IP address of the
Logical Server, which is on the Security Gateway. The request is matched to the Logical
Server rule in the Rule Base. The Security Gateway directs the request to the internal IP
address of the Logical Server group.
4 Logical Server - ConnectControl determines which server in the Logical Server group is best
for the request, based on the selected load-balancing method.
Note - Make sure that rules that allow traffic for services to ConnectControl Logical Servers and
that server groups are before Access Control Policy rules that allow traffic for those services.

Configuring ConnectControl
This procedure explains the steps to set up ConnectControl in your environment.
Procedure
1. In the SmartConsole, click Objects menu > Object Explorer (or press Ctrl+E).
2. Define a Host object for each of the servers that will be load-balanced.
In the Object Explorer, from the toolbar, click New > Host.
3. Define a Network Group object to contain all Host objects for each of the servers that will be load-
balanced.
Instructions
In the Object Explorer, from the toolbar, click New > Network Group.
a. Name the group (for example, HTTP_Server_Group).
b. Add the Host objects for each of the servers.
Best Practice - We recommend adding no more than 29 objects.
4. Define the Logical Server object.

Instructions
a. In the Object Explorer, from the toolbar, click New > Network Object > More > Logical
Server.
b. In the New Logical Server window, enter a name for the ConnectControl Logical Server.
c. Enter a Virtual IP address.
Make sure the IP address is a public IP address.
All traffic to be load-balanced, must be directed through the cluster.
Note for a cluster environment
If the assigned IP address is on the same subnet as a Cluster Virtual IP address, you
also need to configure a Manual ARP proxy entry for this IP address.
i. Click Menu >Global properties > NAT - Network Address Translation.
ii. Select Merge manual proxy ARP configuration.
iii. Click OK.
iv. Configure the $FWDIR/conf/local.arp file as described in sk30197.
v. Install the Access Control Policy on this cluster object.

d. Select the Server type.

Logical Server Types
When you create the Logical server object, configure the server type as HTTP or
Other. This distinction is important. ConnectControl handles the connection to the
client differently for each server type.
n The HTTP server type uses HTTP redirection.
This type supports offsite HTTP servers and form-based applications, but only
works with the HTTP protocol. An HTTP Logical server makes sure that all
HTTP-connection sessions are directed to one server, which is a requirement
for many Web applications. ConnectControl finds the correct physical server,
behind the Security Gateway or offsite, based on the selected load-balancing
method. The session connections continue to go to that one server.
n The Other server type uses NAT (address translation) to send traffic to the
grouped servers.
This Logical server supports all protocols (including HTTP) and gives the most
effectively balanced load. It requires servers to be NATed by the Security
Gateway. ConnectControl mediates each service request and then selects the
server to get that request. It uses NAT to change the destination IP address of
the incoming packet. If a return connection is opened, the connection is
automatically established between the server and the client. The server's
source address in the packet is translated to the IP address of the Logical
server. On the packet's return, the Security Gateway translates the packet's
original address to the IP address of the Logical server.
e. Select the Server group.

Select the Server Group object that you defined earlier (or define a new Server Group
object).
The members of the group must be hosts, Security Gateways, or OSE devices.
f. Select Use persistent server mode that fits your environment.
Persistency
This setting maintains a client's connection to the server that ConnectControl first
selected.
n Persistency by server is useful for HTTP applications, such as forms, in a load-
balanced environment with multiple Web servers. ConnectControl directs an
HTTP client to one server for all requests. This allows clients to fill forms without
the data loss that occurs if different servers take the requests.
n Persistency by service is useful if you are load balancing multiple services in
your server group. For example, in a redundant environment of two servers,
each running HTTP and FTP, ConnectControl directs traffic from one client to
the server of the correct service. This prevents heavy load on one server, which
can happen with Persistency by server.

Item Description
1 Multiple client requests for HTTP and FTP.
2 Internet.
3 Security Gateway.
The service requests arrive at the destination public IP address of the
Logical Server, which is on the Security Gateway.
The Security Gateway directs the requests to the internal IP address of
the Logical Server group.
4 Logical Server group with two servers, each with FTP and HTTP
services.
ConnectControl balances the load between the servers.
g. Select a Balance method that fits your environment.

Load Balancing Methods
ConnectControl distributes network traffic to load-balanced servers according to one

of these predefined balancing methods:
Method Description
Random The Security Gateway directs service requests to servers at

random.
This method is a good choice when all the load-balanced servers
have similar RAM and CPU and are located on the same segment.
Server The Security Gateway determines which server is best equipped to

load handle the new connection.
Round The Security Gateway directs service requests to the next server in
Robin the sequence.
This method is a good choice when all the load balanced servers
have similar RAM and CPU and are on the same segment.
Round Trip Not supported.
Domain Not supported.
h. Click OK.

5. Close the Object Explorer window.

6. From the left navigation panel, click Security Policies and click Access Control.
7. Add the Load Balancing rule to the Access Control Policy Rule Base:
Source Destination Services & Applications Action
*Any Logical Server object Load-balanced Services Accept

or
User Auth
or
Client Auth
8. For applications that use HTTP redirection, add a rule to allow the Network Group object (that
contains load-balanced server objects) to communicate directly with the clients:
Source Destination Services & Applications Action
*Any Network Group object http Accept
9. Configure global settings for ConnectControl.

Instructions
a. At the top, click Menu > Global properties.

b. From the left tree, click ConnectControl.
c. Configure the settings that fit your environment:
n Server Availability
This configures how ConnectControl finds available servers.
l The Server availability check interval control the number of seconds
between pings from the Security Gateway or Cluster to the load-balanced
servers.
l The Server check retries controls the number of attempts to contact a non-
responsive server after ConnectControl stops directing connections to it.
n Server Persistency
If you enabled Persistency by server, you can set a timeout for a client to use one
server. If a server becomes unavailable, ConnectControl directs new connections
to a new, available server. This bypasses the persistency and optimizes load
balancing.
n Server Load Balancing
Not supported.
d. Click OK.
10. Install the Access Control Policy on this Security Gateway or Cluster object.

Monitoring Software Blade
Monitoring Software Blade

This Software Blade enables administrator to monitor these counters in real-time:
n System counters (CPU usage, Used Virtual Memory, Free Disk Space, and so on)
n Traffic connections
n Traffic throughput
To see System and Traffic counters in SmartConsole:

1. From the left navigation panel, click Gateways & Servers.
2. In the top pane, select the Security Gateway (or Cluster) object.
3. In the bottom pane, click the Summary tab and click the Device & License Information link at the
bottom.
4. From the left tree, click System Counters and Traffic.
5. For a cluster object, from the top drop-down menu, select the Cluster Member.
To see User and VPN Tunnel counters in SmartView Monitor:

1. From the left navigation panel, click Logs & Monitor > Logs.
2. At the bottom, click the Tunnel & User Monitoring link.
n R81 Logging and Monitoring Administration Guide
n R77 SmartView Monitor Administration Guide

Cloud Security
Cloud Security
Check Point cloud security protects assets in the cloud from the most sophisticated threats with dynamic
scalability, intelligent provisioning and consistent control across physical and virtual networks.
n R81 CloudGuard Controller Administration Guide
n https://www.checkpoint.com/products/

Advanced Routing
Advanced Routing
Gaia OS supports:
n Dynamic Routing protocols - OSPF, BGP, and RIP.
n Dynamic Multicast Routing - PIM Sparse Mode (SM), PIM Dense Mode (DM), PIM Source-Specific
Multicast (SSM), and IGMP.
n Different routing options.
You can configure these routing protocols and options in Gaia Portal and Gaia Clish.
For more information, see the R81 Gaia Advanced Routing Administration Guide.

SNMP
SNMP
SNMP, as implemented on Check Point platforms, enables an SNMP manager to monitor the device using
GetRequest, GetNextRequest, GetBulkRequest, and a select number of traps.
The Check Point implementation also supports using SetRequest to change these attributes:
sysContact, sysLocation, and sysName. You must configure read-write permissions for set operations
to work.
Check Point Gaia supports SNMP v1, v2, and v3.
For more information, see the R81 Gaia Administration Guide > Chapter System Management > Section
SNMP.

Deploying a Single Security Gateway in Monitor Mode
Deploying a Single Security

Gateway in Monitor Mode
Introduction to Monitor Mode
You can configure Monitor Mode on a single Check Point Security Gateway's interface.
The Check Point Security Gateway listens to traffic from a Mirror Port or Span Port on a connected switch.
Use the Monitor Mode to analyze network traffic without changing the production environment.
The mirror port on a switch duplicates the network traffic and sends it to the Security Gateway with an
interface configured in Monitor Mode to record the activity logs.
You can use the Monitor Mode:
n To monitor the use of applications as a permanent part of your deployment
n To evaluate the capabilities of the Software Blades:
l The Security Gateway neither enforces any security policy, nor performs any active operations
(prevent / drop / reject) on the interface in the Monitor Mode.
l The Security Gateway terminates and does not forward all packets that arrive at the interface in
the Monitor Mode.
l The Security Gateway does not send any traffic through the interface in the Monitor Mode.
Benefits of the Monitor Mode include:
n There is no risk to your production environment.
n It requires minimal set-up configuration.
n It does not require TAP equipment, which is expensive.

Deploying a Single Security Gateway in Monitor Mode
Example Topology for Monitor Mode
Item Description
1 Switch with a mirror or SPAN port that duplicates all incoming and outgoing packets.
The Security Gateway connects to a mirror or SPAN port on the switch.
2 Servers.
3 Clients.
4 Security Gateway with an interface in Monitor Mode.
5 Security Management Server that manages the Security Gateway.
For More About Monitor Mode

See the R81 Installation and Upgrade Guide > Chapter Special Scenarios for Security Gateways > Section
Deploying a Security Gateway in Monitor Mode.

Deploying a Single Security Gateway or ClusterXL in Bridge Mode
Deploying a Single Security

Gateway or ClusterXL in Bridge
Mode
Introduction to Bridge Mode
If you cannot divide the existing network into several networks with different IP addresses, you can install a
Check Point Security Gateway (or a ClusterXL) in the Bridge Mode.
A Security Gateway (or ClusterXL) in Bridge Mode is invisible to Layer 3 traffic.
When traffic arrives at one of the bridge subordinate interfaces, the Security Gateway (or Cluster Members)
inspects it and passes it to the second bridge subordinate interface.

Deploying a Single Security Gateway or ClusterXL in Bridge Mode
Example Topology for a single Security

Gateway in Bridge Mode
Item Description
1 Network, which an administrator needs to divide into two Layer 2 segments.

The Security Gateway in Bridge Mode connects between these segments.
2 First network segment.
3 Switch that connects the first network segment to one bridged subordinate interface (4) on the
Security Gateway in Bridge Mode.
4 One bridged subordinate interface (for example, eth1) on the Security Gateway in Bridge
Mode.
5 Security Gateway in Bridge Mode.
6 Another bridged subordinate interface (for example, eth2) on the Security Gateway in Bridge
Mode.
7 Dedicated Gaia Management Interface (for example, eth0) on the Security Gateway.
8 Switch that connects the second network segment to the other bridged subordinate interface
(6) on the Security Gateway in Bridge Mode.
9 Second network segment.
For More About Bridge Mode

See the R81 Installation and Upgrade Guide > Chapter Special Scenarios for Security Gateways > Section
Deploying a Security Gateway or a ClusterXL in Bridge Mode.

Security Before Firewall Activation
Security Before Firewall Activation

To protect the Security Gateway and network, Check Point Security Gateway has baseline security:
Baseline
Name of Policy Description
Security
Boot defaultfilter Security during boot process.

Security
Initial Policy InitialPolicy Security before a policy is installed for the first time, or when
Security Gateway failed to load the policy.
Important - If you disable the boot security or unload the currently installed policy, you leave your
Security Gateway, or a Cluster Member without protection.
Best Practice - Before you disable the boot security, we recommend to disconnect your
Security Gateway, or a Cluster Member from the network completely.
For additional information, see these commands in the R81 CLI Reference Guide:
Command Description
$CPDIR/bin/cpstat -f policy fw Shows the currently installed policy
$FWDIR/bin/control_bootsec {-r | -R} Disables the boot security
$FWDIR/bin/control_bootsec [-g | -G] Enables the boot security
$FWDIR/bin/comp_init_policy [-u | -U] Deletes the local state policy
$FWDIR/bin/comp_init_policy [-g | -G] Creates the local state Initial Policy
$FWDIR/bin/fw unloadlocal Unloads the currently installed policy

Boot Security
Boot Security
The Boot Security protects the Security Gateway and its networks, during the boot:
n Disables the IP Forwarding in Linux OS kernel
n Loads the Default Filter Policy
Important - In a Cluster, you must configure all the Cluster Members in the same way.
The Default Filter Policy
The Default Filter Policy (defaultfilter) protects the Security Gateway from the time it boots up until
it installs the user-defined Security Policy.
Boot Security disables IP Forwarding and loads the Default Filter Policy.
There are three Default Filters templates on the Security Gateway:
Default Filter
Default Filter Policy File Description
Mode
Boot Filter $FWDIR/lib/defaultfilter.boot This filter:

n Drops all incoming packets
that have the same source
IP addresses as the IP
addresses assigned to the
Security Gateway interfaces
n Allows all outbound packets
from the Security Gateway
Drop Filter $FWDIR/lib/defaultfilter.drop This filter drops all inbound and

outbound packets on the Security
Gateway.
Best Practice - If the boot
process requires that the
Security Gateway
communicate with other
hosts, do not use the Drop
Filter.

Boot Security
Default Filter
Default Filter Policy File Description
Mode
Filter for $FWDIR/lib/defaultfilter.dag This filter for Security Gateways

Dynamically with Dynamically Assigned IP
Assigned address:
Gateways (DAG)
n Allows all DHCP Requests
n Allows all DHCP Replies
n Uses Boot Filter:
a. Drops all incoming
packets that have the
same source IP
addresses as the IP
addresses assigned
to the Security
Gateway interfaces
b. Allows all outbound
packets from the
Security Gateway
Selecting the Default Filter Policy
Step Instructions
1 Make sure to configure and install a Security Policy on the Security Gateway.
2 Connect to the command line on the Security Gateway.
4 Back up the current Default Filter Policy file:

cp -v $FWDIR/conf/defaultfilter.pf{,_BKP}
5 Create a new Default Filter Policy file.

n To create a new Boot Filter, run:
cp -v $FWDIR/lib/defaultfilter.boot
$FWDIR/conf/defaultfilter.pf
n To create a new Drop Filter, run:
cp -v $FWDIR/lib/defaultfilter.drop
n To create a new DAG Filter, run:
cp -v $FWDIR/lib/defaultfilter.dag

Boot Security
Step Instructions
6 Compile the new Default Filter file:

fw defaultgen
n The new complied Default Filter file for IPv4 traffic is:
$FWDIR/state/default.bin
$FWDIR/state/default.bin6
7 Get the path of the Default Filter Policy file:

$FWDIR/boot/fwboot bootconf get_def
Example:
[Expert@MyGW:0]# $FWDIR/boot/fwboot bootconf get_def
/etc/fw.boot/default.bin
[Expert@MyGW:0]#
8 Copy new complied Default Filter file to the path of the Default Filter Policy file.
n For IPv4 traffic, run:
cp -v $FWDIR/state/default.bin
cp -v $FWDIR/state/default.bin6
/etc/fw.boot/default.bin6
9 Make sure to connect to the Security Gateway over a serial console.

Important - If the new Default Filter Policy fails and blocks all access
through the network interfaces, you can unload that Default Filter Policy
and install the working policy.
10 Reboot the Security Gateway.
Defining a Custom Default Filter
Administrators with Check Point INSPECT language knowledge can define customized Default Filters.
Important - Make sure your customized Default Filter policy does not interfere with the Security
Gateway boot process.
Step Instructions
1 Make sure to configure and install a Security Policy on the Security Gateway.

Boot Security
Step Instructions
4 Back up the current Default Filter Policy file:

cp -v $FWDIR/conf/defaultfilter.pf{,_BKP}
5 Create a new Default Filter Policy file.

n To use the Boot Filter as a template, run:
cp -v $FWDIR/lib/defaultfilter.boot
n To use the Drop Filter as a template, run:
cp -v $FWDIR/lib/defaultfilter.drop
n To use the DAG Filter as a template, run:
cp -v $FWDIR/lib/defaultfilter.dag
6 Edit the new Default Filter Policy file to include the applicable INSPECT code.
Important - Your customized Default Filter must not use these functions:
n Logging
n Authentication
n Encryption
n Content Security
7 Compile the new Default Filter file:

fw defaultgen
$FWDIR/state/default.bin
$FWDIR/state/default.bin6
8 Get the path of the Default Filter Policy file:

$FWDIR/boot/fwboot bootconf get_def
Example:
[Expert@MyGW:0]# $FWDIR/boot/fwboot bootconf get_def
[Expert@MyGW:0]#

Boot Security
Step Instructions
9 Copy new complied Default Filter file to the path of the Default Filter Policy file.
cp -v $FWDIR/state/default.bin
cp -v $FWDIR/state/default.bin6
/etc/fw.boot/default.bin6
10 Make sure to connect to the Security Gateway over a serial console.

Important - If the new Default Filter Policy fails and blocks all access through
the network interfaces, you can unload that Default Filter Policy and install
the working policy.
Using the Default Filter Policy for Maintenance
It is sometimes necessary to stop the Security Gateway for maintenance. It is not always practical to
disconnect the Security Gateway from the network (for example, if the Security Gateway is on a remote
site).
To stop the Security Gateway for maintenance and maintain security, you can run:
Command Description
cpstop -
n Shuts down Check Point processes
fwflag - n Loads the Default Filter policy (defaultfilter)
default
cpstop -
n Shuts down Check Point processes
fwflag - n Keeps the currently loaded kernel policy
proc n Maintains the Connections table, so that after you run the cpstart
command, you do not experience dropped packets because they are
"out of state"
Note - Only security rules that do not use user space processes continue
to work.

The Initial Policy
The Initial Policy

Until the Security Gateway administrator installs the Security Policy on the Security Gateway for the first
time, security is enforced by an Initial Policy.
The Initial Policy operates by adding the predefined implied rules to the Default Filter policy.
These implied rules forbid most communication, yet allow the communication needed for the installation of
the Security Policy.
The Initial Policy also protects the Security Gateway during Check Point product upgrades, when a SIC
certificate is reset on the Security Gateway, or in the case of a Check Point product license expiration.
Note - During a Check Point upgrade, a SIC certificate reset, or license expiration, the Initial
Policy overwrites the user-defined policy.
The sequence of actions during boot of the Security Gateway until a Security Policy is loaded for the first
time:
Step Instructions
1 The Security Gateway boots up.
2 The Security Gateway disables IP Forwarding and loads the Default Filter policy.
3 The Security Gateway configures the interfaces.
4 The Security Gateway services start.
5 The Security Gateway fetches the Initial Policy from the local directory.
6 Administrator installs the user-defined Security Policy from the Management Server.
The Security Gateway enforces the Initial Policy until administrator installs a user-defined policy.
In subsequent boots, the Security Gateway loads the user-defined policy immediately after the Default Filter
policy.
There are different Initial Policies for Standalone and distributed setups:
n In a Standalone configuration, where the Security Management Server and the Security Gateway are
on the same computer, the Initial Policy allows CPMI management communication only.
This permits SmartConsole clients to connect to the Security Management Server.
n In a distributed configuration, where the Security Management Server is on one computer and the
Security Gateway is on a different computer, the Initial Policy:
l Allows the cpd and fwd daemons to communicate for SIC (to establish trust) and for Policy
installation.
l Does not allow CPMI connections through the Security Gateway.
The SmartConsole is not be able to connect to the Security Management Server, if the
SmartConsole must access the Security Management Server through a Security Gateway with
the Initial Policy.

Troubleshooting: Cannot Complete Reboot
Troubleshooting: Cannot Complete Reboot

In some configurations, the Default Filter policy prevents the Security Gateway from completing the reboot
after installation.
Firstly, look at the Default Filter. Does the Default Filter allow traffic required by the boot procedures?
Secondly, if the boot process cannot finish successfully, remove the Default Filter:
Step Instructions
1 Connect to the Security Gateway over serial console.
3 During boot, press any key to enter the Boot Menu.
4 Select the Start in maintenance mode.
5 Enter the Expert mode password.
6 Set the Default Filter to not load again:

a. Go to the $FWDIR directory:
cd /opt/CPsuite-<VERSION>/fw1/
b. Set the Default Filter to not load again:
./fwboot bootconf set_def
7 In the $FWDIR/boot/boot.conf file, examine the value of the "DEFAULT_FILTER_PATH":

a. Go to the $FWDIR directory:
cd /opt/CPsuite-<VERSION>/fw1/
b. examine the value of the "DEFAULT_FILTER_PATH":
grep DEFAULT_FILTER_PATH boot/boot.conf

Command Line Reference
Command Line Reference

See the R81 CLI Reference Guide.
Important - For Scalable Platforms, see the chapter Managing Security Groups > Section Global
Commands in:
n R81 Quantum Maestro Administration Guide
n R81 Quantum Scalable Chassis Administration Guide

Working with Kernel Parameters on Security Gateway
Working with Kernel Parameters on

Security Gateway
This section describes what are kernel parameters, and how to view and configure their values.

Introduction to Kernel Parameters
Introduction to Kernel Parameters

Kernel parameters let you change the advanced behavior of your Security Gateway.
These are the supported types of kernel parameters:
Type Description
Integer Accepts only one integer value.
String Accepts only a plain-text string.
Important:
n In Cluster, you must see and configure the same value for the same kernel parameter on
each Cluster Member.
n In VSX Gateway, the configured values of kernel parameters apply to all existing Virtual
Systems and Virtual Routers.
Security Gateway gets the names and the default values of the kernel parameters from these kernel module
files:
n $FWDIR/boot/modules/fw_kern_64.o
n $FWDIR/boot/modules/fw_kern_64_v6.o
n $PPKDIR/boot/modules/sim_kern_64.o
n $PPKDIR/boot/modules/sim_kern_64_v6.o

Firewall Kernel Parameters

To change the internal default behavior of Firewall or to configure special advanced settings for Firewall,
you can use Firewall kernel parameters.
The names of applicable Firewall kernel parameters and their values appear in various SK articles in Check
Point Support Center, and provided by Check Point Support.
Important:
n The names of Firewall kernel parameters are case-sensitive.
n You can configure most of the Firewall kernel parameters on-the-fly with the "fw ctl
set" command.
This change does not survive a reboot.
You can use the "fw ctl set -f" command to make this change permanent as well.
n You can configure some of the Firewall kernel parameters only permanently in the special
configuration file $FWDIR/boot/modules/fwkern.conf command.
This requires a maintenance window, because the new values of the kernel parameters
take effect only after a reboot.
n You can configure some of the Firewall kernel parameters only permanently in the special
configuration files - $FWDIR/boot/modules/fwkern.conf or
$FWDIR/boot/modules/vpnkern.conf.
You must manually edit these files.
This requires a maintenance window, because the new values of the kernel parameters
take effect only after a reboot.
n On Scalable Platforms (Maestro and Chassis), you must connect to the applicable Security
Group.
Examples of Firewall kernel parameters
Type Name
Integer fw_allow_simultaneous_ping
fw_kdprintf_limit
fw_log_bufsize
send_buf_limit
String simple_debug_filter_addr_1
simple_debug_filter_daddr_1
simple_debug_filter_vpn_1
ws_debug_ip_str
fw_lsp_pair1

Working with Integer Kernel Parameters

Viewing the list of the available Firewall integer kernel parameters and their values
Step Instructions
1 Connect to the command line on your Security Gateway / each Cluster Member.
Note - On Scalable Platforms (Maestro and Chassis), you must connect to the applicable
Security Group.
3 Make sure you can get the list of the available integer kernel parameters and their values
without errors:
Note - The configuration of your Security Gateway might not support all kernel
parameters. As a result, the Security Gateway might fail to get the value of some
kernel parameters.
modinfo -p $FWDIR/boot/modules/fw_kern*.o | sort -u | grep
':int param' | awk 'BEGIN {FS=":"} ; {print $1}' | xargs -n 1
fw ctl get int
4 If in the previous step there were no errors, get the list of the available integer kernel
parameters and their values, and save the list to a file:
fw ctl get int 1>> /var/log/fw_integer_kernel_parameters.txt
2>> /var/log/fw_integer_kernel_parameters.txt
5 Analyze the output file:

/var/log/fw_integer_kernel_parameters.txt

Viewing the current value of a Firewall integer kernel parameter
Step Instructions
Security Group.
2 Log in to Gaia Clish or the Expert mode.

Note - On Scalable Platforms (Maestro and Chassis), you must use Gaia gClish or the
Expert mode.
3 Get the current value of an integer kernel parameter:

n On the Security Gateway / each Cluster Member, run in Gaia Clish or the Expert
mode:
fw ctl get int <Name of Integer Kernel Parameter> [-a]
n On the Scalable Platform Security Group, run in Gaia gClish:
n On the Scalable Platform Security Group, run in the Expert mode:
g_fw ctl get int <Name of Integer Kernel Parameter> [-a]
Example:
[Expert@MyGW:0]# fw ctl get int send_buf_limit
send_buf_limit = 80
[Expert@MyGW:0]#

Configuring a value for a Firewall integer kernel parameter temporarily
Important - This change does not survive reboot.
Step Instructions
Security Group.

Expert mode.
3 Configure the new value for an integer kernel parameter:

n On a Security Gateway / each Cluster Member, run in Gaia Clish or the Expert
mode:
fw ctl set int <Name of Integer Kernel Parameter> <Integer
Value>
n On a Scalable Platform Security Group, run in Gaia gClish:
Value>
n On a Scalable Platform Security Group, run in the Expert mode:
g_fw ctl set int <Name of Integer Kernel Parameter>
<Integer Value>
Example:
[Expert@MyGW:0]# fw ctl set int send_buf_limit 100
Set operation succeeded
[Expert@MyGW:0]#
4 Make sure the new value is configured.

mode:
fw ctl get int <Name of Integer Kernel Parameter>
g_fw ctl get int <Name of Integer Kernel Parameter>
Example:
[Expert@MyGW:0]# fw ctl get int send_buf_limit
send_buf_limit = 100
[Expert@MyGW:0]#

Configuring a value for a Firewall integer kernel parameter permanently

To make a kernel parameter configuration permanent (to survive reboot), you must edit one of the
applicable configuration files:
n For Firewall kernel parameters:
$FWDIR/boot/modules/fwkern.conf
n For VPN kernel parameters:
$FWDIR/boot/modules/vpnkern.conf
The exact parameters appear in various SK articles in Check Point Support Center, and provided by
Check Point Support.
Short procedure for the "fwkern.conf" file
Step Instructions
Note - On Scalable Platforms (Maestro and Chassis), you must connect to the
applicable Security Group.
3 Back up the current configuration file, if it exists:

n On the Security Gateway (each Cluster Member), run:
cp -v $FWDIR/boot/modules/fwkern.conf{,_BKP}
n On the Scalable Platform Security Group, run:
g_cp -v $FWDIR/boot/modules/fwkern.conf{,_BKP}
4 Configure the required Firewall kernel parameter with the assigned value in the exact
format specified below.
fw ctl set -f int <Name_of_Integer_Kernel_Parameter>
<Integer_Value>
n On the Scalable Platform Security Group, run one of these commands:
g_fw ctl set -f int <Name_of_Integer_Kernel_Parameter>
<Integer_Value>
g_update_conf_file fwkern.conf <Name_of_Integer_Kernel_

Parameter>=<Integer_Value>
Example:
[Expert@MyGW:0]# fw ctl set -f int send_buf_limit 100
"fwkern.conf" was updated successfully
[Expert@MyGW:0]#
[Expert@MyGW:0]# g_update_conf_file fwkern.conf send_buf_limit=100

[Expert@MyGW:0]#

Step Instructions
5 Examine the configuration file.

cat $FWDIR/boot/modules/fwkern.conf
g_cat $FWDIR/boot/modules/fwkern.conf
6 Reboot.
n On the Security Gateway / Cluster Member, run:
reboot
Important - In cluster, this can cause a failover.

g_reboot -a

Expert mode.
9 Make sure the new value of the kernel parameter is configured.

n On a Security Gateway / each Cluster Member, run:
n On a Scalable Platform Security Group, run:
Long procedure for the "fwkern.conf" and "vpnkern.conf" files
For more information, see sk26202: Changing the kernel global parameters for Check Point Security
Gateway.
Step Instructions

Step Instructions
3 See if the configuration file already exists.

n On a Security Gateway / each Cluster Member:
l For Firewall kernel parameters, run:
ls -l $FWDIR/boot/modules/fwkern.conf
l For VPN kernel parameters, run:
ls -l $FWDIR/boot/modules/vpnkern.conf
n On a Scalable Platform Security Group:
g_ls -l $FWDIR/boot/modules/fwkern.conf
g_ls -l $FWDIR/boot/modules/vpnkern.conf
4 If this file already exists, skip to Step 5.

If this file does not exist, then create it manually and then skip to Step 6.
touch $FWDIR/boot/modules/fwkern.conf
g_all touch $FWDIR/boot/modules/fwkern.conf

g_all touch $FWDIR/boot/modules/vpnkern.conf
5 Back up the current configuration file.

cp -v $FWDIR/boot/modules/vpnkern.conf{,_BKP}
g_cp -v $FWDIR/boot/modules/vpnkern.conf{,_BKP}

Step Instructions
6 Edit the current configuration file.

The same syntax applies to the Security Gateway / each Cluster Member and the
Scalable Platform Security Group:
n For Firewall kernel parameters, run:
vi $FWDIR/boot/modules/fwkern.conf
n For VPN kernel parameters, run:
vi $FWDIR/boot/modules/vpnkern.conf
7 Add the required Firewall kernel parameter with the assigned value in the exact format
specified below.
Important - These configuration files do not support space characters, tabulation
characters, and comments (lines that contain the # character).
<Name_of_Integer_Kernel_Parameter>=<Integer_Value>
9 On the Scalable Platform Security Group, copy the updated configuration file to all other
Security Group Members:
asg_cp2blades $FWDIR/boot/modules/fwkern.conf
asg_cp2blades $FWDIR/boot/modules/vpnkern.conf
10 Reboot.
reboot

g_reboot -a

Expert mode.

Step Instructions

mode:

Working with String Kernel Parameters

Viewing the list of the available Firewall string kernel parameters and their values
Step Instructions
Security Group.
without errors:
kernel parameters.
':string param' | awk 'BEGIN {FS=":"} ; {print $1}' | xargs -n
1 fw ctl get str
4 If in the previous step there were no errors, get the list of the available string kernel
1 fw ctl get str 1>> /var/log/fw_string_kernel_parameters.txt
2>> /var/log/fw_string_kernel_parameters.txt

/var/log/fw_string_kernel_parameters.txt

Viewing the current value of a Firewall string kernel parameter
Step Instructions
Security Group.

Expert mode.
3 Get the current value of a string kernel parameter:

mode:
fw ctl get str <Name of String Kernel Parameter> [-a]
g_fw ctl get str <Name of String Kernel Parameter> [-a]
Example:
[Expert@MyGW:0]# fw ctl get str fileapp_default_encoding_charset
fileapp_default_encoding_charset = 'UTF-8'
[Expert@MyGW:0]#

Configuring a value for a Firewall string kernel parameter temporarily
Step Instructions
Security Group.

Expert mode.
3 Configure the new value for a string kernel parameter.

Note - You must write the value in single quotes, or double quotes. Use one of these
syntax options.
mode:
fw ctl set str <Name of String Kernel Parameter> '<String
Text>'
or
fw ctl set str <Name of String Kernel Parameter> "<String
Text>"
Text>'
or
Text>"
g_fw ctl set str <Name of String Kernel Parameter>
'<String Text>'
or
"<String Text>"
Example:
[Expert@MyGW:0]# fw ctl set str debug_filter_saddr_ip '1.1.1.1'
[Expert@MyGW:0]#

Step Instructions

mode:
fw ctl get str <Name of String Kernel Parameter>
g_fw ctl get str <Name of String Kernel Parameter>
Example:
[Expert@MyGW:0]# fw ctl get str debug_filter_saddr_ip
debug_filter_saddr_ip = '1.1.1.1'
[Expert@MyGW:0]#

Configuring a value for a Firewall string kernel parameter permanently

To make a kernel parameter configuration permanent (to survive reboot), you must edit one of the
applicable configuration files:
n For Firewall kernel parameters:
$FWDIR/boot/modules/fwkern.conf
n For VPN kernel parameters:
$FWDIR/boot/modules/vpnkern.conf
The exact parameters appear in various SK articles in Check Point Support Center, and provided by
Check Point Support.
Short procedure for the "fwkern.conf" file
Step Instructions
3 Back up the current configuration file, if it exists:


Step Instructions
4 Configure the required Firewall kernel parameter with the assigned value in the exact
format specified below.
Note - You must write the value in single quotes, or double quotes. Use one of
these syntax options.
mode:
fw ctl set -f str <Name_of_String_Kernel_Parameter>
'<String_Text>'
or
fw ctl set -f str <Name_of_String_Kernel_Parameter>
"<String_Text>"
g_fw ctl set -f str <Name_of_String_Kernel_Parameter>
'<String_Text>'
or
g_fw ctl set -f str <Name_of_String_Kernel_Parameter>
"<String_Text>"
Example:
[Expert@MyGW:0]# fw ctl set -f str ws_debug_ip_str '1.1.1.1'
[Expert@MyGW:0]#
5 Examine the configuration file.

n On the Security Gateway / each Cluster Member, run:
cat $FWDIR/boot/modules/fwkern.conf
g_cat $FWDIR/boot/modules/fwkern.conf
6 Reboot.
reboot

g_reboot -a

Step Instructions

Expert mode.

mode:
Long procedure for the "fwkern.conf" and "vpnkern.conf" files
For more information, see sk26202: Changing the kernel global parameters for Check Point Security
Gateway.
Step Instructions
3 n On a Security Gateway / each Cluster Member:

ls -l $FWDIR/boot/modules/fwkern.conf
ls -l $FWDIR/boot/modules/vpnkern.conf
g_ls -l $FWDIR/boot/modules/fwkern.conf
g_ls -l $FWDIR/boot/modules/vpnkern.conf

Step Instructions

If this file does not exist, then create it manually and then skip to Step 6.
g_all touch $FWDIR/boot/modules/fwkern.conf

g_all touch $FWDIR/boot/modules/vpnkern.conf

cp -v $FWDIR/boot/modules/vpnkern.conf{,_BKP}
g_cp -v $FWDIR/boot/modules/vpnkern.conf{,_BKP}

The same syntax applies to the Security Gateway / each Cluster Member and the
Scalable Platform Security Group:
vi $FWDIR/boot/modules/fwkern.conf
vi $FWDIR/boot/modules/vpnkern.conf

Step Instructions
7 Add the required kernel parameter with the assigned value in the exact format specified
below.
Important - These configuration files do not support space characters, tabulation
Note - You must write the value in single quotes, or double quotes. Use one of
<Name_of_String_Kernel_Parameter>='<String_Text>'
or
<Name_of_String_Kernel_Parameter>="<String_Text>"
9 On the Scalable Platform Security Group, copy the updated configuration file to all other
Security Group Members:
asg_cp2blades $FWDIR/boot/modules/fwkern.conf
asg_cp2blades $FWDIR/boot/modules/vpnkern.conf
10 Reboot.
reboot

g_reboot -a

Expert mode.

Step Instructions

mode:

Removing the current value from a Firewall string kernel parameter temporarily
Step Instructions
1 Connect to the command line on your Security Gateway or Cluster Member.

Security Group.

Expert mode.
3 Clear the current value from a string kernel parameter:

Note - You must set an empty value in single quotes, or double quotes. Use one of
mode:
fw ctl set str '<Name of String Kernel Parameter>'
or
fw ctl set str "<Name of String Kernel Parameter>"
fw ctl set str '<Name of String Kernel Parameter>'
or
fw ctl set str "<Name of String Kernel Parameter>"
g_fw ctl set str '<Name of String Kernel Parameter>'
or
g_fw ctl set str "<Name of String Kernel Parameter>"
Example:
[Expert@MyGW:0]# fw ctl set str debug_filter_saddr_ip ''
[Expert@MyGW:0]#

Step Instructions
4 Make sure the value is cleared (the new value is empty):

mode:
Example:
[Expert@MyGW:0]# fw ctl get str debug_filter_saddr_ip
debug_filter_saddr_ip = ''
[Expert@MyGW:0]#

SecureXL Kernel Parameters

To change the internal default behavior of SecureXL or to configure special advanced settings for
SecureXL, you can use SecureXL kernel parameters.
The names of applicable SecureXL kernel parameters and their values appear in various SK articles in
Check Point Support Center, and provided by Check Point Support.
Important:
n The names of SecureXL kernel parameters are case-sensitive.
n You can configure SecureXL kernel parameters in the current session with the "fw ctl
set" command.
This change does not survive reboot.
n To configure SecureXL kernel parameters permanently, you must configure them in the
special configuration file - $PPKDIR/conf/simkern.conf
Schedule a maintenance window, because this procedure requires a reboot.
n For some SecureXL kernel parameters, you cannot get their current value on-the-fly with
the "fw ctl get" command (see sk43387).
n On Scalable Platforms (Maestro and Chassis), you must connect to the applicable Security
Group.
Examples of SecureXL kernel parameters
Type Name
Integer num_of_sxl_devices
sim_ipsec_dont_fragment
tcp_always_keepalive
sim_log_all_frags
simple_debug_filter_dport_1
simple_debug_filter_proto_1
String simple_debug_filter_addr_1
simple_debug_filter_daddr_2
simlinux_excluded_ifs_list

Working with Integer Kernel Parameters

Viewing the list of the available SecureXL integer kernel parameters and their values
Step Instructions
Security Group.
without errors:
kernel parameters.
modinfo -p $PPKDIR/boot/modules/sim_kern*.o | sort -u | grep
fw ctl get int
4 If in the previous step there were no errors, get the list of the available integer kernel
fw ctl get int 1>> /var/log/sxl_integer_kernel_parameters.txt
2>> /var/log/sxl_integer_kernel_parameters.txt

/var/log/sxl_integer_kernel_parameters.txt

Viewing the current value of a SecureXL integer kernel parameter
Step Instructions
Security Group.

Expert mode.

mode:
Example:
[Expert@MyGW:0]# fw ctl get int sim_ipsec_dont_fragment
sim_ipsec_dont_fragment = 1
[Expert@MyGW:0]#

Configuring a value for a SecureXL integer kernel parameter temporarily
Step Instructions
Security Group.

Expert mode.
3 Configure the new value for an integer kernel parameter:

mode:
Value>
Value>
g_fw ctl set int <Name of Integer Kernel Parameter>
<Integer Value>
Example:
[Expert@MyGW:0]# fw ctl set int sim_ipsec_dont_fragment 0
[Expert@MyGW:0]#

mode:
g_fw ctl get int <Name of Integer Kernel Parameter>
Example:
[Expert@MyGW:0]# fw ctl get int sim_ipsec_dont_fragment
sim_ipsec_dont_fragment = 0
[Expert@MyGW:0]#

Configuring a value for a SecureXL integer kernel parameter permanently
Step Instructions
Security Group.

ls -l $PPKDIR/conf/simkern.conf
g_ls -l $PPKDIR/conf/simkern.conf

If this file does not exist, then create it manually and then skip to Step 6:
touch $PPKDIR/conf/simkern.conf
g_all touch $PPKDIR/conf/simkern.conf

cp -v $PPKDIR/conf/simkern.conf{,_BKP}
g_cp -v $PPKDIR/conf/simkern.conf{,_BKP}

The same syntax applies to the Security Gateway / each Cluster Member and the Scalable
Platform Security Group:
vi $PPKDIR/conf/simkern.conf
7 Add the required SecureXL kernel parameter with the assigned value in the exact format
specified below.
Important - This configuration file does not support space characters, tabulation
<Name_of_SecureXL_Integer_Kernel_Parameter>=<Integer_Value>

Step Instructions
9 Reboot.
reboot

g_reboot -a
Security Group.

Expert mode.

mode:

Working with String Kernel Parameters

Viewing the list of the available SecureXL string kernel parameters and their values
Step Instructions
Security Group.
without errors:
kernel parameters.
1 fw ctl get str
4 If in the previous step there were no errors, get the list of the available string kernel
1 fw ctl get str 1>> /var/log/sxl_string_kernel_parameters.txt
2>> /var/log/sxl_string_kernel_parameters.txt

/var/log/sxl_string_kernel_parameters.txt

Viewing the current value of a SecureXL string kernel parameter
Step Instructions
Security Group.

Expert mode.

mode:
fw ctl get str <Name of Integer Kernel Parameter> [-a]
fw ctl get str <Name of Integer Kernel Parameter> [-a]
g_fw ctl get str <Name of Integer Kernel Parameter> [-a]
Example:
[Expert@MyGW:0]# fw ctl get str fwkdebug_print_connkey_on_str
fwkdebug_print_connkey_on_str = ''
[Expert@MyGW:0]#

Configuring a value for a SecureXL string kernel parameter temporarily
Step Instructions
Security Group.

Expert mode.
3 Configure the new value for a string kernel parameter.

syntax options.
mode:
Text>'
or
Text>"
Text>'
or
Text>"
'<String Text>'
or
"<String Text>"
Example:
[Expert@MyGW:0]# fw ctl set str fwkdebug_print_connkey_on_str 'Packet accepted'
[Expert@MyGW:0]#

Step Instructions

mode:
Example:
[Expert@MyGW:0]# fw ctl get str fwkdebug_print_connkey_on_str
fwkdebug_print_connkey_on_str = 'Packet accepted'
[Expert@MyGW:0]#

Configuring a value for a SecureXL string kernel parameter permanently
Step Instructions
Security Group.

ls -l $PPKDIR/conf/simkern.conf
g_ls -l $PPKDIR/conf/simkern.conf

If this file does not exist, then create it manually and then skip to Step 6:
touch $PPKDIR/conf/simkern.conf
g_all touch $PPKDIR/conf/simkern.conf

cp -v $PPKDIR/conf/simkern.conf{,_BKP}
g_cp -v $PPKDIR/conf/simkern.conf{,_BKP}

The same syntax applies to the Security Gateway / each Cluster Member and the Scalable
Platform Security Group:
vi $PPKDIR/conf/simkern.conf
7 Add the required SecureXL kernel parameter with the assigned value in the exact format
specified below.
Important - This configuration file does not support space characters, tabulation
syntax options.
<Name_of_SecureXL_String_Kernel_Parameter>='<String_Text>'
or
<Name_of_SecureXL_String_Kernel_Parameter>="<String_Text>"

Step Instructions
9 Reboot.
reboot

g_reboot -a
Security Group.

Expert mode.

mode:

Kernel Debug on Security Gateway
Kernel Debug on Security Gateway

This section describes how to collect a kernel debug on Security Gateway.

Kernel Debug Syntax
Kernel Debug Syntax

Description:
During a kernel debug session, Security Gateway prints special debug messages that help Check Point
Support and R&D understand how the Security Gateway processes the applicable connections.
Important - In Cluster, you must configure and perform the kernel debug procedure on all cluster
members in the same way.
Action plan to collect a kernel debug:
Note - See the "Kernel Debug Procedure" on page 215, or the "Kernel Debug Procedure with
Connection Life Cycle" on page 219.
Step Action Description
1 Configure the applicable In this step, you prepare the kernel debug options:
debug settings:
a. Restore the default debug settings, so that any other
a. Restore the default debug settings do not interfere with the kernel debug.
settings. b. Allocate the kernel debug buffer, in which Security
b. Allocate the debug Gateway holds the applicable debug messages.
buffer.
2 Configure the applicable In this step, you prepare the applicable kernel debug modules
kernel debug modules and and their debug flags, so that Security Gateway collects only
their debug flags. applicable debug messages.
3 Start the collection of the In this step, you configure Security Gateway to write the debug
kernel debug into an output messages from the kernel debug buffer into an output file.
file.
4 Stop the kernel debug. In this step, you configure Security Gateway to stop writing the
debug messages into an output file.
5 Restore the default kernel In this step, you restore the default kernel debug options.
debug settings.

Kernel Debug Syntax
To see the built-in help for the kernel debug

fw ctl debug -h
To restore the default kernel debug settings
n To reset all debug flags and enable only the default debug flags in all kernel modules:
fw ctl debug 0
n To disable all debug flags including the default flags in all kernel modules:
Best Practice - Do not run this command, because it disables even the basic default
debug messages.
fw ctl debug -x
To allocate the kernel debug buffer

fw ctl debug -buf 8200 [-v {"<List of VSIDs>" | all}] [-k]
Notes:
n Security Gateway allocates the kernel debug buffer with the specified size for every
CoreXL Firewall instance.
n The maximal supported buffer size is 8192 kilobytes..
To configure the debug modules and debug flags
n General syntax:
fw ctl debug [-d <Strings to Search>] [-v {"<List of VSIDs>" | all}]

-m <Name of Debug Module> {all | + <List of Debug Flags> | - <List
of Debug Flags>}
fw ctl debug [-s "<String to Stop Debug>"] [-v {"<List of VSIDs>" |

all}] -m <Name of Debug Module> {all | + <List of Debug Flags> | -
<List of Debug Flags>}
n To see a list of all debug modules and their flags:
Note - The list of kernel modules depends on the Software Blades you enabled on the
Security Gateway.
fw ctl debug -m
n To see a list of debug flags that are already enabled:
fw ctl debug
n To enable all debug flags in the specified kernel module:
fw ctl debug -m <Name of Debug Module> all
n To enable the specified debug flags in the specified kernel module:

Kernel Debug Syntax
fw ctl debug -m <Name of Debug Module> + <List of Debug Flags>
n To disable the specified debug flags in the specified kernel module:
fw ctl debug -m <Name of Debug Module> - <List of Debug Flags>
To collect the kernel debug output
n General syntax (only supported parameters are listed):
fw ctl kdebug [-p <List of Fields>] [-T] -f > /<Path>/<Name of

Output File>
fw ctl kdebug [-p <List of Fields>] [-T] -f -o /<Path>/<Name of

Output File> -m <Number of Cyclic Files> [-s <Size of Each Cyclic
File in KB>]
n To start the collection of the kernel debug into an output file:
fw ctl kdebug -T -f > /<Path>/<Name of Output File>
n To start collecting the kernel debug into cyclic output files:
fw ctl kdebug -T -f -o /<Path>/<Name of Output File> -m <Number of

Cyclic Files> [-s <Size of Each Cyclic File in KB>]
Parameters
Note - Only supported parameters are listed.
Table: Parameters of the 'fw ctl debug' command

Parameter Description
0 | -x Controls how to disable the debug flags:

n 0
Resets all debug flags and enables only the default debug flags
in all kernel modules.
n -x
Disables all debug flags, including the default flags in all kernel
modules.
Best Practice - Do not use the "-x" parameter, because it
disables even the basic default debug messages.

Kernel Debug Syntax
Table: Parameters of the 'fw ctl debug' command (continued)

-d <Strings to When you specify this parameter, the Security Gateway:

Search>
1. Examines the applicable debug messages based on the
enabled kernel debug modules and their debug flags.
2. Collects only debug messages that contain at least one of the
specified strings into the kernel debug buffer.
3. Writes the entire kernel debug buffer into the output file.
Notes:
n These strings can be any plain text (not a regular
expression) that you see in the debug messages.
n Separate the applicable strings by commas without
spaces:
-d String1,String2,...,StringN
n You can specify up to 10 strings, up to 250 characters in
total.
-s "<String to Stop When you specify this parameter, the Security Gateway:
Debug>"
1. Collects the applicable debug messages into the kernel debug
buffer based on the enabled kernel debug modules and their
debug flags.
2. Does not write any of these debug messages from the kernel
debug buffer into the output file.
3. Stops collecting all debug messages when it detects the first
debug message that contains the specified string in the kernel
debug buffer.
4. Writes the entire kernel debug buffer into the output file.
Notes:
n This one string can be any plain text (not a regular
expression) that you see in the debug messages.
n String length is up to 50 characters.
-m <Name of Debug Specifies the name of the kernel debug module, for which you print or
Module> configure the debug flags.

Kernel Debug Syntax

{all | + <List of Specifies which debug flags to enable or disable in the specified kernel
Debug Flags> | - debug module:
<List of Debug
n all
Flags>}
Enables all debug flags in the specified kernel debug module.
n + <List of Debug Flags>
Enables the specified debug flags in the specified kernel debug
module.
You must press the space bar key after the plus (+) character:
+ <Flag1> [<Flag2> ... <FlagN>]
Example: + drop conn
n - <List of Debug Flags>
Disables the specified debug flags in the specified kernel debug
module.
You must press the space bar key after the minus (-) character:
- <Flag1> [<Flag2> ... <FlagN>]
Example: - conn
-v {"<List of Specifies the list of Virtual Systems.

VSIDs>" | all} A VSX Gateway automatically filters the collected kernel debug
information for debug messages only for these Virtual Systems.
n -v "<List of VSIDs>"
Monitors the messages only from the specified Virtual Systems.
To specify the Virtual Systems, enter their VSID number
separated with commas and without spaces:
"VSID1[,VSID2,VSID3,...,VSIDn]"
Example: -v "1,3,7"
n -v all
Monitors the messages from all configured Virtual Systems.
Notes:
n This parameter is supported only in VSX mode.
n This parameter and the -k parameter are mutually
exclusive.

Kernel Debug Syntax

-e <Expression> Specifies the INSPECT filter for the debug:

-i <Name of Filter
n -e <Expression>
File>
-i - Specifies the INSPECT filter. See the R81 CLI Reference Guide
> section "fw monitor".
-u
n -i <Name of Filter File>
Specifies the file that contains the INSPECT filter.
n -i -
Specifies that the INSPECT filter arrives from the standard
input.
The Security Gateway prompts to enter the INSPECT filter on
the screen.
n -u - Removes the INSPECT debug filter.
Notes:
n These are legacy parameters ("-e" and "-i").
n When you use these parameters ("-e" and "-i"), the
Security Gateway cannot apply the specified INSPECT
filter to the accelerated traffic.
n For new debug filters, see "Kernel Debug Filters" on
page 210.
-z The Security Gateway processes some connections in both SecureXL

code and in the Host appliance code (for example, Passive Streaming
Library (PSL) - an IPS infrastructure, which transparently listens to
TCP traffic as network packets, and rebuilds the TCP stream out of
these packets.).
The Security Gateway processes some connections in only in the Host
appliance code.
When you use this parameter, kernel debug output contains the debug
messages only from the Host appliance code.
-k The Security Gateway processes some connections in both kernel

space code and in the user space code (for example, Web
Intelligence).
The Security Gateway processes some connections only in the kernel
space code.
When you use this parameter, kernel debug output contains the debug
messages only from the kernel space.
Notes:
n This parameter is not supported in the VSX mode, in which
the Firewall works in the user space.
n This parameter and the -v parameter are mutually
exclusive.

Kernel Debug Syntax

-p <List of Fields> By default, when the Security Gateway prints the debug messages, the
messages start with the applicable CPU ID and CoreXL Firewall
instance ID.
You can print additional fields in the beginning of each debug
message.
Notes:
n These fields are available:
all, proc, pid, date, mid, type, freq, topic, time,
ticks, tid, text, errno, host, vsid, cpu.
n When you specify the applicable fields, separate them with
commas and without spaces:
Field1,Field2,...,FieldN
n The more fields you specify, the higher the load on the
CPU and on the hard disk.
-T Prints the time stamp in microseconds in front of each debug message.

Best Practice - Always use this parameter to make the debug
analysis easier.
-f Collects the debug data until you stop the kernel debug in one of these
ways:
n When you press the CTRL+C keys.
n When you run the "fw ctl debug 0" command.
n When you run the "fw ctl debug -x" command.
n When you kill the "fw ctl kdebug" process.
/<Path>/<Name of Specifies the path and the name of the debug output file.
Output File> Best Practice - Always use the largest partition on the disk -
/var/log/. Security Gateway can generate many debug
messages within short time. As a result, the debug output file can
grow to large size very fast.
-o /<Path>/<Name of Saves the collected debug data into cyclic debug output files.
Output File> -m When the size of the current <Name of Output File> reaches the
<Number of Cyclic specified <Size of Each Cyclic File in KB> (more or less),
Files> [-s <Size of the Security Gateway renames the current <Name of Output
Each Cyclic File in File> to <Name of Output File>.0 and creates a new <Name
KB>] of Output File>.
If the <Name of Output File>.0 already exists, the Security
Gateway renames the <Name of Output File>.0 to <Name of
Output File>.1, and so on - until the specified limit <Number of
Cyclic Files>. When the Security Gateway reaches the <Number
of Cyclic Files>, it deletes the oldest files.
The valid values are:
n <Number of Cyclic Files> - from 1 to 999
n <Size of Each Cyclic File in KB> - from 1 to 2097150

Kernel Debug Filters

By default, kernel debug output contains information about all processed connections.
You can configure filters for kernel debug to collect debug messages only for the applicable connections.
There are three types of debug filters:
n By connection tuple parameters
n By an IP address parameter
n By a VPN peer parameter
To configure these kernel debug filters, assign the applicable values to the applicable kernel parameters
before you start the kernel debug.
You assign the values to the applicable kernel parameters temporarily with the "fw ctl set" command.
Notes:
n A Security Gateway supports:
l up to five Connection Tuple filters in total (from all types)
l up to three Host IP Address filters
l up to two VPN Peer filters
n A Security Gateway applies these debug filters to both the non-accelerated and
accelerated traffic.
n A Security Gateway applies these debug filters to "Kernel Debug Procedure with
Connection Life Cycle" on page 219.
Best Practice - It is usually simpler to set the Connection Tuple and Host IP Address filters from
within the "fw ctl debug" command (see the R81 CLI Reference Guide). To filter the kernel
debug by a VPN Peer, use the procedure below.

To configure debug filter of the type "By connection tuple parameters":

A Security Gateway processes connections based on the 5-tuple:
n Source IP address
n Source Port (see IANA Service Name and Port Number Registry)
n Destination IP address
n Destination Port (see IANA Service Name and Port Number Registry)
n Protocol Number (see IANA Protocol Numbers)
With this debug filter you can filter by these tuple parameters:
Tuple Parameter Syntax for Kernel Parameters
Source IP address fw ctl set str simple_debug_filter_saddr_<N> "<IPv4 or IPv6

Address>"
Source Ports fw ctl set int simple_debug_filter_sport_<N> <1-65535>
Destination IP fw ctl set str simple_debug_filter_daddr_<N> "<IPv4 or IPv6

address Address>"
Destination Ports fw ctl set int simple_debug_filter_dport_<N> <1-65535>
Protocol Number fw ctl set int simple_debug_filter_proto_<N> <0-254>

Notes:
1. <N> is an integer between 1 and 5. This number is an index for the configured kernel
parameters of this type.
2. When you specify IP addresses, you must enclose them in double quotes.
3. When you configure kernel parameters with the same index <N>, the debug filter is a
logical "AND" of these kernel parameters.
In this case, the final filter matches only one direction of the processed connection.
n Example 1 - packets from the source IP address X to the destination IP address Y:
simple_debug_filter_saddr_1 <Value X>

AND
simple_debug_filter_daddr_1 <Value Y>
n Example 2 - packets from the source IP address X to the destination port Y:
AND
simple_debug_filter_dport_1 <Value Y>
4. When you configure kernel parameters with the different indices <N>, the debug filter is a
logical "OR" of these kernel parameters.
This means that if it is necessary the final filter matches both directions of the connection,
then it is necessary to configure the applicable debug filters for both directions.
n Example 1 - packets either from the source IP address X, or to the destination
IP address Y:
OR
simple_debug_filter_daddr_2 <Value Y>
n Example 2 - packets either from the source IP address X, or to the destination port Y:
OR
simple_debug_filter_dport_2 <Value Y>
5. For information about the Port Numbers, see IANA Service Name and Port Number
Registry.
6. For information about the Protocol Numbers, see IANA Protocol Numbers.
To configure debug filter of the type "By an IP address parameter":

With this debug filter you can filter by one IP address, which is either the source or the destination IP
address of the packet.
Syntax for Kernel Parameters:
fw ctl set str simple_debug_filter_addr_<N> "<IPv4 or IPv6 Address>"

Notes:
1. <N> is an integer between 1 and 3.
This number is an index for the configured kernel parameters of this type.
2. You can configure one, two, or three of these kernel parameters at the same time.
n Example 1:
Configure one IP address (simple_debug_filter_addr_1).

n Example 2:
Configure two IP addresses (simple_debug_filter_addr_1 and simple_

debug_filter_addr_2).
This would match packets, where any of these IP addresses appears, either as a
source or a destination.
3. You must enclose the IP addresses in double quotes.
To configure debug filter of the type "By a VPN peer parameter":

With this debug filter you can filter by one IP address.
Syntax for Kernel Parameters:
fw ctl set str simple_debug_filter_vpn_<N> "<IPv4 or IPv6 Address>"

Notes:
1. <N> is an integer - 1 or 2.
This number is an index for the configured kernel parameters of this type.
2. You can configure one or two of these kernel parameters at the same time.
n Example 1:
Configure one VPN peer (simple_debug_filter_vpn_1).

n Example 2:
Configure two VPN peers (simple_debug_filter_vpn_1 and simple_debug_

filter_vpn_2).
3. You must enclose the IP addresses in double quotes.
To disable all debug filters:

You can disable all the configured debug filters of all types.
Syntax for Kernel Parameter:
fw ctl set int simple_debug_filter_off 1

Usage Example
It is necessary to show in the kernel debug the information about the connection from Source IP address
192.168.20.30 from any Source Port to Destination IP address 172.16.40.50 to Destination Port 80
(192.168.20.30:<Any> --> 172.16.40.50:80).
Run these commands before you start the kernel debug:

fw ctl set str simple_debug_filter_saddr_1 "192.168.20.30"
fw ctl set str simple_debug_filter_daddr_1 "172.16.40.50"
fw ctl set str simple_debug_filter_saddr_2 "172.16.40.50"
fw ctl set str simple_debug_filter_daddr_2 "192.168.20.30"
fw ctl set int simple_debug_filter_dport_1 80
fw ctl set int simple_debug_filter_sport_2 80
Important - In the above example, two Connection Tuple filters are used ("..._1" and "..._2") -
one for each direction, because we want the debug filter to match both directions of this
connection.

Kernel Debug Procedure

Alternatively, use the "Kernel Debug Procedure with Connection Life Cycle" on page 219.
Important:
n Debug increases the load on the CPU on the Security Gateway / Cluster
Members / Security Group Members. Schedule a maintenance window.
n We strongly recommend to connect over serial console to your Security
Gateway / each Cluster Member / Scalable Platform Security Group Members.
This is to prevent a possible issue when you cannot work with the CLI because
of a high load on the CPU.
n In Cluster, you must perform these steps on all the Cluster Members in the
same way.
n On Scalable Platforms (Maestro and Chassis), you must connect to the
Step Instructions
1 Connect to the command line on the Security Gateway / each Cluster Member over SSH, or
console.
Security Group.
3 Reset the kernel debug options.

fw ctl debug 0
g_fw ctl debug 0
4 Reset the kernel debug filters.

g_fw ctl set int simple_debug_filter_off 1
5 Configure the applicable kernel debug filters.

See "Kernel Debug Filters" on page 210.

Step Instructions
6 Allocate the kernel debug buffer for each CoreXL Firewall instance.
fw ctl debug -buf 8200
g_fw ctl debug -buf 8200
7 Make sure the kernel debug buffer was allocated.

fw ctl debug | grep buffer
g_fw ctl debug | grep buffer
8 Enable the applicable debug flags in the applicable kernel modules.

fw ctl debug -m <module> {all | + <flags>}
g_fw ctl debug -m <module> {all | + <flags>}
See "Kernel Debug Modules and Debug Flags" on page 224.

Important - The CPU load increases at this point because the Firewall kernel starts to
write some debug messages to the /var/log/messages file and the dmesg buffer.
9 Examine the list of the debug flags that are enabled in the specified kernel modules.
fw ctl debug -m <module>
g_fw ctl debug -m <module>
10 Save the kernel debug output to a file.

fw ctl kdebug -T -f > /var/log/kernel_debug.txt
g_fw ctl kdebug -T -f > /var/log/kernel_debug.txt
Important - The CPU load increases even more at this point because the Firewall starts
to write all debug messages to the output file.
11 Replicate the issue, or wait for the issue to occur.

Step Instructions
12 Stop the kernel debug output:

Press the CTRL+C keys.
Important - This does not stop all CPU load yet because the Firewall kernel continues to
write some debug messages to the /var/log/messages file and the dmesg buffer.
13 Reset the kernel debug options.

fw ctl debug 0
g_fw ctl debug 0
Important - This stops all CPU load from the kernel debug.
14 Reset the kernel debug filters.

g_fw ctl set int simple_debug_filter_off 1
15 Transfer this file from the Security Gateway / each Cluster Member / each Security Group
Member to your computer:
/var/log/kernel_debug.txt
Best Practice - Compress this file with the "tar -zxvf" command and transfer it from
the Security Gateway / each Cluster Member / each Security Group Members to your
computer. If you transfer to an FTP server, do so in the binary mode.
16 Analyze the debug output file.

Example - Connection 192.168.20.30:<Any> --> 172.16.40.50:80
[Expert@GW:0]# fw ctl debug 0

Defaulting all kernel debugging options
Debug state was reset to default.
[Expert@GW:0]#
[Expert@GW:0]# fw ctl set int simple_debug_filter_off 1
[Expert@GW:0]#
[Expert@GW:0]# fw ctl set str simple_debug_filter_saddr_1 "192.168.20.30"
[Expert@GW:0]#
[Expert@GW:0]# fw ctl set str simple_debug_filter_daddr_2 "192.168.20.40"
[Expert@GW:0]#
[Expert@GW:0]# fw ctl set int simple_debug_filter_dport_1 80
[Expert@GW:0]#
[Expert@GW:0]# fw ctl debug -buf 8200
Initialized kernel debugging buffer to size 8192K
[Expert@GW:0]#
[Expert@GW:0]# fw ctl debug | grep buffer
Kernel debugging buffer size: 8192KB
[Expert@GW:0]#
[Expert@GW:0]# fw ctl debug -m fw + conn drop
Updated kernel's debug variable for module fw
Debug flags updated.
[Expert@GW:0]#
[Expert@GW:0]# fw ctl debug -m fw
Module: fw
Enabled Kernel debugging options: error warning conn drop
Messaging threshold set to type=Info freq=Common
[Expert@GW:0]#
[Expert@GW:0]# fw ctl kdebug -T -f > /var/log/kernel_debug.txt
... ... Replicate the issue, or wait for the issue to occur ... ...
... ... Press CTRL+C ... ...
[Expert@GW:0]#
[Expert@GW:0]# fw ctl debug 0
[Expert@GW:0]#
[Expert@GW:0]# fw ctl set int simple_debug_filter_off 1
[Expert@GW:0]#
[Expert@GW:0]# ls -l /var/log/kernel_debug.txt
-rw-rw---- 1 admin root 1630619 Apr 12 19:49 /var/log/kernel_debug.txt
[Expert@GW:0]#

Kernel Debug Procedure with Connection Life Cycle
Kernel Debug Procedure with Connection Life

Cycle
Introduction
R80.20 introduced a new debug tool called Connection Life Cycle.
This tool generates a formatted debug output file that presents the debug messages hierarchically by
connections and packets:
n The first hierarchy level shows connections.
n After you expand the connection, you see all the packets of this connection.
Important - You must use this tool in the Expert mode together with the regular kernel debug flags
(see "Kernel Debug Modules and Debug Flags" on page 224).
Syntax
n To start the debug capture:
conn_life_cycle.sh -a start -o /<Path>/<Name of Raw Debug Output File>

[{-t | -T}] [[-f "<Filter1>"] [-f "<Filter2>"] [-f "<Filter3>] [-f
"<Filter4>] [-f "<Filter5>"]]
n To stop the debug capture and prepare the formatted debug output:
conn_life_cycle.sh -a stop -o /<Path>/<Name of Formatted Debug Output

File>
Parameters
Table: Parameters of the 'conn_life_cycle.sh' script
-a start Mandatory.
-a stop Specifies the action:
n start - Starts the debug capture based on the debug
flags you enabled and debug filters you specified.
n stop - Stops the debug capture, resets the kernel debug
options, resets the kernel debug filters.
-t | -T Optional.
Specifies the resolution of a time stamp in front of each debug
message:
n -t - Prints the time stamp in milliseconds.
n -T - Prints the time stamp in microseconds.
Best Practice - Always use the "-T" option to make the

debug analysis easier.

Table: Parameters of the 'conn_life_cycle.sh' script (continued)

-f "<Filter>" Optional.
Specifies which connections and packets to capture.
For additional information, see "Kernel Debug Filters" on
page 210.
Important - If you do not specify filters, then the tool prints
debug messages for all traffic. This causes high load on the
CPU and increases the time to format the debug output file.
Each filter must contain these five numbers (5-tuple) separated
with commas:
"<Source IP Address>,<Source
Port>,<Destination IP Address>,<Destination
Port>,<Protocol Number>"
Example of capturing traffic from IP 192.168.20.30 from any port
to IP 172.16.40.50 to port 22 over the TCP protocol:
-f "192.168.20.30,0,172.16.40.50,22,6"
Notes:
n The tool supports up to five of such filters.
n The tool treats the value 0 (zero) as "any".
n If you specify two or more filters, the tool performs a
logical "OR" of all the filters on each packet.
If the packet matches at least one filter, the tool prints
the debug messages for this packet.
n "<Source IP Address>" and "<Destination
IP Address>" - IPv4 or IPv6 address
n "<Source Port>" and "<Destination Port>" -
integers from 1 to 65535 (see IANA Service Name
and Port Number Registry)
n <Protocol Number> - integer from 0 to 254 (see
IANA Protocol Numbers)
-o /<Path>/<Name of Raw Mandatory.

Debug Output File> Specifies the absolute path and the name of the raw debug
output file.
Example:
-o /var/log/kernel_debug.txt
-o /<Path>/<Name of Mandatory.
Formatted Debug Output Specifies the absolute path and the name of the formatted debug
File> output file (to analyze by an administrator).
Example:
-o /var/log/kernel_debug_formatted.txt

Procedure
Important - In cluster, you must perform these steps on all the Cluster Members in the same way.
Step Instructions
3 Enable the applicable debug flags in the applicable kernel modules:

fw ctl debug -m <module> {all | + <flags>}
See "Kernel Debug Modules and Debug Flags" on page 224.
4 Examine the list of the debug flags that are enabled in the specified kernel modules:
fw ctl debug -m <module>
5 Start the debug capture:

conn_life_cycle.sh -a start -o /var/log/kernel_debug.txt -T -f
"<Filter1>" [... [-f "<FilterN>"]]
6 Replicate the issue, or wait for the issue to occur.
7 Stop the debug capture and prepare the formatted debug output:
conn_life_cycle.sh -a stop -o /var/log/kernel_debug_formatted.txt
8 Transfer the formatted debug output file from your Security Gateway to your desktop or laptop
computer:
/var/log/kernel_debug_formatted.txt
9 Examine the formatted debug output file in an advanced text editor like Notepad++ (click
Language > R > Ruby), or any other Ruby language viewer.

Example
Collecting the kernel debug for TCP connection from IP 172.20.168.15 (any port) to IP
192.168.3.53 and port 22
[Expert@GW:0]# fw ctl debug -m fw + conn drop
Updated kernel's debug variable for module fw
Debug flags updated.
[Expert@GW:0]#
HOST:
Module: fw
Enabled Kernel debugging options: error warning conn drop
[Expert@GW:0]#
[Expert@GW:0]# conn_life_cycle.sh -a start -o /var/log/kernel_debug.txt -T -f
"172.20.168.15,0,192.168.3.53,22,6"
Initialized kernel debugging buffer to size 8192K
Capturing started...
[Expert@GW:0]#
... ... Replicate the issue, or wait for the issue to occur ... ...
[Expert@GW:0]#
[Expert@GW:0]# conn_life_cycle.sh -a stop -o /var/log/kernel_debug_formatted.txt
doing unification...
Openning host debug file /tmp/tmp.KiWmF18217... OK
New unified debug file: /tmp/tmp.imzMZ18220... OK
prepare unification
performing unification
Done :-)
doing grouping...
wrapping connections and packets...
Some of packets lack description, probably because they were already handled when the feature was enabled.
[Expert@GW:0]#
HOST:
Module: fw
Enabled Kernel debugging options: error warning
[Expert@GW:0]
[Expert@GW:0] ls -l /var/log/kernel_debug.*
-rw-rw---- 1 admin root 40960 Nov 26 13:02 /var/log/kernel_debug.txt
-rw-rw---- 1 admin root 24406 Nov 26 13:02 /var/log/kernel_debug_formatted.txt
[Expert@GW:0]

Opening the kernel debug in Notepad++
Everything is collapsed:
Connection with 1st packet already in handling so no conn details

[+]
{+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++
Opened the first hierarchy level to see the connection:

[-]
{+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++
;26Nov2018 13:02:06.736016;[cpu_2];[fw4_1];Packet 0xffff8101ea45e680 is INBOUND;
[+]{---------------------------------------------------------- packet begins -----------------------------
-------------------------
Opened the second hierarchy level to see the packets of this connection:

[-]
{+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++
;26Nov2018 13:02:06.736016;[cpu_2];[fw4_1];Packet 0xffff8101ea45e680 is INBOUND;
[-]{---------------------------------------------------------- packet begins -----------------------------
-------------------------
;26Nov2018 13:02:06.736021;[cpu_2];[fw4_1];Packet 0xffff8101ea45e680 is entering CHAIN_MODULES_ENTER;
;26Nov2018 13:02:06.736035;[cpu_2];[fw4_1];#fwconn_lookup_cache: conn <dir 0, 172.20.168.15:57821 ->
192.168.3.53:22 IPP 6>;
;26Nov2018 13:02:06.736046;[cpu_2];[fw4_1];#<1c001,44000,2,1e2,0,UUID: 5bfbc2a2-0000-0000-c0-a8-3-35-1-0-
0-c0, 1,1,ffffffff,ffffffff,40800,0,80,OPQS:
[0,ffffc20033d220f0,0,0,0,0,ffffc20033958648,0,0,0,ffffc200325d57b0,0,0,0,0,0],0,0,0,0,0,0,0,0,0,0,0,0,0,
0>
;26Nov2018 13:02:06.736048;[cpu_2];[fw4_1];CONN LIFE CYCLE: lookup: found;
;26Nov2018 13:02:06.736053;[cpu_2];[fw4_1];Packet 0xffff8101ea45e680 is entering VM_ENTER;
;26Nov2018 13:02:06.736055;[cpu_2];[fw4_1];#
;26Nov2018 13:02:06.736060;[cpu_2];[fw4_1];#Before VM: <dir 0, 172.20.168.15:57821 -> 192.168.3.53:22 IPP
6> (len=40) TCP flags=0x10 (ACK), seq=686659054, ack=4181122096, data end=686659054 (ifn=1) (first seen)
(looked up) ;
;26Nov2018 13:02:06.736068;[cpu_2];[fw4_1];#After VM: <dir 0, 172.20.168.15:57821 -> 192.168.3.53:22 IPP
6> (len=40) TCP flags=0x10 (ACK), seq=686659054, ack=4181122096, data end=686659054 ;
;26Nov2018 13:02:06.736071;[cpu_2];[fw4_1];#VM Final action=ACCEPT;
;26Nov2018 13:02:06.736072;[cpu_2];[fw4_1];# ----- Stateful VM inbound Completed -----
;26Nov2018 13:02:06.736075;[cpu_2];[fw4_1];Packet 0xffff8101ea45e680 is exiting VM_EXIT;
;26Nov2018 13:02:06.736081;[cpu_2];[fw4_1];Packet 0xffff8101ea45e680 is entering POST VM_ENTER;
;26Nov2018 13:02:06.736083;[cpu_2];[fw4_1];#
;26Nov2018 13:02:06.736085;[cpu_2];[fw4_1];#fw_post_vm_chain_handler: (first_seen 32, new_conn 0, is_my_ip
0, is_first_packet 0);
;26Nov2018 13:02:06.736089;[cpu_2];[fw4_1];#Before POST VM: <dir 0, 172.20.168.15:57821 -> 192.168.3.53:22
IPP 6> (len=40) TCP flags=0x10 (ACK), seq=686659054, ack=4181122096, data end=686659054 (ifn=1) (first
seen) (looked up) ;
;26Nov2018 13:02:06.736095;[cpu_2];[fw4_1];#After POST VM: <dir 0, 172.20.168.15:57821 -> 192.168.3.53:22
IPP 6> (len=40) TCP flags=0x10 (ACK), seq=686659054, ack=4181122096, data end=686659054 ;
;26Nov2018 13:02:06.736097;[cpu_2];[fw4_1];#POST VM Final action=ACCEPT;
;26Nov2018 13:02:06.736098;[cpu_2];[fw4_1];# ----- Stateful POST VM inbound Completed -----
;26Nov2018 13:02:06.736101;[cpu_2];[fw4_1];Packet 0xffff8101ea45e680 is exiting POST VM_EXIT;
;26Nov2018 13:02:06.736104;[cpu_2];[fw4_1];#fwconnoxid_msg_get_cliconn: warning - failed to get connoxid
message.;
;26Nov2018 13:02:06.736107;[cpu_2];[fw4_1];Packet 0xffff8101ea45e680 is entering CPAS_ENTER;
;26Nov2018 13:02:06.736110;[cpu_2];[fw4_1];Packet 0xffff8101ea45e680 is exiting CPAS_EXIT;
;26Nov2018 13:02:06.736113;[cpu_2];[fw4_1];Packet 0xffff8101ea45e680 is exiting CHAIN_MODULES_EXIT;
;26Nov2018 13:02:06.736116;[cpu_2];[fw4_1];Packet 0xffff8101ea45e680 is ACCEPTED;
}
;26Nov2018 13:02:06.770652;[cpu_2];[fw4_1];Packet 0xffff8101ea128580 is INBOUND;

Kernel Debug Modules and Debug Flags

This section describes the Kernel Debug Modules and their Debug Flags.
To see the available kernel debug modules and their debug flags, run:
fw ctl debug -m
List of kernel debug modules (in alphabetical order):

n "Module 'accel_apps' (Accelerated Applications)" on page 226
n "Module 'accel_pm_mgr' (Accelerated Pattern Match Manager)" on page 227
n "Module 'APPI' (Application Control Inspection)" on page 228
n "Module 'BOA' (Boolean Analyzer for Web Intelligence)" on page 230
n "Module 'CI' (Content Inspection)" on page 231
n "Module 'cluster' (ClusterXL)" on page 233
n "Module 'cmi_loader' (Context Management Interface / Infrastructure Loader)" on page 236
n "Module 'CPAS' (Check Point Active Streaming)" on page 238
n "Module 'cpcode' (Data Loss Prevention - CPcode)" on page 239
n "Module 'CPSSH' (SSH Inspection)" on page 240
n "Module 'crypto' (SSL Inspection)" on page 242
n "Module 'dlpda' (Data Loss Prevention - Download Agent for Content Awareness)" on page 243
n "Module 'dlpk' (Data Loss Prevention - Kernel Space)" on page 245
n "Module 'dlpuk' (Data Loss Prevention - User Space)" on page 246
n "Module 'DOMO' (Domain Objects)" on page 247
n "Module 'fg' (FloodGate-1 - QoS)" on page 248
n "Module 'FILE_SECURITY' (File Inspection)" on page 250
n "Module 'FILEAPP' (File Application)" on page 251
n "Module 'fw' (Firewall)" on page 252
n "Module 'gtp' (GPRS Tunneling Protocol)" on page 258
n "Module 'h323' (VoIP H.323)" on page 260
n "Module 'ICAP_CLIENT' (Internet Content Adaptation Protocol Client)" on page 261
n "Module 'IDAPI' (Identity Awareness API)" on page 263
n "Module 'kiss' (Kernel Infrastructure)" on page 264
n "Module 'kissflow' (Kernel Infrastructure Flow)" on page 267
n "Module 'MALWARE' (Threat Prevention)" on page 268
n "Module 'multik' (Multi-Kernel Inspection - CoreXL)" on page 269
n "Module 'MUX' (Multiplexer for Applications Traffic)" on page 271

n "Module 'NRB' (Next Rule Base)" on page 273

n "Module 'PSL' (Passive Streaming Library)" on page 275
n "Module 'RAD_KERNEL' (Resource Advisor - Kernel Space)" on page 276
n "Module 'RTM' (Real Time Monitoring)" on page 277
n "Module 'seqvalid' (TCP Sequence Validator and Translator)" on page 279
n "Module 'SFT' (Stream File Type)" on page 280
n "Module 'SGEN' (Struct Generator)" on page 281
n "Module 'synatk' (Accelerated SYN Defender)" on page 282
n "Module 'TPUTILS' (Threat Prevention Utilities)" on page 283
n "Module 'UC' (UserCheck)" on page 284
n "Module 'UP' (Unified Policy)" on page 285
n "Module 'upconv' (Unified Policy Conversion)" on page 287
n "Module 'UPIS' (Unified Policy Infrastructure)" on page 288
n "Module 'VPN' (Site-to-Site VPN and Remote Access VPN)" on page 290
n "Module 'WS' (Web Intelligence)" on page 293
n "Module 'WS_SIP' (Web Intelligence VoIP SIP Parser)" on page 296
n "Module 'WSIS' (Web Intelligence Infrastructure)" on page 298

Module 'accel_apps' (Accelerated Applications)
Module 'accel_apps' (Accelerated Applications)

Syntax
n On the Security Gateway / each Cluster Member, run in the Expert mode:
fw ctl debug -m accel_apps + {all | <List of Debug Flags>}
g_fw ctl debug -m accel_apps + {all | <List of Debug Flags>}
Flag Description
av_lite Content Inspection (Anti-Virus) Lite application -

general information about packet processing
cmi_lite Context Management Interface / Infrastructure Lite application -

daf_lite Decrypt & Forward Lite application -

daf_lite_dump Decrypt & Forward Lite application -

writes the contents of the internal buffer
error General errors
info General information
rad_lite Resource Advisor Lite application -

general information about internal connection processing
warning General warnings

Module 'accel_pm_mgr' (Accelerated Pattern Match Manager)
Module 'accel_pm_mgr' (Accelerated Pattern Match

Manager)
Syntax
fw ctl debug -m accel_pm_mgr + {all | <List of Debug Flags>}
g_fw ctl debug -m accel_pm_mgr + {all | <List of Debug Flags>}
Flag Description
debug Operations in the Accelerated Pattern Match Manager module
error General errors and failures
flow Internal flow of functions
submit_error General failures to submit the data for analysis
warning General warnings and failures

Module 'APPI' (Application Control Inspection)

Syntax
fw ctl debug -m APPI + {all | <List of Debug Flags>}
g_fw ctl debug -m APPI + {all | <List of Debug Flags>}
Flag Description
account Accounting information
address Information about connection's IP address
btime Browse time
connection Application Control connections
coverage Coverage times (entering, blocking, and time spent)
global Global policy operations
limit Application Control limits
memory Memory allocation operations
module Operations in the Application Control module (initialization, module loading, calls to
the module, policy loading, and so on)
observer Classification Object (CLOB) observer (data classification)
policy Application Control policy
referrer Application Control referrer
subject Prints the debug subject of each debug message
timestamp Prints the timestamp for each debug message (changes when you enable the debug
flag 'coverage')
urlf_ssl Application Control and URL Filtering for SSL
verbose Prints additional information (used with other debug flags)
vs Prints the VSID of the debugged Virtual System

Flag Description

Module 'BOA' (Boolean Analyzer for Web Intelligence)
Module 'BOA' (Boolean Analyzer for Web Intelligence)

Syntax
fw ctl debug -m BOA + {all | <List of Debug Flags>}
g_fw ctl debug -m BOA + {all | <List of Debug Flags>}
Flag Description
analyzer Operations in the BOA module
disasm Disassembler information
fatal Fatal errors
flow Operations in the BOA module
lock Information about internal locks in the FireWall kernel
spider Internal hash tables
stat Statistics
stream Memory allocation when processing streamed data

Module 'CI' (Content Inspection)

Syntax
fw ctl debug -m CI + {all | <List of Debug Flags>}
g_fw ctl debug -m CI + {all | <List of Debug Flags>}
Flag Description
address Prints connection addresses (as Source_IP:Source_Port -> Dest_IP:Dest_

Port)
av Anti-Virus inspection
crypto Basic information about encryption and decryption
fatal Fatal errors
filter Basic information about URL filters
ioctl Currently is not used
module Operations in the Content Inspection module (initialization, module loading, calls to the
module, policy loading, and so on)
policy Content Inspection policy
profile Basic information about the Content Inspection module (initialization, destroying,
freeing)
regexp Regular Expression library
session Session layer
stat Content Inspection statistics
flag 'coverage')

Flag Description
track Use only for very limited important debug prints, so it can be used in a loaded
environment -
Content-Disposition, Content-Type, extension validation, extension matching
uf URL filters and URL cache

Module 'cluster' (ClusterXL)

Syntax
fw ctl debug -m cluster + {all | <List of Debug Flags>}
g_fw ctl debug -m cluster + {all | <List of Debug Flags>}
Notes:
n To print all synchronization operations in Check Point cluster in the debug output, enable
these debug flags:
l The debug flag "sync" in "Module 'fw' (Firewall)" on page 252
l The debug flag "sync" in "Module 'CPAS' (Check Point Active Streaming)" on
page 238
n To print the contents of the packets in HEX format in the debug output (as "FW-1: fwha_
print_packet: Buffer ..."), before you start the kernel debug, set this kernel
parameter on each Cluster Member / the applicable Scalable Platform Security Group:
l On the Security Gateway / each Cluster Member, run in the Expert mode:
fw ctl set int fwha_dprint_io 1

l On the Scalable Platform Security Group, run in the Expert mode:
g_fw ctl set int fwha_dprint_io 1
n To print all network checks in the debug output, before you start the kernel debug, set this
kernel parameter on each Cluster Member:
l On the Security Gateway / each Cluster Member, run in the Expert mode:
fw ctl set int fwha_dprint_all_net_check 1

l On the Scalable Platform Security Group, run in the Expert mode:
g_fw ctl set int fwha_dprint_all_net_check 1
Flag Description
arp ARP Forwarding (see sk111956)
autoccp Operations of CCP in Auto mode
ccp Reception and transmission of Cluster Control Protocol (CCP) packets
cloud Replies to the probe packets in CloudGuard IaaS
conf Cluster configuration and policy installation
correction Correction Layer
cu Connectivity Upgrade (see sk107042)

Flag Description
drop Connections dropped by the cluster Decision Function (DF) module (does not include
CCP packets)
forward Forwarding Layer messages (when Cluster Members send and receive a forwarded
packet)
if Interface tracking and validation (all the operations and checks on interfaces)
ifstate Interface state (all the operations and checks on interfaces)
io Information about sending of packets through cluster interfaces
log Creating and sending of logs by cluster

Note - In addition, enable the debug flag "log" in "Module 'fw' (Firewall)" on
page 252.
mac Current configuration of and detection of cluster interfaces
Note - In addition, enable the debug flags "conf" and "if" in this debug module
mmagic Operations on "MAC magic" (getting, setting, updating, initializing, dropping, and so
on)
msg Handling of internal messages between Cluster Members
multik Processing of connections in CoreXL Firewall instances

Notes:
n In addition, see "Module 'multik' (Multi-Kernel Inspection - CoreXL)" on
page 269.
n If you use the QoS Software Blade, enable the debug flag "multik" in
the "Module 'fg' (FloodGate-1 - QoS)" on page 248.
osp Only for Scalable Platforms:

Distribution of connections between Security Group Members
pivot Operation of ClusterXL in Load Sharing Unicast mode (Pivot mode)
pnote Registration and monitoring of Critical Devices (pnotes)
select Packet selection (includes the Decision Function)
smo Only for Scalable Platforms:

Processing of connections on the SMO Security Group Member
stat States of cluster members (state machine)
subs Subscriber module (set of APIs, which enable user space processes to be aware of
the current state of the ClusterXL state machine and other clustering configuration
parameters)

Flag Description
timer Reports of cluster internal timers
trap Sending trap messages from the cluster kernel to the RouteD daemon about Master
change
unisync Only for Scalable Platforms:

Unicast Sync - synchronization of connections to backup Security Group Members
on the local Maestro Site / Scalable Chassis and to one Security Group Member one
the standby Maestro Site / Scalable Chassis

Module 'cmi_loader' (Context Management Interface / Infrastructure Loader)
Module 'cmi_loader' (Context Management Interface /

Infrastructure Loader)
Syntax
fw ctl debug -m cmi_loader + {all | <List of Debug Flags>}
g_fw ctl debug -m cmi_loader + {all | <List of Debug Flags>}
Flag Description
connection Internal messages about connection
cpcode DLP CPcode

Note - Also see "Module 'cpcode' (Data Loss Prevention - CPcode)" on
page 239.
global_ User Space global state structures

states
inspect INSPECT code
module Operations in the Context Management Interface / Infrastructure Loader module

(initialization, module loading, calls to the module, contexts, and so on)
parsers_is Module parsers infrastructure
policy Policy installation
sigload Signatures, patterns, ranges
flag 'coverage')

Module 'cmi_loader' (Context Management Interface / Infrastructure Loader)
Flag Description

Module 'CPAS' (Check Point Active Streaming)
Module 'CPAS' (Check Point Active Streaming)

Syntax
fw ctl debug -m CPAS + {all | <List of Debug Flags>}
g_fw ctl debug -m CPAS + {all | <List of Debug Flags>}
Flag Description
api Interface layer messages
conns Detailed description of connections, and connection's limit-related messages
cpconntim Information about internal timers
events Event-related messages
ftp Messages of the FTP example server
glue Glue layer messages
http Messages of the HTTP example server
icmp Messages of the ICMP example server
notify E-mail Messaging Security application
pkts Packets handling messages (allocation, splitting, resizing, and so on)
skinny Processing of Skinny Client Control Protocol (SCCP) connections
sync Synchronization operations in cluster

Note - Also see the debug flag "sync" in "Module 'fw' (Firewall)" on
page 252.
tcp TCP processing messages
tcpinfo TCP processing messages - more detailed description
timer Reports of internal timer ticks
Warning - Prints many messages, without real content.

Module 'cpcode' (Data Loss Prevention - CPcode)
Module 'cpcode' (Data Loss Prevention - CPcode)

Syntax
fw ctl debug -m cpcode + {all | <List of Debug Flags>}
g_fw ctl debug -m cpcode + {all | <List of Debug Flags>}
Note - Also see:

n "Module 'dlpda' (Data Loss Prevention - Download Agent for Content Awareness)" on
page 243
Flag Description
cplog Resolving of names and IP addresses for Check Point logs
csv Creation of CSV files
echo Prints the function that called the CPcode module
init Initializing of CPcode system
io Input / Output functionality for CPcode module
ioctl IOCTL control messages to kernel
kisspm Kernel Infrastructure Pattern Matcher
persist Operations on persistence domains
policy Policy operations
run Policy operations
url Operations on URLs
vm Virtual Machine execution

Module 'CPSSH' (SSH Inspection)

R80.40 introduced SSH Deep Packet Inspection - decryption / encryption of SSH, extraction of files from
SFTP/SCP, blocking of SSH port forwarding, and so on.
Syntax
fw ctl debug -m CPSSH + {all | <List of Debug Flags>}
g_fw ctl debug -m CPSSH + {all | <List of Debug Flags>}
Important - Also enable the debug flag "cpsshi" in "Module 'fw' (Firewall)" on page 252.
Flag Description
authentication Detailed information about authentication
binary_packet Detailed information about packets
conn_proto Detailed information about connections
crypto Encryption and decryption

Note - Also see "Module 'crypto' (SSL
Inspection)" on page 242.
dump Dumps the connection buffer
mux_auth_app Information about authentication

Note - Also see "Module 'MUX' (Multiplexer
for Applications Traffic)" on page 271.
mux_conn_app Information about connections

mux_decrypt_app Information about decryption of connections


Flag Description
mux_encrypt_app Information about encryption of connections

mux_inf Internal flow

mux_stream Internal flow

probe Information about connections
session Internal flow
sftp_parser Parser of SFTP / SCP connections
state_machine Information about the module State Machine
trans_proto Information about client and server communication

Module 'crypto' (SSL Inspection)
Module 'crypto' (SSL Inspection)

Syntax
fw ctl debug -m crypto + {all | <List of Debug Flags>}
g_fw ctl debug -m crypto + {all | <List of Debug Flags>}
Flag Description

Module 'dlpda' (Data Loss Prevention - Download Agent for Content Awareness)
Module 'dlpda' (Data Loss Prevention - Download Agent for

Content Awareness)
Syntax
fw ctl debug -m dlpda + {all | <List of Debug Flags>}
g_fw ctl debug -m dlpda + {all | <List of Debug Flags>}
Note - Also see:

n "Module 'cpcode' (Data Loss Prevention - CPcode)" on
page 239
n "Module 'dlpk' (Data Loss Prevention - Kernel Space)" on
page 245
n "Module 'dlpuk' (Data Loss Prevention - User Space)" on
page 246
Flag Description
cmi Context Management Interface / Infrastructure operations
ctx Operations on DLP context
engine Content Awareness engine module
filecache Content Awareness file caching
mngr Currently is not used
module Initiation / removal of the Content Awareness infrastructure
observer Classification Object (CLOB) observer (data classification)
policy Content Awareness policy
slowpath Currently is not used

Module 'dlpda' (Data Loss Prevention - Download Agent for Content Awareness)
Flag Description
flag 'coverage')

Module 'dlpk' (Data Loss Prevention - Kernel Space)
Module 'dlpk' (Data Loss Prevention - Kernel Space)

Syntax
fw ctl debug -m dlpk + {all | <List of Debug Flags>}
g_fw ctl debug -m dlpk + {all | <List of Debug Flags>}
Note - Also see:

page 243
Flag Description
cmi HTTP Proxy, connection redirection, identity information, Async
drv DLP inspection
identity User identity, connection identity, Async
rulebase DLP rulebase match
stat Counter statistics

Module 'dlpuk' (Data Loss Prevention - User Space)
Module 'dlpuk' (Data Loss Prevention - User Space)

Syntax
fw ctl debug -m dlpuk + {all | <List of Debug Flags>}
g_fw ctl debug -m dlpuk + {all | <List of Debug Flags>}
Note - Also see:

page 243
Flag Description
buffer Currently is not used
module Initiation / removal of the Data Loss Prevention User Space modules' infrastructure
policy Currently is not used
serialize Data buffers and data sizes
flag 'coverage')

Module 'DOMO' (Domain Objects)
Module 'DOMO' (Domain Objects)

Syntax
fw ctl debug -m DOMO + {all | <List of Debug Flags>}
g_fw ctl debug -m DOMO + {all | <List of Debug Flags>}
Flag Description
conn Internal processing of connections
module Operations in the Domain Objects module (initialization, module loading, calls to the
policy Currently is not used

Module 'fg' (FloodGate-1 - QoS)

Syntax
fw ctl debug -m fg + {all | <List of Debug Flags>}
g_fw ctl debug -m fg + {all | <List of Debug Flags>}
Flag Description
chain Tracing each packet through FloodGate-1 stages in the cookie chain
chainq Internal Chain Queue mechanism - holding and releasing of packets during critical
actions (policy installation and uninstall)
classify Classification of connections to QoS rules
conn Processing and identification of connection
dns DNS classification mechanism
drops Dropped packets due to WFRED policy
dropsv Dropped packets due to WFRED policy - with additional debug information (verbose)
flow Internal flow of connections (direction, interfaces, buffers, and so on)
fwrate Rate statistics for each interface and direction
general Currently is not used
install Policy installation
llq Low latency queuing
log Everything related to calls in the log
ls Processing of connections in ClusterXL in Load Sharing Mode

Flag Description

Notes:
n In addition, see "Module 'multik' (Multi-Kernel Inspection - CoreXL)" on
page 269.
n In a cluster, enable the debug flag "multik" in the "Module 'cluster'
(ClusterXL)" on page 233.
n If you use the IPsec VPN Software Blade, enable the debug flag "multik"
in the "Module 'VPN' (Site-to-Site VPN and Remote Access VPN)" on
page 290.
pkt Packet recording mechanism
policy QoS policy rules matching
qosaccel Acceleration of QoS traffic
rates Rule and connection rates (IQ Engine behavior and status)
rtm Failures in information gathering in the Real Time Monitoring module
Note - In addition, see "Module 'RTM' (Real Time Monitoring)" on page 277.
sched Basic scheduling information
tcp TCP streaming (re-transmission detection) mechanism
time Currently is not used
timers Reports of internal timer ticks
Warning - Prints many messages, without real content.
url URL and URI for QoS classification

Module 'FILE_SECURITY' (File Inspection)
Module 'FILE_SECURITY' (File Inspection)

Syntax
fw ctl debug -m FILE_SECURITY + {all | <List of Debug Flags>}
g_fw ctl debug -m FILE_SECURITY + {all | <List of Debug Flags>}
Note - Also see "Module 'WSIS' (Web Intelligence Infrastructure)" on page 298.
Flag Description
cache File cache
global Global operations
memory Currently is not used
module Operations in the FILE_SECURITY module (identification and processing of connections)

Module 'FILEAPP' (File Application)
Module 'FILEAPP' (File Application)

Syntax
fw ctl debug -m FILEAPP + {all | <List of Debug Flags>}
g_fw ctl debug -m FILEAPP + {all | <List of Debug Flags>}
Flag Description
filetype Information about processing a file type
global Allocation and creation of global object
module Operations in the FILEAPP module (initialization, module loading, calls to the module,
and so on)
normalize File normalization operations (internal operations)
parser File parsing
flag 'coverage')
upload File upload operations

Module 'fw' (Firewall)

Syntax
fw ctl debug -m fw + {all | <List of Debug Flags>}
g_fw ctl debug -m fw + {all | <List of Debug Flags>}
Flag Description
acct Accounting data in logs for Application Control (in addition, enable the debug of
"Module 'APPI' (Application Control Inspection)" on page 228)
advp Advanced Patterns (signatures over port ranges) - runs under ASPII and CMI
aspii Accelerated Stateful Protocol Inspection Infrastructure (INPSECT streaming)
balance ConnectControl - logical servers in kernel, load balancing
bridge Bridge mode
bypass_timer Universal Bypass on CoreXL Firewall Instances during load
caf Mirror and Decrypt feature - only mirror operations on all traffic
cgnat Carrier Grade NAT (CGN/CGNAT)
chain Connection Chain modules, cookie chain
chainfwd Chain forwarding - related to cluster kernel parameter fwha_perform_chain_

forwarding
cifs Processing of Microsoft Common Internet File System (CIFS) protocol
citrix Processing of Citrix connections
cmi Context Management Interface / Infrastructure - IPS signature manager
conn Processing of all connections
connstats Connections statistics for Evaluation of Heavy Connections in CPView (see

sk105762)
content Anti-Virus content inspection
context Operations on Memory context and CPU context in "Module 'kiss' (Kernel
Infrastructure)" on page 264

Flag Description
cookie Virtual de-fragmentation , cookie issues (cookies in the data structure that holds the
packets)
corr Correction layer
cpsshi SSH Inspection

Important - In addition, enable all the debug flags in "Module 'CPSSH' (SSH
Inspection)" on page 240.
cptls CRYPTO-PRO Transport Layer Security (HTTPS Inspection) - Russian VPN GOST
crypt Encryption and decryption of packets (algorithms and keys are printed in clear text
and cipher text)
cvpnd Processing of connections handled by the Mobile Access daemon
dfilter Operations in the debug filters (see "Kernel Debug Filters" on page 210)
dlp Processing of Data Loss Prevention connections
dnstun DNS tunnels
domain DNS queries
dos DDoS attack mitigation (part of IPS)
driver Check Point kernel attachment (access to kernel is shown as log entries)
drop Reason for (almost) every dropped packet
drop_tmpl Operations in Drop Templates
dynlog Dynamic log enhancement (INSPECT logs)
epq End Point Quarantine (and AMD)
event Event App features (DNS, HTTP, SMTP, FTP)
ex Expiration issues (time-outs) in dynamic kernel tables
fast_accel Fast acceleration of connections
filter Packet filtering performed by the Check Point kernel and all data loaded into kernel
ftp Processing of FTP Data connections (used to call applications over FTP Data - i.e.,
Anti-Virus)

Flag Description
handlers Operations related to the Context Management Interface / Infrastructure Loader

Note - In addition, see "Module 'cmi_loader' (Context Management Interface /
Infrastructure Loader)" on page 236.
highavail Cluster configuration - changes in the configuration and information about interfaces
during
traffic processing
hold Holding mechanism and all packets being held / released
icmptun ICMP tunnels
if interface-related information (accessing the interfaces, installing a filter on an

interfaces)
install Driver installation - NIC attachment (actions performed by the "fw ctl install"
and "fw ctl uninstall" commands)
integrity Integrity Client (enforcement cooperation)
ioctl IOCTL control messages (communication between kernel and daemons, loading and
unloading of the FireWall)
ipopt Enforcement of IP Options
ips IPS logs and IPS IOCTL
ipv6 Processing of IPv6 traffic
kbuf Kernel-buffer memory pool (for example, encryption keys use these memory
allocations)
ld Kernel dynamic tables infrastructure (reads from / writes to the tables)
Warning - Security Gateway can freeze or hang due to very high CPU load!.
leaks Memory leak detection mechanism
link Creation of links in Connections kernel table (ID 8158)
log Everything related to calls in the log
machine INSPECT Virtual Machine (actual assembler commands being processed)
Warning - Security Gateway can freeze or hang due to very high CPU load!.
mail Issues with e-mails over POP3, IMAP

Flag Description
malware Matching of connections to Threat Prevention Layers (multiple rulebases)
Note - In addition, see "Module 'MALWARE' (Threat Prevention)" on page 268.
media Does not apply anymore

Only on Security Gateway that runs on Windows OS:
Transport Driver Interface information (interface-related information)
mgcp Media Gateway Control Protocol (complementary to H.323 and SIP)
misc Miscellaneous helpful information (not shown with other debug flags)
misp ISP Redundancy
monitor Prints output similar to the "fw monitor" command (see the R81 CLI Reference
Guide > section "fw monitor")
Note - In addition, enable the debug flag "misc" in this module.
monitorall Prints output similar to the "fw monitor -p all" command (see the R81 CLI
Reference Guide > section "fw monitor")
Note - In addition, enable the debug flag "misc" in this module.
mrtsync Synchronization between cluster members of Multicast Routes that are added when
working with Dynamic Routing Multicast protocols
msnms MSN over MSMS (MSN Messenger protocol)

In addition, always enable the debug flag 'sip' in this module

Notes:
n This debug flag enables all the debug flags in the "Module 'multik' (Multi-
Kernel Inspection - CoreXL)" on page 269, except for the debug flag
"packet".
n If you use the IPsec VPN Software Blade, enable the debug flag
"multik" in the "Module 'VPN' (Site-to-Site VPN and Remote Access
VPN)" on page 290.
n If you use the QoS Software Blade, enable the debug flag "multik" in
the "Module 'fg' (FloodGate-1 - QoS)" on page 248.
nac Network Access Control (NAC) feature in Identity Awareness
nat NAT issues - basic information
nat_hitcount Hit Count in NAT Rule Base

Flag Description
nat_sync NAT issues - NAT port allocation operations in Check Point cluster
nat64 NAT issues - 6in4 tunnels (IPv6 over IPv4) and 4in6 tunnels (IPv4 over IPv6)
netquota IPS protection "Network Quota"
ntup Non-TCP / Non-UDP traffic policy (traffic parser)
packet Actions performed on packets (like Accept, Drop, Fragment)
packval Stateless verifications (sequences, fragments, translations and other header

verifications)
portscan Prevention of port scanning
prof Connection profiler for Firewall Priority Queues (see sk105762)
q Driver queue (for example, cluster synchronization operations)

This debug flag is crucial for the debug of Check Point cluster synchronization issues
qos QoS (FloodGate-1)
rad Resource Advisor policy (for Application Control, URL Filtering, and others)
route Routing issues

This debug flag is crucial for the debug of ISP Redundancy issues
sam Suspicious Activity Monitoring
sctp Processing of Stream Control Transmission Protocol (SCTP) connections
scv SecureClient Verification
shmem Currently is not used
sip VoIP traffic - SIP and H.323

Note - In addition, see:
n "Module 'h323' (VoIP H.323)" on page 260
n "Module 'WS_SIP' (Web Intelligence VoIP SIP Parser)" on page 296
smtp Issues with e-mails over SMTP
sock Sockstress TCP DoS attack (CVE-2008-4609)
span Monitor mode (mirror / span port)
spii Stateful Protocol Inspection Infrastructure and INSPECT Streaming Infrastructure
synatk IPS protection 'SYN Attack' (SYNDefender)

Note - In addition, see "Module 'synatk' (Accelerated SYN Defender)" on
page 282.

Flag Description
sync Synchronization operations in Check Point cluster

Note - In addition, see the debug flag "sync" in "Module 'CPAS' (Check Point
Active Streaming)" on page 238.
tcpstr TCP streaming mechanism
te Prints the name of an interface for incoming connection from Threat Emulation
Machine
tlsparser Currently is not used
tp_container Operations in the Threat Prevention container
ua Processing of Universal Alcatel "UA" connections
ucd Processing of UserCheck connections in Check Point cluster
unibypass Universal Bypass on CoreXL Firewall Instances during load
user User Space communication with Kernel Space (most useful for configuration and
VSX debug)
utest Currently is not used
vm Virtual Machine chain decisions on traffic going through the fw_filter_chain
wap Processing of Wireless Application Protocol (WAP) connections
wire Wire-mode Virtual Machine chain module
xlate NAT issues - basic information
xltrc NAT issues - additional information - going through NAT rulebase
zeco Memory allocations in the Zero-Copy kernel module

Module 'gtp' (GPRS Tunneling Protocol)

Syntax
fw ctl debug -m gtp + {all | <List of Debug Flags>}
g_fw ctl debug -m gtp + {all | <List of Debug Flags>}
Flag Description
create GTPv0 / GTPv1 create PDP context
create2 GTPv2 create session
dbg GTP debug mechanism
delete GTPv0 / GTPv1 delete PDP context
delete2 GTPv2 delete session
error General GTP errors
ioctl GTP IOCTL commands
ld Operations with GTP kernel tables (addition, removal, modification of entries)
log GTPv0 / GTPv1 logging
log2 GTPv2 logging
modify GTPv2 modify bearer
other GTPv0 / GTPv1 other messages
other2 GTPv2 other messages
packet GTP main packet flow
parse GTPv0 / GTPv1 parsing
parse2 GTPv2 parsing
state GTPv0 / GTPv1 dispatching
state2 GTPv2 dispatching
sxl Processing of GTP connections in SecureXL

Flag Description
tpdu GTP T-PDU
update GTPv0 / GTPv1 update PDP context

Module 'h323' (VoIP H.323)
Module 'h323' (VoIP H.323)

Syntax
fw ctl debug -m h323 + {all | <List of Debug Flags>}
g_fw ctl debug -m h323 + {all | <List of Debug Flags>}
Flag Description
align General VoIP debug messages (for example, VoIP infrastructure)
cpas Debug messages about the CPAS TCP

Important - This debug flag is not included when you use the syntax "fw ctl debug
-m h323 all"
decode H.323 decoder messages
h225 H225 call signaling messages (SETUP, CONNECT, RELEASE COMPLETE, and so on)
h245 H245 control signaling messages (OPEN LOGICAL CHANNEL, END SESSION COMMAND,
and so on)
init Internal errors
ras H225 RAS messages (REGISTRATION, ADMISSION, and STATUS REQUEST /

RESPONSE)

Module 'ICAP_CLIENT' (Internet Content Adaptation Protocol Client)
Module 'ICAP_CLIENT' (Internet Content Adaptation

Protocol Client)
Syntax
fw ctl debug -m ICAP_CLIENT + {all | <List of Debug Flags>}
g_fw ctl debug -m ICAP_CLIENT + {all | <List of Debug Flags>}
Flag Description
blade Internal operations in the ICAP Client module
cpas Check Point Active Streaming (CPAS)
Note - Also see "Module 'CPAS' (Check Point Active Streaming)" on page 238.
daf_cmi Mirror and Decrypt of HTTPS traffic - operations related to the Context Management
Interface / Infrastructure Loader
Note - Also see "Module 'cmi_loader' (Context Management Interface /
Infrastructure Loader)" on page 236.
daf_module Mirror and Decrypt of HTTPS traffic - operations related to the ICAP Client module
daf_policy Mirror and Decrypt of HTTPS traffic - operations related to policy installation
daf_ Mirror and Decrypt of HTTPS traffic - operations related to rulebase

rulebase
daf_tcp Mirror and Decrypt of HTTPS traffic - internal processing of TCP connections
global Global operations in the ICAP Client module
icap Processing of ICAP connections
module Operations in the ICAP Client module (initialization, module loading, calls to the
module, and so on)

Module 'ICAP_CLIENT' (Internet Content Adaptation Protocol Client)
Flag Description
flag 'coverage')
trick Data Trickling mode

Module 'IDAPI' (Identity Awareness API)
Module 'IDAPI' (Identity Awareness API)

Syntax
fw ctl debug -m IDAPI + {all | <List of Debug Flags>}
g_fw ctl debug -m IDAPI + {all | <List of Debug Flags>}

>
Flag Description
async Checking for known networks
classifier Data classification
clob Classification Object (CLOB) observer (data classification)
data Portal, IP address matching for Terminal Servers Identity Agent, session handling
htab Checking for network IP address, working with kernel tables
log Various logs for internal operations
module Removal of the Identity Awareness API debug module's infrastructure, failure to
convert to Base64, failure to append Source to Destination, and so on
observer Data classification observer
test IP test, Identity Awareness API synchronization
flag 'coverage')

Module 'kiss' (Kernel Infrastructure)

Syntax
fw ctl debug -m kiss + {all | <List of Debug Flags>}
g_fw ctl debug -m kiss + {all | <List of Debug Flags>}
Note - In addition, see "Module 'kissflow' (Kernel Infrastructure Flow)" on page 267.
Flag Description
accel_pm Accelerated Pattern Matcher
bench CPU benchmark
connstats Statistics for connections
cookie Virtual de-fragmentation , cookie issues (cookies in the data structure that holds the
packets)
dbg_filter Information about the configured Debug Filters - "Kernel Debug Filters" on page 210
dfa Pattern Matcher (Deterministic Finite Automaton) compilation and execution
driver Loading / unloading of the FireWall driver
flofiler FLow prOFILER
ghtab Multi-threaded safe global hash tables
ghtab_bl Internal operations on global hash tables
handles Memory pool allocation for tables
htab Multi-threaded safe hash tables
htab_bl Internal operations on hash tables
htab_bl_err Errors and failures during internal operations on hash tables
htab_bl_exp Expiration in hash tables
htab_bl_ Errors and failures during internal operations on hash tables

infra

Flag Description
htab_bl_ Warnings during internal operations on hash tables

warn
ioctl IOCTL control messages (communication between the kernel and daemons)
kqstats Kernel Worker thread statistics (resetting, initializing, turning off)
kw Kernel Worker state and Pattern Matcher inspection
leak Memory leak detection mechanism
memprof Memory allocation operations in the Memory Profiler (when the kernel parameter fw_
conn_mem_prof_enabled=1)
misc CPU counters, Memory counters, getting/setting of global kernel parameters
mtctx Multi-threaded context - memory allocation, reference count
packet Internal parsing operations on packets
pcre Perl Compatible Regular Expressions (execution, memory allocation)
pm Pattern Matcher compilation and execution
pmdump Pattern Matcher DFA (dumping XMLs of DFAs)
pmint Pattern Matcher compilation
pools Memory pool allocation operations
queue Kernel Worker thread queues
rem Regular Expression Matcher - Pattern Matcher 2nd tier (slow path)
salloc System Memory allocation
shmem Shared Memory allocation
sm String Matcher - Pattern Matcher 1st tier (fast path)
stat Statistics for categories and maps
swblade Registration of Software Blades
thinnfa Currently is not used
thread Kernel thread that supplies low level APIs to the kernel thread
timers Internal timers

Flag Description
usrmem User Space platform memory usage
vbuf Virtual buffer
worker Kernel Worker - queuing and dequeuing

Module 'kissflow' (Kernel Infrastructure Flow)
Module 'kissflow' (Kernel Infrastructure Flow)

Syntax
fw ctl debug -m kissflow + {all | <List of Debug Flags>}
g_fw ctl debug -m kissflow + {all | <List of Debug Flags>}
Note - Also see "Module 'kiss' (Kernel Infrastructure)" on page 264.
Flag Description
compile Pattern Matcher (pattern compilation)
dfa Pattern Matcher (Deterministic Finite Automaton) compilation and execution
pm Pattern Matcher - general information

Module 'MALWARE' (Threat Prevention)
Module 'MALWARE' (Threat Prevention)

Syntax
fw ctl debug -m MALWARE + {all | <List of Debug Flags>}
g_fw ctl debug -m MALWARE + {all | <List of Debug Flags>}
Flag Description
av Currently is not used
global Prints parameters from the $FWDIR/conf/mail_security_config file
ioc Operations on Indicators of Compromise (IoC)
memory Currently is not used
module Removal of the MALWARE module's debug infrastructure
te Currently is not used
flag 'coverage')

Module 'multik' (Multi-Kernel Inspection - CoreXL)

Syntax
fw ctl debug -m multik + {all | <List of Debug Flags>}
g_fw ctl debug -m multik + {all | <List of Debug Flags>}
Notes:
n When you enable the debug flag 'multik' in the "Module 'fw' (Firewall)" on page 252, it
enables all the debug flags in this debug module, except for the debug flag 'packet'.
n In a cluster, enable the debug flag "multik" in the "Module 'cluster' (ClusterXL)" on
page 233.
n If you use the IPsec VPN Software Blade, enable the debug flag "multik" in the "Module
'VPN' (Site-to-Site VPN and Remote Access VPN)" on page 290.
n If you use the QoS Software Blade, enable the debug flag "multik" in the "Module 'fg'
(FloodGate-1 - QoS)" on page 248.
Flag Description
api Registration and unregistration of cross-instance function calls
cache_tab Cache table infrastructure
conn Creation and deletion of connections in the dispatcher table
counter Cross-instance counter infrastructure
event Cross-instance event aggregation infrastructure
fwstats Firewall statistics
ioctl Distribution of IOCTLs to different CoreXL Firewall instances
lock Obtaining and releasing the fw_lock on multiple CoreXL Firewall instances
message Cross-instance messages (used for local sync and port scanning)
packet For each packet, shows the CoreXL SND dispatching decision (CoreXL Firewall instance
and reason)
packet_ Invalid packets, for CoreXL SND could not make a dispatching decision
err
prio Firewall Priority Queues (refer to sk105762)

Flag Description
queue Packet queue
quota Cross-instance quota table (used by the Network Quota feature)
route Routing of packets
state Starting and stopping of CoreXL Firewall instances, establishment of relationship

between CoreXL Firewall instances
temp_ Temporary connections

conns
uid Cross-instance Unique IDs
vpn_ MultiCore VPN (see sk118097)

multik

Module 'MUX' (Multiplexer for Applications Traffic)

R80.20 introduced a new layer between the Streaming layer and the Applications layer - MUX (Multiplexer).
Applications are registered to the Streaming layer through the MUX layer.
The MUX layer chooses to work over PSL (passive streaming) or CPAS (active streaming).
Syntax
fw ctl debug -m MUX + {all | <List of Debug Flags>}
g_fw ctl debug -m MUX + {all | <List of Debug Flags>}
Flag Description
active CPAS (active streaming)

Note - Also see "Module 'CPAS' (Check Point Active Streaming)" on
page 238.
advp Advanced Patterns (signatures over port ranges)
api API calls
comm Information about opening and closing of connections
http_disp HTTP Dispatcher
misc Miscellaneous helpful information (not shown with other debug flags)
passive PSL (passive streaming)
Note - Also see "Module 'PSL' (Passive Streaming Library)" on page 275.
proxy_tp Proxy tunnel parser
stream General information about the data stream
test Currently is not used
tier1 Pattern Matcher 1st tier (fast path)
tls General information about the TLS
tlsp TLS parser
tol Test Object List algorithm (to determine whether an application is malicious or not)

Flag Description
udp UDP parser
ws Web Intelligence

Module 'NRB' (Next Rule Base)

Syntax
fw ctl debug -m NRB + {all | <List of Debug Flags>}
g_fw ctl debug -m NRB + {all | <List of Debug Flags>}
Flag Description
appi Rules and applications
Note - Also see "Module 'APPI' (Application Control Inspection)" on page 228.
dlp Data Loss Prevention

Note - Also see:
n "Module 'dlpda' (Data Loss Prevention - Download Agent for Content
Awareness)" on page 243
match Rule matching
module Operations in the NRB module (initialization, module loading, calls to the module,
contexts, and so on)
sec_rb Security rulebase
ssl_insp HTTPS Inspection

Flag Description
flag 'coverage')

Module 'PSL' (Passive Streaming Library)
Module 'PSL' (Passive Streaming Library)

Syntax
fw ctl debug -m PSL + {all | <List of Debug Flags>}
g_fw ctl debug -m PSL + {all | <List of Debug Flags>}
Note - Also see "Module 'MUX' (Multiplexer for Applications Traffic)" on page 271.
Flag Description
pkt Processing of packets
tcpstr Processing of TCP streams
seq Processing of TCP sequence numbers

Module 'RAD_KERNEL' (Resource Advisor - Kernel Space)
Module 'RAD_KERNEL' (Resource Advisor - Kernel Space)

Syntax
fw ctl debug -m RAD_KERNEL + {all | <List of Debug Flags>}
g_fw ctl debug -m RAD_KERNEL + {all | <List of Debug Flags>}
Flag Description
cache RAD kernel malware cache
global RAD global context
flag 'coverage')

Module 'RTM' (Real Time Monitoring)

Syntax
fw ctl debug -m RTM + {all | <List of Debug Flags>}
g_fw ctl debug -m RTM + {all | <List of Debug Flags>}
Flag Description
accel Prints SecureXL information about the accelerated packets, connections, and so on
chain Prints information about chain registration and about the E2E (Virtual Link) chain
function actions
Note - This important debug flag helps you know, whether the E2E identifies
the Virtual Link packets
con_conn Prints messages for each connection (when a new connection is handled by the
RTM module)
The same debug flags as 'per_conn'
err General errors
import Importing of the data from other kernel modules (FireWall, QoS)
init Initialization of the RTM module
ioctl IOCTL control messages
netmasks Information about how the RTM handles netmasks, if you are monitoring an object
of type Network
per_conn Prints messages for each connection (when a new connection is handled by the
RTM module)
The same debug flags as 'con_conn'
per_pckt Prints messages for each packet (when a new packet arrives)
Warning - Prints many messages, which increases the load on the CPU
performance Currently is not used
policy Prints messages about loading and unloading on the FireWall module (indicates
that the RTM module received the FireWall callback)
rtm Real time monitoring

Flag Description
s_err General errors about kernel tables and other failures
sort Sorting of "Top XXX" counters
special Information about how the E2E modifies the E2ECP protocol packets
tabs Currently is not used
topo Calculation of network topography
view_add Adding or deleting of a View
view_update Updating of Views with new information
view_update1 Updating of Views with new information
wd WebDefense views

Module 'seqvalid' (TCP Sequence Validator and Translator)
Module 'seqvalid' (TCP Sequence Validator and Translator)

Syntax
fw ctl debug -m seqvalid + {all | <List of Debug Flags>}
g_fw ctl debug -m seqvalid + {all | <List of Debug Flags>}
Flag Description
seqval TCP sequence validation and translation
sock Currently is not used

Module 'SFT' (Stream File Type)
Module 'SFT' (Stream File Type)

Syntax
fw ctl debug -m SFT + {all | <List of Debug Flags>}
g_fw ctl debug -m SFT + {all | <List of Debug Flags>}
Flag Description
fatal Fatal errors
mgr Rule match, database, connection processing, classification

Module 'SGEN' (Struct Generator)
Module 'SGEN' (Struct Generator)

Syntax
fw ctl debug -m SGEN + {all | <List of Debug Flags>}
g_fw ctl debug -m SGEN + {all | <List of Debug Flags>}
Flag Description
engine Struct Generator engine operations on objects
fatal Fatal errors
field Operations on fields
general General types macros
load Loading of macros
serialize Serialization while loading the macros

Module 'synatk' (Accelerated SYN Defender)
Module 'synatk' (Accelerated SYN Defender)

For additional information, see R81 Performance Tuning Administration Guide - Chapter SecureXL -
Section Accelerated SYN Defender.
Syntax
fw ctl debug -m synatk + {all | <List of Debug Flags>}
g_fw ctl debug -m synatk + {all | <List of Debug Flags>}
Flag Description
cookie TCP SYN Cookie
radix_dump Dump of the radix tree
radix_match Matched items in the radix tree
radix_modify Operations in the radix tree

Module 'TPUTILS' (Threat Prevention Utilities)
Module 'TPUTILS' (Threat Prevention Utilities)

Syntax
fw ctl debug -m TPUTILS + {all | <List of Debug Flags>}
g_fw ctl debug -m TPUTILS + {all | <List of Debug Flags>}
Flag Description
bloom Bloom filter operations
error General errors (the connection is probably rejected)
global Handling of global structure (usually, related to policy)
module Operations in the TPUTILS module (initialization, module loading, calls to the module,
policy loading, and so on)
flag 'coverage')
uuid Session UUID

Module 'UC' (UserCheck)
Module 'UC' (UserCheck)

Syntax
fw ctl debug -m UC + {all | <List of Debug Flags>}
g_fw ctl debug -m UC + {all | <List of Debug Flags>}
Flag Description
htab Hash table
module Operations in the UserCheck module (initialization, UserCheck table hits, finding User
ID in cache, removal of UserCheck debug module's infrastructure)
flag 'coverage')
webapi URL patterns, UserCheck incidents, connection redirection

Module 'UP' (Unified Policy)

Syntax
fw ctl debug -m UP + {all | <List of Debug Flags>}
g_fw ctl debug -m UP + {all | <List of Debug Flags>}

n "Module 'upconv' (Unified Policy Conversion)" on
page 287
n "Module 'UPIS' (Unified Policy Infrastructure)" on
page 288
Flag Description
account Currently is not used
btime Currently is not used
connection Information about connections, transactions
limit Unified Policy download and upload limits
log Some logging operations
mab Mobile Access handler
manager Unified Policy manager operations
match Classification Object (CLOB) observer (data classification)
module Operations in the Unified Policy module (initialization, module loading, calls to the
module, and so on)
policy Unified Policy internal operations

Flag Description
prob Currently is not used
prob_impl Implied matched rules
rulebase Unified Policy rulebase
sec_rb Secondary NRB rulebase operations
stats Statistics about connections, transactions
flag 'coverage')
urlf_ssl Currently is not used
vpn VPN classifier

Module 'upconv' (Unified Policy Conversion)
Module 'upconv' (Unified Policy Conversion)

Syntax
fw ctl debug -m upconv + {all | <List of Debug Flags>}
g_fw ctl debug -m upconv + {all | <List of Debug Flags>}

n "Module 'UPIS' (Unified Policy Infrastructure)" on
page 288
Flag Description
map UTF-8 and UTF-16 characters conversion
mem Prints how much memory is used for character sets
tree Lookup of characters
utf7 Conversion of UTF-7 characters to a Unicode characters
utf8 Conversion of UTF-8 characters to a Unicode characters

Module 'UPIS' (Unified Policy Infrastructure)

Syntax
fw ctl debug -m UPIS + {all | <List of Debug Flags>}
g_fw ctl debug -m UPIS + {all | <List of Debug Flags>}

n "Module 'upconv' (Unified Policy Conversion)" on
page 287
Flag Description
cpdiag CPDiag operations
crumbs Currently is not used
db SQLite Database operations
dnd Processing of Dynamic & Domain objects
fwapp Information about policy installation for the FireWall application
initialapp Information about the Initial Install Policy App
mgr Policy installation manager
module Operations in the Unified Policy Infrastructure module (initialization, module loading,
calls to the module, and so on)
mutex Unified Policy internal mutex operations
policy Unified Policy Infrastructure internal operations

Flag Description
report Various reports about Unified Policy installations
sna Operations on SnA objects ("Services and Application")
tables Operations on kernel tables
flag 'coverage')
topo Information about topology and Anti-Spoofing of interfaces; about Address Range
objects
upapp Information about policy installation for Unified Policy application
update Information about policy installation for CMI Update application
vpn VPN classifier

Module 'VPN' (Site-to-Site VPN and Remote Access VPN)

Syntax
fw ctl debug -m VPN + {all | <List of Debug Flags>}
g_fw ctl debug -m VPN + {all | <List of Debug Flags>}
Flag Description
cluster Events related to cluster
comp Compression for encrypted connections
counters Various status counters (typically for real-time Monitoring)
cphwd Traffic acceleration issues (in hardware)
err Errors that should not happen, or errors that critical to the working of the VPN module
gtp Processing of GPRS Tunneling Protocol (GTP) connections
Note - Also see "Module 'gtp' (GPRS Tunneling Protocol)" on page 258
ifnotify Notifications about the changes in interface status - up or down (as received from OS)
ike Enables all IKE kernel debug in respect to moving the IKE to the interface, where it will
eventually leave and the modification of the source IP of the IKE packet, depending on
the configuration
init Initializes the VPN kernel and kernel data structures, when kernel is up, or when policy
is installed (it will also print the values of the flags that are set using the CPSET upon
policy reload)
l2tp Processing of L2TP connections
lsv Large Scale VPN (LSV)
mem Allocation of VPN pools and VPN contexts
mspi Information related to creation and destruction of MSA / MSPI
multicast VPN multicast

Flag Description
multik Information related to interaction between VPN and CoreXL

Notes:
n If you use the QoS Software Blade, enable the debug flag "multik" in the
"Module 'fg' (FloodGate-1 - QoS)" on page 248.
nat NAT issues , cluster IP manipulation (Cluster Virtual IP address <=> Member IP
address)
om_alloc Allocation of Office Mode IP addresses
osu Cluster Optimal Service Upgrade (see sk107042)
packet Events that can happen for every packet, unless covered by more specific debug flags
pcktdmp Prints the encrypted packets before the encryption

Prints the decrypted packets after the decryption
policy Events that can happen only for a special packet in a connection, usually related to
policy decisions or logs / traps
queue Handling of Security Association (SA) queues
rdp Processing of Check Point RDP connections
ref Reference counting for MSA / MSPI, when storing or deleting Security Associations
(SAs)
resolver VPN Link Selection table and Certificate Revocation List (CRL), which is also part of
the peer resolving mechanism
rsl Operations on Range Skip List
sas Information about keys and Security Associations (SAs)
sr SecureClient / SecureRemote related issues
tagging Sets the VPN policy of a connection according to VPN communities, VPN Policy
related information
tcpt Information related to TCP Tunnel (Visitor mode - FireWall traversal on TCP port 443)
tnlmon VPN tunnel monitoring
topology VPN Link Selection
vin Does not apply anymore

Only on Security Gateway that runs on Windows OS:
Information related to IPSec NIC interaction

Flag Description
warn General warnings
xl Does not apply anymore

Interaction with Accelerator Cards (AC II / III / IV)

Module 'WS' (Web Intelligence)

Syntax
fw ctl debug -m WS + {all | <List of Debug Flags>}
g_fw ctl debug -m WS + {all | <List of Debug Flags>}
Notes:
n In addition, see "Module 'WSIS' (Web Intelligence Infrastructure)" on page 298.
n To print information for all Virtual Systems in the debug output, before you start the kernel
debug, set this kernel parameter on the VSX Gateway or each VSX Cluster Member (this is
the default behavior):
# fw ctl set int ws_debug_vs 0
n To print information for a specific Virtual System in the debug output, before you start the
kernel debug, set this kernel parameter on the VSX Gateway or each VSX Cluster Member:
# fw ctl set int ws_debug_vs <VSID>
n To print information for all IPv4 addresses in the debug output, before you start the kernel
debug, set this kernel parameter on the VSX Gateway or each VSX Cluster Member (this is
the default behavior):
# fw ctl set int ws_debug_ip 0
n To print information for a specific IPv4 address in the debug output, before you start the
kernel debug, set this kernel parameter on the VSX Gateway or each VSX Cluster Member:
# fw ctl set int ws_debug_ip <XXX.XXX.XXX.XXX>
Flag Description
body HTTP body (content) layer
connection Connection layer
cookie HTTP cookie header
crumb Currently is not used
error General errors (the connection is probably rejected)
event Events
fatal Fatal errors

Flag Description
flow Currently is not used
hpack Processing of HTTP/2 HPACK header compression
http2 Processing of HTTP/2 packets
ioctl IOCTL control messages (communication between the kernel and daemons, loading
and unloading of the FireWall)
mem_pool Memory pool allocation operations
module Operations in the Web Intelligence module (initialization, module loading, calls to the
parser HTTP header parser layer
parser_err HTTP header parsing errors
pfinder Pattern finder
pkt_dump Packet dump
policy Policy (installation and enforcement)
report_mgr Report manager (errors and logs)
spii Stateful Protocol Inspection Infrastructure (INSPECT streaming)
sslt SSL Tunneling (SSLT)
stat Memory usage statistics
stream Stream virtualization
flag 'coverage')
uuid Session UUID

Flag Description

Module 'WS_SIP' (Web Intelligence VoIP SIP Parser)

Syntax
fw ctl debug -m WS_SIP + {all | <List of Debug Flags>}
g_fw ctl debug -m WS_SIP + {all | <List of Debug Flags>}
Flag Description
body HTTP body (content) layer
connection Connection layer
cookie HTTP cookie header
crumb Currently is not used
event Events
fatal Fatal errors
hpack Processing of HTTP/2 HPACK header compression
http2 Processing of HTTP/2 packets
ioctl IOCTL control messages (communication between the kernel and daemons, loading
and unloading of the FireWall)
mem_pool Memory pool allocation operations
module Operations in the Web Intelligence VoIP SIP Parser module (initialization, module
loading, calls to the module, policy loading, and so on)

Flag Description
parser_err HTTP header parsing errors
pfinder Pattern finder
pkt_dump Packet dump
policy Policy (installation and enforcement)
report_mgr Report manager (errors and logs)
spii Stateful Protocol Inspection Infrastructure (INSPECT streaming)
sslt SSL Tunneling (SSLT)
stat Memory usage statistics
stream Stream virtualization
flag 'coverage')
uuid Session UUID

Module 'WSIS' (Web Intelligence Infrastructure)
Module 'WSIS' (Web Intelligence Infrastructure)

Syntax
fw ctl debug -m WSIS + {all | <List of Debug Flags>}
g_fw ctl debug -m WSIS + {all | <List of Debug Flags>}
Note - In addition, see "Module 'WS' (Web Intelligence)" on page 293.
Flag Description
cipher Currently is not used
common Prints a message, when parameters are invalid
crumb Information about connections
datastruct Data structure tree
decoder Decoder for the content transfer encoding (UUEncode, UTF-8, HTML encoding &#)
dump Packet dump
flag 'coverage')

Glossary
Glossary
A
Anti-Bot
Check Point Software Blade on a Security Gateway that blocks botnet behavior and
communication to Command and Control (C&C) centers. Acronyms: AB, ABOT.
Anti-Spam
Check Point Software Blade on a Security Gateway that provides comprehensive
protection for email inspection. Synonym: Anti-Spam & Email Security. Acronyms: AS,
ASPAM.
Anti-Virus
Check Point Software Blade on a Security Gateway that uses real-time virus signatures
and anomaly-based protections from ThreatCloud to detect and block malware at the
Security Gateway before users are affected. Acronym: AV.
Application Control
Check Point Software Blade on a Security Gateway that allows granular control over
specific web-enabled applications by using deep packet inspection. Acronym: APPI.
Audit Log
Log that contains administrator actions on a Management Server (login and logout,
creation or modification of an object, installation of a policy, and so on).
Bridge Mode
Security Gateway or Virtual System that works as a Layer 2 bridge device for easy
deployment in an existing topology.
Cluster
Two or more Security Gateways that work together in a redundant configuration - High
Availability, or Load Sharing.

Glossary
Cluster Member
Security Gateway that is part of a cluster.
Compliance
Check Point Software Blade on a Management Server to view and apply the Security
Best Practices to the managed Security Gateways. This Software Blade includes a
library of Check Point-defined Security Best Practices to use as a baseline for good
Security Gateway and Policy configuration.
Content Awareness
Check Point Software Blade on a Security Gateway that provides data visibility and
enforcement. See sk119715. Acronym: CTNT.
CoreXL
Performance-enhancing technology for Security Gateways on multi-core processing
platforms. Multiple Check Point Firewall instances are running in parallel on multiple
CPU cores.
CoreXL Firewall Instance

On a Security Gateway with CoreXL enabled, the Firewall kernel is copied multiple
times. Each replicated copy, or firewall instance, runs on one processing CPU core.
These firewall instances handle traffic at the same time, and each firewall instance is a
complete and independent firewall inspection kernel. Synonym: CoreXL FW Instance.
CoreXL SND
Secure Network Distributer. Part of CoreXL that is responsible for: Processing incoming
traffic from the network interfaces; Securely accelerating authorized packets (if
SecureXL is enabled); Distributing non-accelerated packets between Firewall kernel
instances (SND maintains global dispatching table, which maps connections that were
assigned to CoreXL Firewall instances). Traffic distribution between CoreXL Firewall
instances is statically based on Source IP addresses, Destination IP addresses, and the
IP 'Protocol' type. The CoreXL SND does not really "touch" packets. The decision to stick
to a particular FWK daemon is done at the first packet of connection on a very high level,
before anything else. Depending on the SecureXL settings, and in most of the cases, the
SecureXL can be offloading decryption calculations. However, in some other cases,
such as with Route-Based VPN, it is done by FWK daemon.
CPUSE
Check Point Upgrade Service Engine for Gaia Operating System. With CPUSE, you can
automatically update Check Point products for the Gaia OS, and the Gaia OS itself. For
details, see sk92449.

Glossary
DAIP Gateway
Dynamically Assigned IP (DAIP) Security Gateway is a Security Gateway, on which the
IP address of the external interface is assigned dynamically by the ISP.
Data Loss Prevention

Check Point Software Blade on a Security Gateway that detects and prevents the
unauthorized transmission of confidential information outside the organization. Acronym:
DLP.
Data Type
Classification of data in a Check Point Security Policy for the Content Awareness
Software Blade.
Distributed Deployment
Configuration in which the Check Point Security Gateway and the Security Management
Server products are installed on different computers.
Dynamic Object
Special object type, whose IP address is not known in advance. The Security Gateway
resolves the IP address of this object in real time.
Endpoint Policy Management

Check Point Software Blade on a Management Server to manage an on-premises
Harmony Endpoint Security environment.
Expert Mode
The name of the elevated command line shell that gives full system root permissions in
the Check Point Gaia operating system.
Gaia
Check Point security operating system that combines the strengths of both
SecurePlatform and IPSO operating systems.

Glossary
Gaia Clish
The name of the default command line shell in Check Point Gaia operating system. This
is a restricted shell (role-based administration controls the number of commands
available in the shell).
Gaia Portal
Web interface for the Check Point Gaia operating system.
Hotfix
Software package installed on top of the current software version to fix a wrong or
undesired behavior, and to add a new behavior.
HTTPS Inspection
Feature on a Security Gateway that inspects traffic encrypted by the Secure Sockets
Layer (SSL) protocol for malware or suspicious patterns. Synonym: SSL Inspection.
Acronyms: HTTPSI, HTTPSi.
ICA
Internal Certificate Authority. A component on Check Point Management Server that
issues certificates for authentication.
Identity Awareness
Check Point Software Blade on a Security Gateway that enforces network access and
audits data based on network location, the identity of the user, and the identity of the
computer. Acronym: IDA.
Identity Logging
Check Point Software Blade on a Management Server to view Identity Logs from the
managed Security Gateways with enabled Identity Awareness Software Blade.
Internal Network
Computers and resources protected by the Firewall and accessed by authenticated
users.

Glossary
IPS
Check Point Software Blade on a Security Gateway that inspects and analyzes packets
and data for numerous types of risks (Intrusion Prevention System).
IPsec VPN
Check Point Software Blade on a Security Gateway that provides a Site to Site VPN and
Remote Access VPN access.
Jumbo Hotfix Accumulator

Collection of hotfixes combined into a single package. Acronyms: JHA, JHF, JHFA.
Kerberos
An authentication server for Microsoft Windows Active Directory Federation Services
(ADFS).
Log Server
Dedicated Check Point server that runs Check Point software to store and process logs.
Logging & Status

Check Point Software Blade on a Management Server to view Security Logs from the
managed Security Gateways.
Management Interface
(1) Interface on a Gaia Security Gateway or Cluster member, through which
Management Server connects to the Security Gateway or Cluster member. (2) Interface
on Gaia computer, through which users connect to Gaia Portal or CLI.
Management Server
Check Point Single-Domain Security Management Server or a Multi-Domain Security
Management Server.

Glossary
Manual NAT Rules

Manual configuration of NAT rules by the administrator of the Check Point Management
Server.
Mobile Access
Check Point Software Blade on a Security Gateway that provides a Remote Access VPN
access for managed and unmanaged clients. Acronym: MAB.
Multi-Domain Log Server

Dedicated Check Point server that runs Check Point software to store and process logs
in a Multi-Domain Security Management environment. The Multi-Domain Log Server
consists of Domain Log Servers that store and process logs from Security Gateways that
are managed by the corresponding Domain Management Servers. Acronym: MDLS.
Multi-Domain Server
Dedicated Check Point server that runs Check Point software to host virtual Security
Management Servers called Domain Management Servers. Synonym: Multi-Domain
Security Management Server. Acronym: MDS.
Network Object
Logical object that represents different parts of corporate topology - computers, IP
addresses, traffic protocols, and so on. Administrators use these objects in Security
Policies.
Network Policy Management

Check Point Software Blade on a Management Server to manage an on-premises
environment with an Access Control and Threat Prevention policies.
Open Server
Physical computer manufactured and distributed by a company, other than Check Point.

Glossary
Provisioning
Check Point Software Blade on a Management Server that manages large-scale
deployments of Check Point Security Gateways using configuration profiles. Synonyms:
SmartProvisioning, SmartLSM, Large-Scale Management, LSM.
QoS
Check Point Software Blade on a Security Gateway that provides policy-based traffic
bandwidth management to prioritize business-critical traffic and guarantee bandwidth
and control latency.
Rule
Set of traffic parameters and other conditions in a Rule Base (Security Policy) that cause
specified actions to be taken for a communication session.
Rule Base
All rules configured in a given Security Policy. Synonym: Rulebase.
SecureXL
Check Point product on a Security Gateway that accelerates IPv4 and IPv6 traffic that
passes through a Security Gateway.
Security Gateway
Dedicated Check Point server that runs Check Point software to inspect traffic and
enforce Security Policies for connected network resources.
Security Management Server

Dedicated Check Point server that runs Check Point software to manage the objects and
policies in a Check Point environment within a single management Domain. Synonym:
Single-Domain Security Management Server.

Glossary
Security Policy
Collection of rules that control network traffic and enforce organization guidelines for
data protection and access to resources with packet inspection.
SIC
Secure Internal Communication. The Check Point proprietary mechanism with which
Check Point computers that run Check Point software authenticate each other over SSL,
for secure communication. This authentication is based on the certificates issued by the
ICA on a Check Point Management Server.
SmartConsole
Check Point GUI application used to manage a Check Point environment - configure
Security Policies, configure devices, monitor products and events, install updates, and
so on.
SmartDashboard
Legacy Check Point GUI client used to create and manage the security settings in
versions R77.30 and lower. In versions R80.X and higher is still used to configure
specific legacy settings.
SmartProvisioning
Check Point Software Blade on a Management Server (the actual name is
"Provisioning") that manages large-scale deployments of Check Point Security
Gateways using configuration profiles. Synonyms: Large-Scale Management,
SmartLSM, LSM.
SmartUpdate
Legacy Check Point GUI client used to manage licenses and contracts in a Check Point
environment.
Software Blade
Specific security solution (module): (1) On a Security Gateway, each Software Blade
inspects specific characteristics of the traffic (2) On a Management Server, each
Software Blade enables different management capabilities.
Standalone
Configuration in which the Security Gateway and the Security Management Server
products are installed and configured on the same server.

Glossary
Threat Emulation
Check Point Software Blade on a Security Gateway that monitors the behavior of files in
a sandbox to determine whether or not they are malicious. Acronym: TE.
Threat Extraction
Check Point Software Blade on a Security Gateway that removes malicious content from
files. Acronym: TEX.
Updatable Object
Network object that represents an external service, such as Microsoft 365, AWS, Geo
locations, and more.
URL Filtering
Check Point Software Blade on a Security Gateway that allows granular control over
which web sites can be accessed by a given group of users, computers or networks.
Acronym: URLF.
User Directory
Check Point Software Blade on a Management Server that integrates LDAP and other
external user management servers with Check Point products and security solutions.
VSX
Virtual System Extension. Check Point virtual networking solution, hosted on a computer
or cluster with virtual abstractions of Check Point Security Gateways and other network
devices. These Virtual Devices provide the same functionality as their physical
counterparts.
VSX Gateway
Physical server that hosts VSX virtual networks, including all Virtual Devices that provide
the functionality of physical network devices. It holds at least one Virtual System, which
is called VS0.

Glossary
Zero Phishing
Check Point Software Blade on a Security Gateway (R81.20 and higher) that provides
real-time phishing prevention based on URLs. Acronym: ZPH.

CP R81 Quantum SecurityGateway AdminGuide

Uploaded by

Copyright:

Available Formats

CP R81 Quantum SecurityGateway AdminGuide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CP R81 Quantum SecurityGateway AdminGuide

Uploaded by

Copyright:

Available Formats

27 October 2023

RESTRICTED RIGHTS LEGEND:

Check Point R81

Latest Version of this Document in English

Quantum Security Gateway R81 Administration Guide | 3

13 October First release of this document

Quantum Security Gateway R81 Administration Guide | 4

Quantum Security Gateway R81 Administration Guide | 5

Quantum Security Gateway R81 Administration Guide | 6

Configuring Mirror and Decrypt in SmartConsole for Gateway Mode 123

Quantum Security Gateway R81 Administration Guide | 7

Kernel Debug Syntax 203

Quantum Security Gateway R81 Administration Guide | 8

Module 'RAD_KERNEL' (Resource Advisor - Kernel Space) 276

Quantum Security Gateway R81 Administration Guide | 9

Check Point Quantum Security

2 Security Management Server

3 Internet and external networks

4 Security Gateway (or Cluster)

These are the primary components of a Check Point Firewall solution:

Quantum Security Gateway R81 Administration Guide | 10

Access Control Policy 11

Access Control Policy

Access Control Policy consists of these parts:

Quantum Security Gateway R81 Administration Guide | 11

n Access Control Rule Base

How to get there:

Quantum Security Gateway R81 Administration Guide | 12

n NAT Rule Base

How to get there:

Origin Origin Translat Translat

Automatic Generated Rules

NAT Rules for X (Y-Z)

# Specific Specific Specific or = Original = Original = Original Policy Your

Quantum Security Gateway R81 Administration Guide | 13

n Desktop Rule Base

For more information, see the SmartDashboard Help (press F1).

The Desktop Policy consists of two Rule Bases:

How to get there:

No Source Desktop Service Action Track Comment

# Any All Users@Any Any Accept None Your Comment

Quantum Security Gateway R81 Administration Guide | 14

Threat Prevention Policy

How to get there:

Quantum Security Gateway R81 Administration Guide | 15

HTTPS Inspection Policy

How to get there:

Quantum Security Gateway R81 Administration Guide | 16

Data Loss Prevention Policy

How to get there:

D Desti Exce Tr Ins Ti

Quantum Security Gateway R81 Administration Guide | 17

How to get there:

Country Direction Action Track Comments

Quantum Security Gateway R81 Administration Guide | 18

Mobile Access Policy

How to get there:

No Users Applications Install On Comment

# All Users Any Any Your Comment

Quantum Security Gateway R81 Administration Guide | 19