Add custom exceptions to enabled detection models/filters to exclude specified highlighted objects or events from future detections.
Procedure
- Go to .
- Click + Add.
- Specify the general settings (Exception name and Description).
- Specify the Field and Values target settings.

Note
-
You can specify up to 50 values. Each value cannot exceed 128 characters.
-
The values must match the format of the selected field. For example, if the field is endpointGUID, you must specify a GUID.
-
If you need to define multiple targets, click +Add Target to define another target.
-
- Select the event source Event type, Event ID, and Event sub-ID.

Note
Each event type is associated with one type of activity data that specific data sources collect. For example, the ENDPOINT_ACTIVITY_DATA event type is associated with endpoint activity data that endpoint sensors collect.For more information about data sources, see Data sources. - Specify the match criteria (Field type, Field, and Values). If you need to add multiple criteria, click Add criteria.
- To use regex in criteria values, select Allow regex in criteria values.

Note
Standard regex syntax is supported:-
.*: Match zero or more characters
-
.+: Match one or more characters
-
^: Start of string
-
$: End of string
-
\: Escape charactersUse a backslash (\) if the value contains any of the following characters and you want to match the characters exactly: \ { } ( ) [ ] . + * ? ^ $ |
Example 1: To match all .exe files inC:\Users\Temp, type C:\\Users\\Temp\\.*\.exe.Example 2: To match all URLs starting with https://example.com/, type https://example\.com/.*. -
- Click Add.
