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:

  1. The Endpoint Security client checks for the latest signatures from a randomly selected super node listed in the Client Settings > General policy.

  2. If the update fails with the chosen super node, the Endpoint Security client attempts the update with another super node in the list.

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

  1. Go to Policy > Client Settings.

  2. From the toolbar, click Manage Super Nodes.

    The Manage Super Nodes page is displayed.

  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. After selecting the devices, click Save.

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

  5. Go to Client Settings and 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.