Authenticated Proxy

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

  1. Go to Policy > Client Settings > General > Authenticated Proxy.

  2. Enter:

    • Proxy - Proxy server address in the format address:host. For example,

    • Username - User name for the proxy server.

    • Password - Password for the proxy server.

  3. 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:

  1. Go to Policy > Client Settings > General > Sharing Data with Check Point.

  2. 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.

  3. 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 ServerClosed 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:

  1. 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.

  2. Click Save.



What is a Super Node?

A Super Node is a machine running a specially configured Endpoint Security Client that also consists of server-like and proxy-like capabilities, and which listens on port 4434 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.

Note - Super Node is not suitable for offline environments. Endpoint Security clients must be online and connected to the Harmony Endpoint Management server.

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.

Note - Super-Node is available in both Domain and Workgroup environments.

To configure a Super Node:

For Management Servers supporting Manage Super Nodes capability:

  1. Go to Policy > Client Settings.

  2. From the toolbar, click Manage Super Nodes.

  3. 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.

  4. When required devices are added, click Save, as promoting a machine to a Super Node does not require policy installation. To revert all changes, click Discard.

  5. Go to Client Settingsand select the required ruleClosed 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.

  6. Click + and add Super Nodes with all its specific devices to the relevant Client Settings rule.

  7. 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.

Supported Features

Starting in version E86.10, Super Node supports Anti-MalwareClosed A component on Endpoint Security Windows clients. This component protects clients from known and unknown viruses, worms, Trojan horses, adware, and keystroke loggers., Behavioral-Guard & Static Analysis signature updates. Additionally, software upgrades for Dynamic (EXE) and Windows installer (MSI) packages, client policies and policy changes are all relayed through Super Node.


  • Proxy configuration is not supported.

  • 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 an addition of approximately 350 MB to operate properly.

Disable Capabilities allows users to turn on or turn off capabilities, such as Threat Prevention, ComplianceClosed 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.

To allow users to disable capabilities:

  1. Go to Policy > Client Settings > General > Disable Capabilities.

  2. Select the capabilities that can be disabled by the user on the client.

  3. To enable the disabled capabilities automatically after a set interval of time:

    Note - This is supported only on Windows with Endpoint Security client version E88.30 and higher.

    1. Select the Set timeout checkbox.

    2. In the timeout field, enter the time in minutes.

  4. To allow users to disable the capabilities only after entering a password, select the Protect by password checkbox.

    Note - This is supported only on Windows with Endpoint Security client version E88.30 and higher.

    1. Click Manage Disable Capabilities Protect Password.

      Note - Optionally, from the taskbar, click Manage and select the Manage Disable Capabilities Protect Password from the list.

    2. In the Password field, enter a password and re-enter the password in the Confirm Password field.

      Note - Make sure the password is at least eight characters long, without spaces, and includes:

      • An uppercase letter

      • A lower case letter

      • A number.

    3. Click OK.

  5. Click Save & Install.

Network Protection

You can let users disable network protection on their computers.

Network Protection includes these components:

To configure network protection alerts:

  1. Go to the Policy > Client Settings > General > Network Protection.

  2. You may select Allow users to disable network protection on their computers - To disable network protection.

  3. 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.

  4. 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:

  1. Go to the Policy > Client Settings > General > Push Operation.

  2. Set the Minimum interval between status updates of Push Operations.

  3. Click Save.