Add a Suppression Rule
- Click 'Security' > 'Endpoint Security' > 'Alerts' > 'Suppression Rules' and click 'Add Suppression Rule', or expand an 'EXDR' alert on 'Alert Search' and click 'Add Suppression Rule' in its detail panel.
A suppression rule names a set of events and tells the platform not to raise alerts for them. The form asks for a name, an optional description and a query that picks out the events. The query is typed in a conditions box with a row of operator buttons and a panel of the field names you can use.
You can name the rule, describe it, build the query from the fields and operators on screen, read the query syntax help, clear what you have built, and add the rule.

The warning at the top
A strip across the top of the form reads: 'Please beware of that suppression rules with fewer conditions result in broader range of suppressed alerts. Try to suppress alerts for specific conditions.' In other words, the fewer tests your query makes, the more alerts it silences.
The fields
| Field | Control | Description |
| Name: | Text box | The name of the rule, shown in the 'Rule Name' column of the list. Required — a red asterisk follows the label. Empty by default, with no placeholder. |
| Description: | Text area | A description of the rule, shown in the 'Description' column of the list. Optional. The corner of the box can be dragged to make it taller. |
| Do not raise alerts for the following conditions: | Query box | The query that picks the events to suppress. It shows 'Please choose at least one condition' until you put something in it. Required. |
The buttons and links
| Control | Description |
| Clear Fields | A link at the right of the conditions caption. Empties the query box. |
| AND, OR, NOR | Three blue pills under the query box. Click one to put that logical operator into the query at the cursor. |
| Equals (=), Not Equals (!=), Contains (*), Not Contains (!*), Starts With (**), Ends With (:*), Is Empty (@), Is Not Empty (!@) | Eight blue pills on the next line. Click one to put that comparison into the query. Each pill also carries its plain name as a tooltip — 'Equals', 'Not Equals', 'Contains', 'Not Contains', 'Starts With', 'Ends With', 'Is Empty', 'Is Not Empty'. |
| Query Builder Help | A link at the right of the 'Available Fields' caption. Opens the syntax reference. |
| + Add Rule | The button at the bottom right. Creates the rule. It is faded and unavailable until the form is complete. |
| (the cross) | The cross at the top right of the title bar. Closes the form without creating anything. There is no 'Cancel' button on this form. |
The Available Fields panel
Under the caption 'Available Fields' sit two columns listing every field you may use in the query, each with a sample value. Each column scrolls on its own. Click a field name to put it into the query; click a value to put the field and the value into the query together.
| Field | Field |
| action | file_hash |
| adaptive_event_type | file_name |
| alert_name | file_path |
| alert_time | file_size |
| base_event_type | network_destination_ip |
| component | network_destination_port |
| device_name | network_source_ip |
| event_group | network_source_port |
| event_time | network_transfer_protocol |
| parent_process_hash | parent_process_creation_time |
| parent_process_instance_id | parent_process_user_domain |
| parent_process_logged_on_user | parent_process_user_name |
| parent_process_path | parent_process_verdict |
| process_creation_time | registry_key_path |
| process_hash | registry_value_data |
| process_path | registry_value_name |
| process_pid | |
| process_verdict |
Opened from the 'Suppression Rules' tab, the panel shows the empty defaults for each field — an empty string, 'Unknown', '--', 0 or '0.0.0.0'.

Add a rule from the Suppression Rules tab
- Choose the customer in the 'Customer' drop-down at the top right of the tab.
- Click 'Add Suppression Rule' beside the 'Alert Suppression Rules' title. The form opens.
- Type a name in 'Name:'.
- Type a description in 'Description:' if you want one.
- Click in the conditions box and build the query: click a field name in 'Available Fields', click the operator pill you want, then type the value. Use 'AND', 'OR' and 'NOR' to join tests.
- Click '+ Add Rule'. The rule is added to the list for that customer.
Add a rule from an alert
Starting from an alert saves you looking the values up, because the 'Available Fields' panel then holds that alert's own values instead of the empty defaults.
- Open 'Alert Search' and expand an 'EXDR' alert row.
- Click 'Add Suppression Rule' at the top right of the detail panel. The same form opens.
- Read the alert's values in 'Available Fields' — for example '"component" : "EXDR"', '"device_name" : "win11"', '"adaptive_event_type" : "Add Scheduled Task"'.
- Click the values you want to match on; each click copies the field and its value into the query.
- Fill in 'Name:', then click '+ Add Rule'.

Close the form without adding a rule
- Click the cross at the top right of the 'Add Alert Suppression Rule' title bar.
- The form closes and nothing is saved. Use 'Clear Fields' first if you only want to empty the query and start again.
Note: the form is the same whichever button opens it, and the rule it creates always belongs to the customer selected at the top right of the tab.
Note: the operator pills and the help text spell two of the operators differently — the pills read 'Contains (*)' and 'Starts With (**)', while the syntax help gives '~' for Contains and '*' for Starts With. Follow the syntax help when you type a query by hand, and the pills when you build it by clicking.
