search-identifier
elements define the specific patterns Trend Vision One uses to detect events. A filter
can contain up to 19 search-identifier
elements.Components
{search-identifier key}: {List or object} {List or object} .... {List or object}
The following table outlines the components of search-identifier elements:
Component
|
Description
|
Search-identifier key
|
Key of the search-identifier.
|
List
|
List of strings that the filter attempts to localize in the detection logs. All elements
in a list are matched using the "OR" operator.
Use the field names defined in the search method data sources to create lists.
eventSub: eventSubId: - TELEMETRY_CONNECTION_CONNECT_OUTBOUND - TELEMETRY_CONNECTION_CONNECT_INBOUND |
Object |
Objects consist of key-value pairs. All elements in an object are matched using the
"AND" operator.
Use the field names defined in the search method data sources to create objects.
detection: selection: dpt: - 5650 - 5655 processCmd: '*-run_agent*' condition: selection |
Guidelines
The following table outlines the guidelines to create search-identifier elements.
Section
|
Description
|
||
Strings
|
|
||
Wildcards
|
|
||
Numeric values
|
Numeric values do not require apostrophes.
|
||
Value modifiers
|
Value modifiers are not allowed in custom filters.
|
Special Field Values
-
Avoid using the following special field values:
-
Empty values (
''
,null
) -
Single character wildcards (
?
)
-
-
For the
eventId
andeventSubId
fields, use the data field mapping value instead of the numeric value.eventSubId: TELEMETRY_PROCESS_OPEN # Instead of eventSubId: 1