General

Authenticated Proxy

If you have a proxy server to authenticate access to a resource:

Go to Policy > Client Settings > General > Authenticated Proxy.
Enter:
- Proxy - Proxy server address in the format address:host. For example, 192.168.79.157:3128
- Username - User name for the proxy server.
- Password - Password for the proxy server.
Click Save.

Sharing Data with Check Point

Clients can share information about detected infections and bots with Check Point.

The information goes to ThreatCloud, a Check Point database of security intelligence that is dynamically updated using a worldwide network of threat sensors.

ThreatCloud helps to keep Check Point protection up-to-date with real-time information.

Note - Check Point does not share any private information with third parties.

To share the data with Check Point ThreatCloud:

Go to Policy > Client Settings > General > Sharing Data with Check Point.
Enable anonymized telemetry - Select to enable sharing information with Check Point.

Select or clear any of these options:
- Anonymized forensics reports - Forensics reports include a lot of private identifiable information. This option lets customers anonymize this information.
- Files related to detection - Select to allow Check Point learn more about the attacks through metadata.
- Memory dumps related to detections - Select to allow sharing memory dumps from the RAM with Check Point.
Click Save.

Connection Awareness

Connection Awareness - Connection awareness controls how an endpoint enforces its Connected or Disconnected policy. By default, the client checks connectivity to the Endpoint Management Server Check Point Single-Domain Security Management Server or a Multi-Domain Security Management Server. to determine its connectivity state. Alternatively, the administrator can configure the client's connection status by checking its connectivity to a different network component, for example, a web server or a router, through ICMP packets or HTTP/HTTPS/IPv4 requests. If the client can connect to the network component, then its connection status is Connected. Otherwise, its connection status is Disconnected.

To configure the connection awareness setting:

Go to the Policy > Client Settings > General > Connection Awareness.

The Connection Awareness feature allows the administrator to choose between two options:
1. Connected to management - The client's status is Connected if it is connected to the Endpoint Security Management Servers. This is the default mode.
2. Connected to a list of specified targets - The client's status is Connected if it is connected to the specified target (network component) regardless of its connection to the Endpoint Security Management Servers.
  
  If you do not specify a disconnected policy for these addresses, the user is automatically considered connected.
Click Save.

Notes:

The client triggers HTTP GET requests to the server for connected or disconnected status in intervals of 30 seconds.
Connection Awareness is supported with Endpoint Security Client version E85.30 and higher for windows and E87.30 and higher for macOS.
Some capabilities, such as Full Disk Encryption A component on Endpoint Security Windows clients. This component combines Pre-boot protection, boot authentication, and strong encryption to make sure that only authorized users are given access to information stored on desktops and laptops. Acronym: FDE. (FDE) remain active even if the client's status is disconnected. However, it cannot perform operations that require connection to the server, such as acquire users from the server or send recovery data to the server.

Super-Node

What is a Super Node?

A Super Node is a Windows device running a specially configured Endpoint Security Client that also consists of server-like and proxy-like capabilities, and which listens on port 4434 and port 3128 to proxy by default. Super Node is a light-weight proxy (based on NGNIX) that allows admins to reduce their bandwidth consumption and enable offline updates, where only the Super Node needs connectivity to the update servers.

Super Node Workflow

When a device is assigned as a super node and has the supported blades installed, it downloads signatures from the sources defined in the policy and stores a local copy. This local copy serves as the signature source for other Endpoint Security Clients.

When an Endpoint Security Client initiates an update, it follows this process:

The Endpoint Security client checks for the latest signatures from a randomly selected super node listed in the Client Settings > General policy.
If the update fails with the chosen super node, the Endpoint Security client attempts the update with another super node in the list.
If the update fails with all the super nodes listed in the General Client Settings policy, the Endpoint Security client will update directly from the sources specified in the policy.

Primary Advantages:

Reduces site bandwidth usage.
Reduces server workload.
Reduces customer expense on server equipment, as there is no need for a local appliance.
Improved scale.

Notes -

Super Node is available in both Domain and Work group environments.
If the Endpoint Security client configured as a super node is of a lower version than its connection clients, the super node will return a 404 error response when a connection client tries to download the policy signatures. In this case the connection client downloads the signatures from the fallback location.

Supported Features

Endpoint Security Client Version

Features Supported

E85.30 and higher

Downloading the software upgrades for Windows installer (MSI) packages from the super nodes.

Super node tries to cache the requested files in the local folder.

Note - The files are cached based on the available free space in the super node device and the cache size configured.

E85.40 and higher

Downloading the software upgrades for Dynamic (EXE) packages from super nodes.
Downloading Behavioral-Guard & Static Analysis signature updates from super nodes.

E86.10 and higher

Downloading client policies and policy changes from super nodes.

E87.00 and higher

Harmony Endpoint Security Client

Application installed on end-user computers to monitor security status and enforce security policies. for macOS can be configured to create a local mirror of the Anti-Malware

A component of the Endpoint Security client that protects against known and unknown viruses, worms, Trojan horses, adware, and keystroke loggers. signatures which can be used as a signature source for other Endpoint Security clients for macOS.

E88.70 and higher

Super node proxies are supported for offline environment.

Limitations

By default, the cache max size is 4 GB and will automatically purge files after 7 days of inactivity. Files stored for a longer time without access are removed from cache.
Super Node requires approximately 350 MB of additional space to operate properly.

To configure a Super Node:

For Management Servers supporting Manage Super Nodes capability:

Go to Policy > Client Settings.
From the toolbar, click Manage Super Nodes.

The Manage Super Nodes page is displayed.
Click + and select the devices you want to define as Super Nodes and then click Add.

Note - You can also use the search bar to search for a device or devices that you want to define as Super Nodes.

Widgets are created for each entities selected as super nodes.

After selecting the devices, click Save.

Note - Configuring a device as a Super Node does not require policy installation.

Go to Client Settings and select the required 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.. In the Capabilities & Exclusions pane, click General and scroll-down to Super Nodes section.
Click + and add Super Nodes with all its specific devices to the relevant Client Settings rule.
Click Save and install the rule.

Note - Super Node settings are rule dependent. It means that Super Nodes defined in the General tab will be applied only to devices which are related to a specific rule.

Disable Capabilities

Disable Capabilities allows users to turn on or turn off capabilities, such as Threat Prevention, 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., and so on in the Endpoint Security client.

Notes:

This feature is supported with the Endpoint Security client version E86.40 and higher.
If the Endpoint Security Client device is restarted, the option to enable or disable the capabilities will only be available after five minutes.
For a Department of Homeland Security (DHS) compliant client (E2), the 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. and Anti-Malware, Anti-Exploit, 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. and URL filtering, and Anti-Ransomware, Behavioral Guard and Forensics A SandBlast Agent component on Endpoint Security Windows clients. This component: (1) Prevents ransomware attacks (2) Monitors files and the registry for suspicious processes and network activity. Analyzes incidents reported by other components. capabilities can only be turned on or off only together. These capabilities cannot be turned on or off separately.
For a non-DHS compliant client (E1), the Threat Emulation and Anti-Exploit, Anti-Bot and URL filtering, and Anti-Ransomware, Behavioral Guard and Forensics capabilities can only be turned on or off together. These capabilities cannot be turned on or off separately.

To allow users to disable capabilities:

Go to Policy > Client Settings > General > Disable Capabilities.
Toggle Allow users to disable capabilities to On.
Click Save.

Network Protection

You can let users disable network protection on their computers.

Network Protection includes these components:

To configure network protection alerts:

Go to the Policy > Client Settings > General > Network Protection.
You may select Allow users to disable network protection on their computers - To disable network protection.
In the Network Protection section, select or clear these options for each Firewall and Application Control:
- Allow Log - To generate logs for events.
- Allow Alert - To generate alerts for events. You must also select this to use Alert in the Track column of Firewall rules.
Click Save.

Push Operations

Push Operations are operations that the server pushes directly to client computers with no policy installation required. You can set the minimum time interval between status updates of Push Operations.

For more information, see Performing Push Operations.

To set the minimum time interval between status updates of Push Operations:

Go to the Policy > Client Settings > General > Push Operation.
Set the Minimum interval between status updates of Push Operations.
Click Save.