for Windows, macOS, and Linux
This section lets you configure telemetry from managed devices to telemetry collection servers. Telemetry is a list of events that have occurred on the protected computer. Kaspersky Endpoint Security analyzes telemetry and sends it to Kaspersky Anti Targeted Attack Platform or to telemetry collection servers during synchronization. Telemetry events arrive on the server almost continuously. Kaspersky Endpoint Security initiates synchronization with the server when any of the following conditions are satisfied:
If there is no connection between Kaspersky Endpoint Security and the server, the application queues new events. When the connection is restored, Kaspersky Endpoint Security sends queued events to the server in proper order. To avoid overloading the server, Kaspersky Endpoint Security may skip some events.
You can manage synchronization settings for each Built-in Agent in the "Built-in agents" section and select optimal values depending on your network load.
In this section, you can configure:
EDR Expert (on-premise) telemetry
for Windows, macOS, and Linux
EDR Expert (on-premise) telemetry settings
|
Settings |
OS |
Description |
|---|---|---|
|
EDR Expert (on-premise) telemetry |
|
Import and Export. You can export EDR Expert (on-premise) telemetry settings to a JSON file. Then you can modify the file to, for example, add a large number of event IDs. You can also use the export/import function to back up the settings of sent events or to migrate the list to another policy. |
|
General exclusions |
|
To optimize the transmitted data, you can configure exclusion rules for certain event types. Kaspersky Endpoint Security does not collect telemetry that falls under such a rule. This lets you reduce traffic and avoid processing events from trusted objects and processes. Rule name. Action:
Condition. Rule-triggering condition. Specify a telemetry parameter, a conditional operator, and the value of the parameter. By default, Kaspersky Endpoint Security combines rule triggering criteria with a logical AND. You can add multiple conditions or condition groups using the AND and OR logical operators. |
|
All event types |
|
List of event types for which telemetry is defined by default by Kaspersky. You can manually enable or disable telemetry for each event type and configure telemetry exclusion and inclusion rules. |
EDR (KATA) / NDR (KATA) telemetry
for Windows and Linux
To improve performance and optimize data transmission to the Telemetry server, you can configure telemetry exclusions. For example, you can choose not to send network communications data for individual applications.
EDR (KATA) / NDR (KATA) telemetry exclusion settings
|
Settings |
OS |
Description |
|---|---|---|
|
Excluded processes |
|
Kaspersky Endpoint Security does not process data related to processes from the list. Optimize the telemetry size to send. Kaspersky Endpoint Security allows optimizing the amount of transmitted data and excluding events with certain codes from telemetry: code 102 (basic communications) and 8 (network activity of the process) for the Microsoft SMB protocol, the WinRM service, and the klnagent.exe process of the Network Agent, as well as extended information about the types of network packets for all types of network protocols. Kaspersky Endpoint Security combines rule triggering criteria with a logical AND. Process and Parent process:
You can also select a file manually, and the application will automatically fill out the fields from the selected file. In 64-bit operating systems, you must manually enter the parameters of the 64-bit version of the executable file of a process from the Use for the following event types:
|
|
Excluded network communications |
|
Kaspersky Endpoint Security does not process data related to network communications from the list. In the exclusion rule you can specify: Rule name. Direction. Protocol. Raw socket. Protocol number. Local address. The network address of the computer for which Kaspersky Endpoint Security is excluding telemetry from network traffic. Local port or range. Remote address. The network address of the computer for which Kaspersky Endpoint Security is excluding telemetry from network traffic. Remote port or range. Only the IPv4 format is supported for IP addresses. Apply the rule to the selected applications. If this check box is selected Kaspersky Endpoint Security excludes EDR telemetry from the network traffic for executable files of applications from the list. |
|
Excluded file operations |
|
Kaspersky Endpoint Security does not process file operations from the list. In the exclusion rule you can specify: Rule name. File name or mask. The file name or mask to which Kaspersky Endpoint Security applies the exclusion rule when the file is accessed. Kaspersky Endpoint Security supports the Select file operation. Type of file operation to which the rule will apply. Previous path. Kaspersky Endpoint Security combines rule triggering criteria with a logical AND. Process and Parent process:
You can also select a file manually, and the application will automatically fill out the fields from the selected file. In 64-bit operating systems, you must manually enter the parameters of the 64-bit version of the executable file of a process from the |
|
Excluded DNS operations |
|
Kaspersky Endpoint Security does not process DNS operations from the list. In the exclusion rule you can specify: Rule name. Kaspersky Endpoint Security combines rule triggering criteria with a logical AND. Process and Parent process:
You can also select a file manually, and the application will automatically fill out the fields from the selected file. In 64-bit operating systems, you must manually enter the parameters of the 64-bit version of the executable file of a process from the DNS operation:
|
|
Excluded LDAP operations |
|
Kaspersky Endpoint Security does not process LDAP operations from the list. In the exclusion rule you can specify: Rule name. Kaspersky Endpoint Security combines rule triggering criteria with a logical AND. Process and Parent process:
You can also select a file manually, and the application will automatically fill out the fields from the selected file. In 64-bit operating systems, you must manually enter the parameters of the 64-bit version of the executable file of a process from the LDAP operation:
|
|
Excluded process access queries |
|
Kaspersky Endpoint Security does not process access requests to processes from the list. In the exclusion rule you can specify: Rule name. Kaspersky Endpoint Security combines rule triggering criteria with a logical AND. Process, Parent process, Target process, File of a source process and File of a target process.
You can also select a file manually, and the application will automatically fill out the fields from the selected file. In 64-bit operating systems, you must manually enter the parameters of the 64-bit version of the executable file of a process from the Process access queries:
|
|
Excluded code injections |
|
Kaspersky Endpoint Security does not process code injections from the list. In the exclusion rule you can specify: Rule name. Kaspersky Endpoint Security combines rule triggering criteria with a logical AND. Process and Parent process:
You can also select a file manually, and the application will automatically fill out the fields from the selected file. In 64-bit operating systems, you must manually enter the parameters of the 64-bit version of the executable file of a process from the Code injections:
|
|
Excluded WMI queries |
|
Kaspersky Endpoint Security does not process WMI requests from the list. In the exclusion rule you can specify: Rule name. Kaspersky Endpoint Security combines rule triggering criteria with a logical AND. Process and Parent process:
You can also select a file manually, and the application will automatically fill out the fields from the selected file. In 64-bit operating systems, you must manually enter the parameters of the 64-bit version of the executable file of a process from the WMI queries:
|
|
Excluded pipe operations |
|
Kaspersky Endpoint Security does not process pipe operations from the list. In the exclusion rule you can specify: Rule name. Kaspersky Endpoint Security combines rule triggering criteria with a logical AND. Process and Parent process:
You can also select a file manually, and the application will automatically fill out the fields from the selected file. In 64-bit operating systems, you must manually enter the parameters of the 64-bit version of the executable file of a process from the Pipe operations:
|
|
Excluded registry changes |
|
Kaspersky Endpoint Security does not process registry modifications from the list. In the exclusion rule you can specify: Rule name. Kaspersky Endpoint Security combines rule triggering criteria with a logical AND. Process and Parent process:
You can also select a file manually, and the application will automatically fill out the fields from the selected file. In 64-bit operating systems, you must manually enter the parameters of the 64-bit version of the executable file of a process from the Registry changes:
|
|
Excluded operations with devices |
|
Kaspersky Endpoint Security does not process operations related to USB devices from the list. In the exclusion rule you can specify: Rule name. Device type. Device ID. Device name. |
for Windows
By default, Kaspersky Endpoint Security sends a limited set of telemetry to KUMA. To improve performance and optimize data transmission to the KUMA server, you can manually add individual event logs.
For a list of Windows events that Kaspersky Endpoint Security sends to KUMA by default, see the Endpoint Security for Windows Help.
KUMA telemetry settings
|
Parameter |
OS |
Description |
|---|---|---|
|
Windows Event Logs |
|
List of Windows event logs that you have added manually. You can add logs one by one or import a JSON file with settings. For each event log, you can select how you want it to be sent:
You can also configure exclusion or inclusion rules for the relevant event sending mode. To add rules, you need to specify the ID of the event in the Windows event log. You can list multiple event IDs in a rule. When specify multiple event IDs, use commas as delimiters. |