Limitations of the current version of the program

Kaspersky Anti Targeted Attack Platform 3.7 has the following known limitations:

  1. When you upgrade the software from version 3.6 to version 3.7, user-defined TAA (IOA) rules become disabled. After completing the upgrade process, you need to manually re-enable the rules.

Kaspersky Endpoint Agent 3.8 has the following known limitations:

  1. You can install Kaspersky Endpoint Agent through Kaspersky Security Center (KSC) or locally on computers of your corporate LAN. If you are installing Kaspersky Endpoint Agent locally, keep in mind that the installation wizard does not support user names containing CJK characters. To install Kaspersky Endpoint Agent on computers of users whose names contain CJK characters, you must use KSC.
  2. If Kaspersky Endpoint Agent is used on the same device with Kaspersky Endpoint Security, and the file system level encryption (FLE) component is installed in Kaspersky Endpoint Security, Kaspersky Endpoint Agent does not register telemetry events about loading modules (LoadImage) and does not send these events to KATA Central Node component.
  3. When scanning for indicators of compromise, if the search involves parsing text strings, the "is" condition takes into account whitespace, and the need to escape the indicator description in the IOC file with CDATA characters. For example, to detect an object with the copyright "Copyright (C) 1998-2017 Mark Russinovich" by the "is" condition, the indicator description must be specified in the following format: <Content type="string"><![CDATA[Copyright (C) 1998-2017 Mark Russinovich ]]></Content>.

    To simplify description of the indicators, the “contains” condition can also be used.

  4. Kaspersky Endpoint Agent can double-display data about a triggered object when displaying the results of IOC Scan task.
  5. The installer cannot stop the soyuz service until the service is initialized. For example, the installer returns the "Invalid password" error when trying to remove or modify the configuration of the application immediately after installation is completed, since initialization of the soyuz service is not completed and the service cannot be stopped.
  6. When scanning objects using the FileItem IOC document, Kaspersky Endpoint Agent skips objects with restricted access, for example, files that are used by other applications at the time of scanning. Kaspersky Endpoint Agent returns a false negative scan result for such objects.
  7. If localization of Kaspersky Endpoint Agent differs from localization of Kaspersky Endpoint Agent management plug-in for Kaspersky Security Center, some settings may be displayed incorrectly in the output of commands with the “show" option to the command console.
  8. When searching for indicators in the modules loaded into the address space, Kaspersky Endpoint Agent skips cases when the system loads x64 modules into x32 processes. For example, the following cases will not be detected: loading wowcpu64.dll into system32 or loading ntdll into system32. This limitation is reproduced in Windows Server 2008 R2 and Windows 7 x64 operating systems.
  9. When trying to launch Kaspersky Endpoint Agent installer with the permissions of a user whose account contains Chinese characters, the installer fails. It is recommended to install the application with the Local System account permissions, for example, start installation using Kaspersky Security Center.
  10. Kaspersky Endpoint Agent 3.8 cannot be restored or uninstalled from the device if the integrity of the agent.exe module (Kaspersky Endpoint Agent 3.8 command line utility) is violated.
  11. The capability to run and execute Kaspersky Endpoint Agent service (soyuz.exe) with the PPL flag is implemented. This feature is provided by the klelaml.sys driver. Violation of the klelaml.sys driver integrity results in the operating system loading failure. In this case, it is recommended to use Windows system recovery utilities. The absence of the klelaml.sys driver when the PPL flag is enabled for the soyuz.exe process does not lead to the operating system failure, but results in Kaspersky Endpoint Agent crash. In this case, it is recommended to run the application installer and perform recovery in the quiet mode with the REINSTALL=Drivers.klelam key.
  12. Kaspersky Endpoint Agent installer cannot be launched on a device with the operating system to which the active CodeIntegrity policy is applied.
  13. In Kaspersky Endpoint Agent properties in the Administration Console (in the General section), data about the application installation status is displayed incorrectly.
  14. Objects quarantined by Kaspersky Endpoint Agent cannot be sent from Kaspersky Security Center quarantine to Kaspersky for analysis.
  15. When the active policy sections are deactivated, the "Kaspersky Security Center policy is activated" (5) event is generated instead of the "Kaspersky Security Center policy is deactivated" (7) event.
  16. The check boxes corresponding to the Read and Perform operations with device selections permissions that are displayed in the group of settings for role-based access control (RBAC) in the Administration Console, in the section with permissions for managing Kaspersky Endpoint Agent plug-in, do not apply to the group of settings in Kaspersky Security Center. If you select these check boxes, the Read and Perform operations with device selections permissions will not be restricted for the specified users.
  17. When generating event selections, the filters are not applied to some of Kaspersky Endpoint Agent events published in Kaspersky Security Center Administration Console.
  18. Cosmetic errors in the application interface have not been fixed, such as trimmed text in the control interface.
  19. The agent.exe --help command does not support output of help for one specified command. The full list of all commands supported by the utility is displayed in the console.
  20. The name of the workgroup, but not the name of the user is displayed in the User field in the properties of the object quarantined to the Administration Server repository.
  21. The agent.exe command line utility does not support operation with Cyrillic characters. For example, if a node whose address contains Cyrillic characters is specified in the list of Kaspersky Sandbox nodes in Kaspersky Endpoint Agent settings, the output of the --sandbox=show command may contain errors.
  22. The installer of Kaspersky Endpoint Agent and Kaspersky Endpoint Agent management plug-in automatically selects the application localization based on the operating system regional settings on the device where the application or management plug-in is installed:
    • if the operating system uses the RU-RU locale, the Russian version of Kaspersky Endpoint Agent and Kaspersky Endpoint Agent management plug-in is installed;
    • if the operating system uses any locale other than RU-RU, the English version of Kaspersky Endpoint Agent and Kaspersky Endpoint Agent management plug-in is installed.
  23. Application localization affects the language of texts used to describe application modules in the system and when publishing application events to the Windows Event Log, as well as texts of Kaspersky Security Center reports. Kaspersky Endpoint Agent management plug-in localization affects the language of texts used in the application interface of Administration Console (interface of policies, group tasks, and application properties). The application localization cannot be configured manually.

    Please note that if regional settings on managed devices and on the device with Kaspersky Endpoint Agent management plug-in do not match, localization of Kaspersky Endpoint Agent interface in the Administration Console and localization of events published by the application in Kaspersky Security Center reports may not match. Also, the localization of the application interface in the Administration Console and the localization of events published by the application in Kaspersky Security Center reports may differ from the localization of Administration Console interface and the compatible EPP interface in the Administration Console.

  24. Kaspersky Endpoint Agent saves objects to a queue before sending them to Kaspersky Sandbox for scan. The path to the queue folder can be configured in the application policy. By default, Kaspersky Endpoint Agent uses the %APPDATA%\Sandbox\Queue folder.

    In order to prevent integration errors with Kaspersky Sandbox, consider the following recommendations:

    • When changing the default settings, make sure that the folder you specify exists.
    • When changing the default settings, make sure that the Local System user has at least write permissions to the specified folder.
    • Do not delete the folder used for the queue. Do not change the attributes of this folder.
  25. To perform an automatic IOC Scan task in the policy or in the application properties, the login credentials for the Administration Server with write and execute permissions must be specified. If this data is not specified, Kaspersky Endpoint Agent cannot automatically create group IOC Scan tasks.

See also

Kaspersky Anti Targeted Attack Platform

What's new

About Kaspersky Threat Intelligence Portal

Distribution kit

Hardware and software requirements

Page top