Kaspersky Unified Monitoring and Analysis Platform

Destinations

Destination resources are used to receive events and then forward them to other services. The settings of destinations are configured on two tabs: Basic settings and Advanced settings. The available settings depend on the selected type of destination.

Basic settings

• Name (required)—a unique name for this type of resource. Must contain from 1 to 128 Unicode characters.
• Tenant (required)—name of the tenant that owns the resource.
• Disabled toggle switch—used if you do not need to send events to a destination. By default, sending events is enabled.
• Type (required)—drop-down list for selecting the type of destination:
  • nats—used for NATS communications.
  • tcp—used for communications over TCP.
  • http—used for HTTP communications.
  • kafka—used for Kafka communications.
  • file—used for writing to a file.
  • storage—used to transmit data to the storage.
  • correlator—used to transmit data to the correlator.
• URL (required)—URL where events should be sent. The port must be specified together with the URL. For example: hostname:port.

  You can specify multiple destination URLs using the URL button for all types except nats and file, if your KUMA license includes High Level Availability module.

  If you have selected storage or correlator as the destination type, the URL field can be populated automatically using the Copy service URL drop-down list that displays active services of the selected type.

• Topic (required)—setting for the types of destinations: nats and kafka. The topic that data should be written to. The topic name must contain from 1 to 255 Unicode characters.
• Description—up to 256 Unicode characters describing the resource.

Advanced settings

• Compression is a drop-down list where you can enable Snappy compression. By default, compression is disabled.
• Proxy is a drop-down list for proxy server resource selection.
• Buffer size field is used to set buffer size (in bytes) for the destination resource. The default value is 1 MB, and the maximum value is 64 MB.
• Timeout field is used to set the timeout (in seconds) for another service or component response. The default value is 30.
• Disk buffer size limit field is used to specify the size of the disk buffer in bytes. The default size is 10 GB.
• Storage ID is a NATS storage identifier.
  • TLS mode specifies whether TLS encryption is used:
    • Disabled (default)—do not use TLS encryption.
    • Enabled—use encryption without certificate verification.
    • With verification—use encryption with verification that the certificate was signed with the KUMA root certificate. The root certificate and key of KUMA are created automatically during program installation and are stored on the KUMA Core server in the folder /opt/kaspersky/kuma/core/certificates/.

    When using TLS, it is impossible to specify an IP address as a URL.

• URL selection policy is a drop-down list in which you can select a method for determining which URL to send events to if several URLs have been specified:
  • Any
  • Prefer first
  • Round robin
• Delimiter is used to specify the character delimiting the events. By default, \n is used.
• Path—the file path if the file destination type is selected.
• Flush interval sets the time (in seconds) between sending data to the destination resource. The default value is 100.
• Workers—this field is used to set the number of services processing the queue. By default, this value is equal to the number of vCPUs of the KUMA Core server.
• You can set health checks using the Health check path and Health check timeout fields. You can also disable health checks by selecting the Health Check Disabled check box.
• Debug—a drop-down list where you can specify whether resource logging should be enabled. By default it is Disabled.
• The Disk buffer disabled drop-down list is used to enable or disable the use of a disk buffer. By default, the disk buffer is disabled.
• In the Filter section you can specify conditions to identify events that will be processed by the aggregation rule resource. You can select an existing filter resource from the drop-down list, or select Create new to create a new filter.

  Creating a filter in resources

  1. In the Filter drop-down menu, select Create new.
  2. If you want to keep the filter as a separate resource, set the Save filter toggle switch. This can be useful if you decide to reuse the same filter across different services. The toggle switch is turned off by default.
  3. If you toggle the Save filter switch on, enter a name for the created filter resource in the Name field. The name must contain from 1 to 128 Unicode characters.
  4. In the conditions section, specify the conditions that the events must meet:
     • The Add condition button is used to add filtering conditions. You can select two values (two operands, left and right) and assign the operation you want to perform with the selected values. The result of the operation is either True or False.
       • In the operator drop-down list, select the function to be performed by the filter.

         Filter operators

         • = – the left operand equals the right operand.
         • <—the left operand is less than the right operand.
         • <=—the left operand is less than or equal to the right operand.
         • >—the left operand is greater than the right operand.
         • >=—the left operand is greater than or equal to the right operand.
         • inSubnet—the left operand (IP address) is in the subnet of the right operand (subnet).
         • contains—the left operand contains values of the right operand.
         • startsWith—the left operand starts with one of the values of the right operand.
         • endsWith—the left operand ends with one of the values of the right operand.
         • match—the left operand matches the regular expression of the right operand. The RE2 regular expressions are used.
         • inActiveList—this filter has only one operand. Its values are selected in the Key fields field and are compared with the entries in the active list selected from the Active List drop-down list.
         • inCategory—the asset in the left operand is assigned at least one of the asset categories of the right operand.
         • inActiveDirectoryGroup—the Active Directory account in the left operand belongs to one of the Active Directory groups in the right operand.
         • TIDetect—this operator is used to find events using CyberTrace Threat Intelligence (TI) data. This operator can be used only on events that have completed enrichment with data from CyberTrace Threat Intelligence. In other words, it can only be used in collectors at the destination selection stage and in correlators.

         You can use the Match case check box in the Operator drop-down list to choose whether the values passed to the filter should be case sensitive. This check box is cleared by default.

       • In the Left operand and Right operand drop-down lists, select where the data to be filtered will come from. As a result of the selection, Advanced settings will appear. Use them to determine the exact value that will be passed to the filter. For example, when choosing active list you will need to specify the name of the active list, the entry key and the entry key field.
       • You can use the If drop-down list to choose whether you want to create a negative filter condition.

       Conditions can be deleted using the button.

     • The Add group button is used to add groups of conditions. Operator AND can be switched between AND, OR, and NOT values.

       A condition group can be deleted using the button.

     • Using the Add filter button you can add existing filter resources selected in the Select filter drop-down list to the conditions. You can navigate to a nested filter resource using the button.

       A nested filter can be deleted using the button.