Kaspersky Anti Targeted Attack Platform

Configuring the sizing settings of the application

If you are using the

and mode, use the web interface of the PCN or SCN server for which you want to configure parameters.

You can change the operational load on the Central Node component. For example, you can connect additional hosts with the Endpoint Agent component or servers with the Sensor component to the Central Node component. To do this, you need to specify the planned volume of SPAN traffic, mail traffic, the number of hosts with the Endpoint Agent component, as well as the size of the Storage and event database. Kaspersky Anti Targeted Attack Platform will determine the optimal configuration of the Central Node server taking into account the specified settings.

If the Central Node component is deployed as a cluster, the application determines the optimal configuration of all servers in the cluster.

For the cluster to function, after configuring the sizing parameters, time must be synchronized on servers of the cluster. Before configuring sizing parameters, make sure that integration with a functioning NTP server is configured for at least one server in the cluster.

You can configure NTP server integration in the web interface of Kaspersky Anti Targeted Attack Platform or in the component administrator menu on any server in the cluster. If you have not previously configured NTP server integration, we recommend restarting the cluster servers after configuring it.

To configure the Central Node servers:

  1. In a browser on any computer on which access to the Central Node server has been allowed, enter the IP address of the server with the Central Node component into the browser's address bar.

    If you are using the high availability version of the application, you can enter the IP address of any server of the Central Node cluster or the fully qualified domain name (FQDN) of the cluster.

    An input window for account credentials of the Kaspersky Anti Targeted Attack Platform user opens.

  2. Enter the user name, "admin", and the password that was set during the installation of the application.
  3. Click Log in.
  4. Go to the Server configuration section.
  5. In the Number of Endpoint Agents field, specify the effective number of Endpoint Agent hosts for your infrastructure.

    For details on how to calculate the effective number of Endpoint Agent hosts, see the scaling guide.

    If you are not using a KEDR license key, specify 0.

  6. In the Mail traffic, messages per second field, specify the planned number of emails per second.

    If you are not using a KATA license key, specify 0.

  7. In the SPAN traffic, Mbps field, specify the planned amount of traffic from SPAN ports on servers with the Sensor component.

    If you are not using a KATA license key, specify 0.

  8. If you installed Central Node on a server, in the Disk space section, leave default values in the Events database, GB and Storage, GB fields.
  9. If you installed Central Node as a cluster, in the Available disk space section, specify the sizes of the event database and Storage in one of the following ways:
    • Move the slider separating the Events database and Storage to the left or right.

      Keep in mind that reducing the size of the event database or Storage irreversibly deletes the oldest data in accordance with the rotation rules. Enlarging the event database or Storage does not cause data loss.

    • Specify the values in the Events database, GB and Storage, GB fields.

      If the Central Node component is deployed as a high availability cluster, use the Sizing Guide to calculate the size of the events database.

    • If necessary, you can leave free space on disk by moving the last slider on the right.

    Disk space is automatically reserved for the alert database when the Central Node component is installed.

  10. Click Configure.

If Central Node is installed on a server, Kaspersky Anti Targeted Attack Platform determines the optimal server configuration in accordance with the specified parameters. If Central Node is installed as a cluster, the application configures the servers of the cluster.