The scenario for deployment and installation of application components is determined by the planned load on the application servers.
The Endpoint Agent component can be installed on any computers that belong to the organization's IT infrastructure and run the Windows operating system. Outbound connections from computers with the Endpoint Agent component to the server hosting the Central Node component must be allowed directly, without a proxy server.
You can install one or multiple Central Node components. If you install multiple Central Node components, you can use them independently of each other or combine them for centralized management in distributed solution mode.
The deployment scenario selection depends on the utilized application functionality. All scenarios listed in this manual also apply to the deployment of the application on a virtual platform.
Full functionality (KATA and KEDR)
When using KATA and KEDR functionality, you can scan network traffic, mail traffic, and data on corporate LAN computers.
If more than 5000 hosts with the Endpoint Agent component are used within the organization, it is not recommended to use the Central Node component to process traffic.
You can use the Sensor component as a proxy server for connecting hosts to the Endpoint Agent component and the Central Node. One Sensor component supports the connection of up to 1000 hosts with the Endpoint Agent component.
The criteria for selecting a deployment scenario when using KATA and KEDR functionality are presented in the table below. The selection algorithm is as follows:
If a row contains two cells with identical values, you must select the cell on the left.
Selecting a deployment scenario when using KATA and KEDR functionality
Criterion |
||||
|---|---|---|---|---|
Network traffic and mail traffic cannot be received on the same device. |
No |
Yes |
Yes |
Yes |
Number of Endpoint Agent hosts |
No |
From 5000 to 10,000 |
From 5000 to 10,000 |
Over 10,000 |
1 Gbps |
From 1 to 2 Gbps |
Over 2 Gbps |
Over 2 Gbps |
|
The number of remote infrastructures in which traffic needs to be analyzed. |
No |
One |
Two or more |
Two or more |
The capacities of one Sandbox component are insufficient to analyze all objects within acceptable time frames. |
No |
No |
Yes |
Yes |
In distributed solution mode, each application component must meet the hardware requirements specified in the sizing calculator.
Processing of network traffic, mail traffic, and web traffic (KATA)
It is recommended to use KATA functionality if the organization does not need to process data on corporate LAN computers. If this is the case, only network traffic and mail traffic are processed.
The criteria for selecting a deployment scenario when using KATA functionality are presented in the table below. The selection algorithm is as follows:
If a row contains two cells with identical values, you must select the cell on the left.
Selecting a deployment scenario when using KATA functionality
Criterion |
|||
|---|---|---|---|
Network traffic and mail traffic cannot be received on the same device. |
No |
Yes |
Yes |
1 Gbps |
From 1 to 2 Gbps |
Over 2 Gbps |
|
The number of remote infrastructures in which traffic needs to be analyzed. |
No |
One |
Two or more |
The capacities of one Sandbox component are insufficient to analyze all objects within acceptable time frames. |
No |
No |
Yes |
Processing of data from corporate LAN computers (KEDR)
It is recommended to use KEDR functionality if the organization does not need to process traffic. If this is the case, only data on corporate LAN computers is processed.
Depending on the presence of a third-party Sandbox solution within the organization, you can use one of the following deployment scenarios: