Views:

After successfully setting up the Suspicious Object Hub and registering the Suspicious Object Node Apex Central servers, note the following configuration information.

Note:

After unregistering a Node Apex Central server, all previously synchronized objects remain in the Node Apex Central server suspicious object lists.

Configuration

Hub Apex Central

Node Apex Central

Synchronization interval

N/A

5 minutes (default)

Suspicious Object list synchronization

From the Hub Apex Central to Nodes:

  • Virtual Analyzer list

  • User-Defined list

From a Node Apex Central to the Hub:

  • Virtual Analyzer list
Note:

  • The Hub Apex Central server does not send data from the Notes column of the User-Defined list or the Exception list to the Node Apex Central servers.

  • When synchronizing lists, the User-Defined list has a higher priority than the Virtual Analyzer list.

    • If an object is added to both the User-Defined list and the Virtual Analyzer list on the Hub Apex Central before the next synchronization, the Hub Apex Central server deploys both lists to the Node Apex Central servers.

    • If an object in the Node Apex Central Virtual Analyzer list also exists in the Hub Apex Central User-Defined list, the suspicious object risk level changes to "High" on the Node Apex Central Virtual Analyzer list during the next synchronization.

  • Migrating to Apex Central from Control Manager 7.0 preserves:

    • The Suspicious Object Hub and Node architecture from the migrated Control Manager 7.0 installation

    • The Exception list synchronization settings from the migrated Control Manager 7.0 installation

Configuring Suspicious Object settings

Recommended

Configuring Suspicious Objects through the Hub Apex Central ensures consistency across the registered Node Apex Central servers.

Not available
Parent topic: Suspicious Object Hub and Node Architecture