Kaspersky Anti Targeted Attack Platform 4.0 has the following known limitations:
Version 4.0 upgrade packages can only be installed using the administrator menu or in Technical Support Mode. When connecting to a server with the Central Node component over SSH, you must make sure UTF-8 is used as the local encoding. If a different encoding is used as the local encoding, the update package will fail to install.
There is no way to disable only automatic sending of files to be scanned by Sandbox for an individual TAA (IOA) rule. You can add the selected TAA (IOA) rule to exclusions. In this case, event marking and creation of alerts in accordance with this rule is also stopped.
When scanning processes running on a Kaspersky Endpoint Agent for Windows hosts using YARA rules, only user processes are scanned. Processes with PID under 10 are not scanned.
In the IOC scan schedule settings, the start time is now set in UTC. When upgrading Kaspersky Anti Targeted Attack Platform from version 3.7.2 to version 4.0, start time of IOC scan on hosts with Kaspersky Endpoint Agent for Windows will be shifted according to their time zone
Limitations that apply when integrating with Kaspersky Endpoint Agent 3.12 for Linux:
Hosts with Kaspersky Endpoint Agent for Linux program cannot use the following functions:
No notifications are created about the unsuccessful application of a prevention rule on hosts with Kaspersky Endpoint Agent for Linux program.
Finding indicators of compromise on hosts using IOC files.
No notifications are created about the unsuccessful search of indicators of compromise on hosts with the Kaspersky Endpoint Agent for Linux program.
Searching the event database using the OSVersion criterion displays only hosts with the Kaspersky Endpoint Agent for Linux program. Hosts with the Kaspersky Endpoint Agent for Windows program are not displayed in search results.
The OS name field in the event information is only filled in for events that are logged in the event database by Kaspersky Endpoint Agent for Linux. Event information logged in the event database by Kaspersky Endpoint Agent for Windows does not have this field filled in.
The list of events that Kaspersky Endpoint Agent for Linux logs in the event database is limited to the following types:
When you create the task, the program does not attempt to verify the path to the executable file or the file that you want to receive.
In information about events registered in the event database by Kaspersky Endpoint Agent for Linux, the Time created field displays file modification time.
Kaspersky Endpoint Agent 3.12 for Windows has the following known limitations:
The component that prohibits opening documents has the following limitation: document blocking rules are not applied to objects that are opened using OLE automation.
Before sending telemetry events to the KATA Central Node server, Kaspersky Endpoint Agent saves data in the event queue. If the event queue exceeds 10 000 unprocessed events, Kaspersky Endpoint Agent does not queue the events until free slots appear in the queue.
If Kaspersky Endpoint Agent is running on devices with the Windows 7 operation system, the program excludes data about network connections related to processes with PID=4 and PID=0 from telemetry.
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.
If more than one application is specified as the value of the Application criterion when configuring the settings of network isolation exclusions, Kaspersky Endpoint Agent allows connection only for the first application in the list. Network connections for other applications specified in the list will be ignored. This limitation is reproduced when isolating devices with Windows 7 or Windows Server 2008 R2 operating systems.
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 John Smith" by the "is” condition, the indicator description must be specified in the following format: <Content type="string"><![CDATA[Copyright (C) 1998-2017 John Smith]]></Content>. To simplify description of the indicators, the “contains” condition can also be used.
Kaspersky Endpoint Agent can double-display data about a triggered object when displaying the results of IOC Scan task.
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 program immediately after installation is completed, since initialization of the soyuz service is not completed and the service cannot be stopped.
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.
If localization of Kaspersky Endpoint Agent differs from localization of Kaspersky Endpoint Agent administration plug-in for Kaspersky Security Center, some settings may not be displayed correctly in the outputs of the "show" commands in the command console.
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.
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 program with the Local System account permissions, for example, start installation using Kaspersky Security Center.
Kaspersky Endpoint Agent cannot be restored or uninstalled from the device if the integrity of the agent.exe module (Kaspersky Endpoint Agent command line utility) is violated.
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 program installer and perform recovery in the quiet mode with the REINSTALL=Drivers.klelam key.
Kaspersky Endpoint Agent installer cannot be launched on a device with the operating system to which the active CodeIntegrity policy is applied.
In Kaspersky Endpoint Agent properties in the General section of the Administration Console, information about the program installation status is displayed incorrectly.
Objects quarantined by Kaspersky Endpoint Agent cannot be sent from Kaspersky Security Center quarantine to Kaspersky for analysis.
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.
When generating event selections, the filters are not applied to some of Kaspersky Endpoint Agent events published in Kaspersky Security Center Administration Console.
In Kaspersky Endpoint Agent interface, displayed text of some controls is truncated.
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.
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.
The installer of Kaspersky Endpoint Agent and Kaspersky Endpoint Agent management plug-in automatically selects the program localization based on the operating system regional settings on the device where the program 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 administration 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 administration plug-in is installed.
Program localization affects the language of texts used to describe program modules in the system and when publishing program 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 program interface of Administration Console (interface of policies, group tasks, and program properties). Configuring the localization of the program manually is not supported.
Please note that if regional settings on managed devices and on the device with Kaspersky Endpoint Agent administration plug-in do not match, localization of Kaspersky Endpoint Agent interface in the Administration Console and localization of events published by the program in Kaspersky Security Center reports may not be the same. Also, the localization of the program interface in the Administration Console and the localization of events published by the program in Kaspersky Security Center reports may differ from the localization of Administration Console interface and the compatible EPP interface in the Administration Console.
After installing, restoring, changing set of components, or removing Kaspersky Endpoint Agent, it is recommended to restart the operating system as soon as possible because changes to some program settings can only be finalized at system startup.
When creating an installation package in Kaspersky Security Center version 12 or later to install Kaspersky Endpoint Agent on Windows XP devices, you must use the installer file (setup.exe) from the installation package created in Kaspersky Security Center version 10.5.
In Kaspersky Security Center 13.2 or later, to install Kaspersky Endpoint Agent on Windows XP devices, you must use the standard Kaspersky Endpoint Agent 3.12 distribution kit instead of the installation package created in Kaspersky Security Center.
If group tasks are scheduled to run "At program start", the update of the task completion status in task history is delayed. For this reason, in some cases, the task history will not display task completion status.
Kaspersky Endpoint Agent 3.12 for Linux has the following known limitations:
Kaspersky Endpoint Agent for Linux does not support AppArmor and SELinux mandatory access control systems in their enforcing modes. For the program to work correctly, these systems must be switched to permissive mode.
Kaspersky Endpoint Agent for Linux requires installing Linux Audit Daemon 2.8 or later on the device.
For connection of Kaspersky Endpoint Agent for Linux with Kaspersky Endpoint Security for Linux rsyslog service with loaded imuxsock module is used. To check if the module is loaded in the rsyslog service configuration, run the following command: grep -r imuxsock /etc/rsyslog*. If the module loading string is commented, remove the # comment sign before the string and restart rsyslog service to save the changes.