Scenario for configuring integration with KATA

Configuring integration of Kaspersky Web Traffic Security with KATA consists of the following steps.

  1. Adding a KATA server

    When adding a KATA server, you must compare the certificate fingerprints displayed in the web interfaces of KWTS and KATA. If the fingerprints match, the administrator confirms addition of the server. Then the node with role Control sends the address and certificate of the KATA sever to all cluster nodes without waiting for authorization confirmation.

  2. Selecting an integration mode

    Kaspersky Web Traffic Security provides two modes of integration with KATA. You can send files to KATA so that they can be scanned (in this case, KWTS serves as an external system for KATA) and/or receive information about objects detected by KATA. These modes work independent of each other.

  3. Configuring KATA cache settings

    When applying protection rules and the default policy, Kaspersky Web Traffic Security takes into account the objects whose information is stored in the KATA cache. You can configure the period for storing them in the cache. When this period expires, these objects will no longer be considered when processing traffic.

  4. Authorization of Kaspersky Web Traffic Security in the KATA web interface

    When adding a KATA server, a request is sent for authorization of the external system. The KATA administrator must confirm this request in the KATA web interface. For details about processing requests from external systems, please refer to the Kaspersky Anti Targeted Attack Platform Help Guide.

Page top