Preparing the IT infrastructure for program components installation

Before installing the program, prepare your corporate IT infrastructure for the installation of components of Kaspersky Anti Targeted Attack Platform:

1. Ensure that the servers, the computer intended for working with the program web interface, and the computers to be installed with Kaspersky Endpoint Agent all satisfy the hardware and software requirements.
2. Perform the following preliminary preparations of the corporate IT infrastructure for installation of the Sandbox component:
   1. For both network interfaces, block access of the server hosting the Sandbox component to the corporate LAN in order to keep the network safe from the objects being analyzed.
   2. For the first network interface, allow Internet access for the server hosting the Sandbox component for the purpose of analysis of the behavior of objects.
   3. For the second network interface, allow inbound connections to the following ports for the server hosting the Sandbox component:
      • TCP 22 for connection to the server over the SSH protocol.
      • TCP 443 for receiving objects to scan from the Central Node component.
      • TCP 8443 for using the program web interface.
3. Perform the following preliminary preparations of the corporate IT infrastructure for installation of the Central Node component:
   1. Allow inbound connections to the server hosting the Central Node component on the following ports:
      • TCP 22 for connection to the server via SSH.
      • TCP 443 for receiving data from computers with Kaspersky Endpoint Agent.
      • TCP 8443 for viewing scan results in the program web interface.
   2. Allow outbound connections to the following ports for the server hosting the Central Node component:
      • TCP 80, 443 and 1443 for communication with servers of the KSN service and Kaspersky update servers.
      • TCP 443 for sending objects to the Sandbox component so that they can be scanned.
      • TCP 601 for sending messages to a SIEM system.
4. Perform the following preliminary preparations of the corporate IT infrastructure for installation of the Sensor component:
   1. For the network interface used for integration with a proxy server and mail server, allow inbound connections to the following ports for the server hosting the Sensor component:
      • TCP 22 for connection to the server via SSH.
      • TCP 1344 for receiving traffic from a proxy server.
      • TCP 25 for receiving SMTP traffic from a mail server.
      • TCP 443 when forwarding traffic from Kaspersky Endpoint Agent computers to the server with the Central Node component.
   2. Allow outbound connections to the following ports for the server hosting the Sensor component:
      • TCP 80 and 443 for communication with servers of the KSN service and Kaspersky update servers.
      • TCP 995 (or TCP 110 for unprotected connections) for integration with a mail server.

      If you install a second network interface that receives only mirrored traffic in a VMware ESXi virtual environment, use the E1000 network adapter or disable the LRO (large receive offload) option on a VMXNET3 network adapter.

5. On network equipment, allow an encrypted communication channel between servers that have the Central Node and Sensor components.

   The connection between servers that have the Central Node and Sensor components is established within the encrypted communication channel based on IPSec using the ESP protocol.

6. If you are using distributed solution and multitenancy mode, perform the following preliminary preparations of the corporate IT infrastructure for installation of the Central Node components:
   1. Allow inbound connection to port 8443 for the server with the PCN role.
   2. On network equipment, allow the establishment of an encrypted communication channel between servers that have the Central Node and Sensor components.

      The connection between servers that have the PCN and SCN role is established within the encrypted communication channel based on IPSec using the ESP protocol.

If needed, you can designate other ports for the program's components to use in the administrator menu of the server with the Central Node component. If you change the ports in the administrator menu, you need to allow connections to these ports in your corporate IT infrastructure.

See also Preparing the IT infrastructure for integration with a mail server used for receiving messages via POP3 Preparing the IT infrastructure for integration with a mail server used for receiving messages via SMTP Preparing the virtual machine for installing the Sandbox component

Page top