This section explains how to add a custom or third-party feed and change its settings.
The form for adding a custom or third-party feed can be disabled due to restrictions imposed by the license key or licensing level.
All custom or third-party feeds that you add to Kaspersky CyberTrace must be in UTF-8 encoding. If your custom or third-party feeds have a different encoding, make sure to convert them to UTF-8.
You can add custom feeds that contain subnet masks of Class C networks. These feeds can be used in the matching process: you can mark the feed field as IP.
Currently, you can add feeds through only one field of the URL or DOMAIN type. That is, if you mark one field in a feed as URL or DOMAIN, do not mark another field in the feed as URL or DOMAIN. The URL and DOMAIN types are counted as the same field type.
No KL_ALERT_OutdatedFeed events are generated for the added feeds.
Adding a custom feed
To add a custom or third-party feed:
To add a new feed:
The Custom feed window opens:
Adding a custom or third-party feed
In the feed name, you can use Latin letters, digits, underscores, and hyphens. The name must differ from other feed names that are already used.
You can specify the path in one of the following forms:
The specified network path is available for the active user account, while Feed Service and Feed Utility run under the LocalService account. Therefore, if you need to download custom and third-party feeds from a network directory, give the LocalService user account access to this network directory.
The network directory must be mapped.
You can only specify the network path in Windows.
Path to the certificate that gives access to the feed. The full path must be specified.
You can only specify the certificate path if the feed will be downloaded over an HTTPS connection.
This type can be one of the following:
If a feed in JSON format contains a field with a subnet mask value, Kaspersky CyberTrace discloses data only if it is a first-level field. If this field is nested, Kaspersky CyberTrace cannot disclose data.
Kaspersky CyberTrace supports STIX versions 1 and 1.1.
;
) is used as a delimiter.In the following example, the root element is root
:
<root> <url>http</url> <ip>1</ip> </root> <root> <url>https</url> <ip>2</ip> </root> |
In the following example, the root element is root/element*
:
<root> <element1> <url>http</url> <ip>1</ip> </element1> </root> <root> <element2> <url>https</url> <ip>2</ip> </element2> </root> |
Note the use of a wildcard character (*)
. For more information on the proper use of wildcards for an XML feed, see instructions for choosing feed fields to be used for matching.
If this check box is selected, the STIX feed must be downloaded from the TAXII server.
The name of the collection that must be downloaded from the TAXII server. Note that you can specify only one collection name at a time.
Kaspersky CyberTrace does not support TAXII feeds that have information about the reputation of one object. IBM feeds like xfe.ipr and xfe.url are not supported.
If basic authentication is used, specify the user name and password to the TAXII server.
After you specify a custom or third-party feed and the settings for it, the feed is fully loaded and a part of it is displayed so that you can choose the fields of the feed to be used in the matching process.
Selecting feed fields for matching
This is relevant for feeds in the following formats: CSV, JSON, or XML.
To choose feed fields to be used for matching,
For every field, specify the following information:
One of the following values can be used as the field type:
Note that there must be at least one field with a type other than CONTEXT. Such fields are used for matching. When such a field is involved in the detection process, a detection event is generated with the %FEEDNAME%_%FIELDTYPE%
category, where %FEEDNAME%
is the feed name and %FIELDTYPE%
is the field type.
A feed can have one field of the CONTEXT type, at most one field of the URL or DOMAIN type, and several fields of other types. The URL and DOMAIN types are considered the same field type.
This name will be referred to in the matching process.
In the field name, you can use Latin letters, digits, underscores, and hyphens. The name must contain at least one Latin letter.
For a JSON feed, there is no Field name setting. Use the Property name text box to specify the name that will be referred to in the matching process (nesting will be taken into account).
For JSON feeds, the name of the property is case-sensitive. Specify property names in the same case as they are in a JSON feed.
To specify a nested field, use a slash (/
): for example, mainField/subField
.
Specify the full path to the element relative to the root element. You cannot use wildcard characters (the asterisk (*
) or question mark (?
)) to specify the path, only the root element (see above, "Adding a custom feed"). The path is case sensitive.
In the following example, if you specified root/element*
as the root element, then the full path to the elements relative to the root element is url
and ip
, not root/element1/url
or root/element2/ip
:
<root> <element1> <url>http</url> <ip>1</ip> </element1> </root> <root> <element2> <url>https</url> <ip>2</ip> </element2> </root> |
After a STIX feed is added, Kaspersky CyberTrace fully loads it for use.
In some cases (when a STIX feed is too large or the TAXII server used for downloading the feed is too slow, or both), it may take Kaspersky CyberTrace up to an hour to load a STIX feed.
When adding a custom or third-party feed, feeds updating can be performed. In this case, you will see a notification about it, and a new feed will not be added. We recommend that you wait awhile and then try again to add a feed.
Changing the settings of a custom or third-party feed
To change the settings of a custom or third-party feed, in the Filtering rules for feeds section, click the name of the feed that you want to modify and then click Edit.
Editing a custom or third-party feed
In the Edit custom feed window that opens, make any necessary changes and click Save.
You can change all the settings of a custom or third-party feed, except the feed type. For example, you cannot change a CSV feed to JSON.
Adding new fields to a custom or third-party feed
If a new field or fields have been added to your custom or third-party feed being used, and you want Kaspersky CyberTrace to start using these new fields, do the following:
If you do not specify any new fields for a feed, the feed will contain them, but they will not be displayed in the Available fields subsection and will not be used in the matching process.
For more information, see section "Filtering rules for feeds".