Kaspersky Anti Targeted Attack Platform

Ensuring security when using Kaspersky Anti Targeted Attack Platform API

External systems access the functionality of the application using the Kaspersky Anti Targeted Attack Platform API by establishing encrypted HTTPS connections. Certificates issued by the Central Node component of Kaspersky Anti Targeted Attack Platform are used to secure the connections. This component issues certificates for the connectors that external systems use to connect to the Server.

A separate connector must be created in Kaspersky Anti Targeted Attack Platform for each external system. A connection can be established through a connector only by using the specific certificate that was issued by the Central Node component and saved in the communication data package for that connector. A connection cannot be established if the external system presents a certificate from a different connector, a different Central Node component of Kaspersky Anti Targeted Attack Platform, or a certificate used for other connections (for example, a certificate of the Sensor component).

After establishing an encrypted connection, the external system must request an authentication token for the connector that the external system will use in requests sent to the Central Node REST API server.

An authentication token is valid for 10 hours after it was issued. If a token needs to be used for a longer period, the external system must request a time extension before the token expires.

For information about requests and methods supported by Kaspersky Anti Targeted Attack Platform API, see the documentation for the Kaspersky Anti Targeted Attack Platform API.

When processing requests from external systems, Kaspersky Anti Targeted Attack Platform uses the audit log to record information about attempts to perform the following operations:

  • Receive an authentication token.
  • Extend the validity period for an authentication token.
  • Add a device to the devices table.
  • Edit device information.
  • Delete a device.
  • Query the audit log (when first reading audit entries through the connector after loading the web server).