Setting
|
Description
|
Name
|
Required setting.
Unique name of the resource. Must contain 1 to 128 Unicode characters.
|
Tenant
|
Required setting.
The name of the tenant that owns the resource.
|
The State toggle switch
|
Used when events must be sent to the destination.
By default, sending events is enabled.
|
Type
|
Required setting.
Destination type, storage.
|
URL
|
Required setting.
URL that you want to connect to. Available formats: host:port, IPv4:port, :port. IPv6 addresses are also supported, however, when you use them, you must specify the interface as well: [address%interface]:port.
Example: [fe80::5054:ff:fe4d:ba0c%eth0]:4222).
You can add multiple addresses using the URL button.
The URL field supports search for services by FQDN, IP address, and name. Search string formats:
<Search value>—search is performed by FQDN, IP addresses, and service names.<First search value ending in one or more digits>:<second search value>—the first value is used to search by the service FQDN or IP address, and the second value is used to search by port.:<value>—search is performed by port.
|
Description
|
Resource description: up to 4,000 Unicode characters.
|
Setting
|
Description
|
Proxy server
|
Drop-down list for selecting a proxy server.
|
Buffer size
|
Sets the size of the buffer. The buffer size may not be less than the event size.
The default value is 1 KB, and the maximum value is 64 MB.
|
Disk buffer size limit
|
Size of the disk buffer in bytes.
The default value is 10 GB.
|
URL selection policy
|
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. Events are sent to one of the available URLs as long as this URL receives events. If the connection is broken (for example, the receiving node is disconnected) a different URL will be selected as the events destination.
- Prefer first. Events are sent to the first URL in the list of added addresses. If it becomes unavailable, events are sent to the next available node in sequence. When the first URL becomes available again, events start to be sent to it again.
- Balanced means that packages with events are evenly distributed among the available URLs from the list. Because packets are sent either on a destination buffer overflow or on the flush timer, this URL selection policy does not guarantee an equal distribution of events to destinations.
|
Buffer flush interval
|
Time (in seconds) between sending batches of data to the destination. The default value is 1 second.
|
Number of handlers
|
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.
|
Health check timeout
|
Frequency of the health check in seconds.
|
Debug
|
This toggle switch lets you specify whether resource logging must be enabled. The default value is Disabled.
|
Disk buffer disabled
|
Toggle switch that lets you enable or disable the disk buffer. By default, the disk buffer is enabled.
The disk buffer is used if the collector cannot send normalized events to the destination. The amount of allocated disk space is limited by the value of the Disk buffer size limit setting.
If the disk space allocated for the disk buffer is exhausted, events are rotated as follows: new events replace the oldest events written to the buffer.
|
Filter
|
In this section, you can specify the criteria for identifying events that must be processed by the resource. You can select an existing filter from the drop-down list or create a new filter.
Creating a filter in resources
To create a filter:
- In the Filter drop-down list, select Create new.
- If you want to keep the filter as a separate resource, select the Save filter check box. In this case, you will be able to use the created filter in various services. This check box is cleared by default.
- If you selected the Save filter check box, enter a name for the created filter resource in the Name field. Maximum length of the name: 128 Unicode characters.
- In the Conditions settings block, specify the conditions that the events must meet:
- Click the Add condition button.
- In the Left operand and Right operand drop-down lists, specify the search parameters. Depending on the data source selected in the Right operand field, you may see fields of additional parameters for identifying the value to be passed to the filter. For example, when you select active list, you must specify the name of the active list, the entry key, and the entry key field.
- In the operator drop-down list, select an operator.
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.
- hasBit—checks whether the left operand (string or number) contains bits whose positions are listed in the right operand (in a constant or in a list).
The value to be checked is converted to binary and processed right to left. Chars are checked whose index is specified as a constant or a list. If the value being checked is a string, then an attempt is made to convert it to integer and process it in the way described above. If the string cannot be converted to a number, the filter returns False. - hasVulnerability—checks whether the left operand contains an asset with the vulnerability and vulnerability severity specified in the right operand.
If you do not specify the ID and severity of the vulnerability, the filter is triggered if the asset in the event being checked has any vulnerability. - inActiveList—this operator 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.
- inDictionary—checks whether the specified dictionary contains an entry defined by the key composed with the concatenated values of the selected event fields.
- 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.
- inContextTable—presence of the entry in the specified context table.
- intersect—presence in the left operand of the list items specified in the right operand.
- If you want the operator to be case-insensitive, select the do not match case check box. The selection of this check box does not apply to the InSubnet, InActiveList, InCategory or InActiveDirectoryGroup operators. This check box is cleared by default.
- If you want to add a negative condition, select If not from the If drop-down list.
You can add multiple conditions or a group of conditions. - If you have added multiple conditions or groups of conditions, choose a selection condition (and, or, not) by clicking the AND button.
- If you want to add existing filters that are selected from the Select filter drop-down list, click the Add filter button. You can view the nested filter settings by clicking the
 button.
|