Administration Server on LAN, managed devices on internet, firewall in use

The figure below shows data traffic if the Administration Server is on a local area network (LAN) and the managed devices are on the internet. In this figure, a corporate firewall of your choice is in use. Refer to the documentation of the application for details.

Administration Server on a local area network; managed devices connect to the Administration Server through a corporate firewall

This deployment scheme is recommended if you do not want the mobile devices to connect to the Administration Server directly and do not want to assign a connection gateway in the DMZ.

The arrows indicate the initiation of traffic: each arrow points from a device that initiates the connection to the device that "answers" the call. The number of the port and the name of the protocol used for data transfer are provided. Each arrow has a number label, and details about the corresponding data traffic are as follows:

1. Administration Server sends data to the database. If you install the Administration Server and the database on different devices, you must make available the necessary ports on the device where the database is located (for example, port 3306 for MySQL Server and MariaDB Server, or port 5432 for PostgreSQL Server or Postgres Pro Server). Please refer to the DBMS documentation for the relevant information.
2. Requests for communication from the Administration Server are transferred to all non-mobile managed devices through UDP port 15000.

   Network Agents send requests to each other within one broadcasting domain. The data is then sent to the Administration Server and is used for defining the limits of the broadcasting domain and for automatic assignment of distribution points (if this option is enabled).

   If Administration Server does not have direct access to the managed devices, communication requests from Administration Server to these devices are not sent directly.

3. Information about shutdown of the managed devices is transferred from Network Agent to the Administration Server through UDP port 13000.
4. The Administration Server receives connection from Network Agents and from secondary Administration Servers through SSL port 13000.

   If you used an earlier version of Kaspersky Security Center, the Administration Server on your network can receive connection from Network Agents through non-SSL port 14000. Kaspersky Security Center Linux also supports connection of Network Agents through port 14000, although using SSL port 13000 is recommended.

5. The managed devices (except for mobile devices) request activation through TCP port 17000. This is not necessary if the device has its own access to the internet; in this case, the device sends the data to Kaspersky servers over the internet directly.
6. Kaspersky Security Center Web Console Server sends data to the Administration Server, which may be installed on the same or on a different device, through TLS port 13299.

   6a. Data from the browser, which is installed on a separate device of the administrator, is transferred to Kaspersky Security Center Web Console Server through TLS port 8080. The Kaspersky Security Center Web Console Server can be installed either on the Administration Server or on another device.

7. Applications on a single device exchange local traffic (either on the Administration Server or on a managed device). No external ports have to be opened.
8. Data from the Administration Server to the Kaspersky servers (such as KSN data or information about licenses) and data from the Kaspersky servers to the Administration Server (such as application updates and anti-virus database updates) are transferred using the HTTPS protocol.

   If you do not want your Administration Server to have access to the internet, you must manage this data manually.

9. Requests for packages from managed devices, including mobile devices, are transferred to the Web Server, which is on the same device as the Administration Server.