Skip to content

Commit aae07a6

Browse files
mergify[bot]benironsidejoepeeplesnastasha-solomon
authored
[8.5] [DOCS] New exceptions UI/UX (backport #2546) (#2574)
Co-authored-by: Benjamin Ironside Goldstein <91905639+benironside@users.noreply.github.com> Co-authored-by: Joe Peeples <joe.peeples@elastic.co> Co-authored-by: nastasha-solomon <79124755+nastasha-solomon@users.noreply.github.com>
1 parent 3600afd commit aae07a6

File tree

3 files changed

+18
-14
lines changed

3 files changed

+18
-14
lines changed

docs/detections/detections-ui-exceptions.asciidoc

Lines changed: 18 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ To prevent the creation of unwanted alerts, you can add exceptions to any rule.
66
alerts are not generated. They provide a convenient way of allowing trusted
77
processes and network activity to function without producing unnecessary noise.
88

9-
You can add multiple exceptions to one rule.
9+
You can add multiple exceptions to a single rule. An exception can also apply to multiple rules.
1010

1111
In addition to defining exception queries for source event values, you can use rule
1212
exceptions with value lists. Value lists are lists of items with
@@ -102,11 +102,10 @@ specific event in the sequence, update the rule's EQL statement. For example:
102102
* To add an exception from the rule details page:
103103
.. Go to the rule details page of the rule to which you want to add an
104104
exception (*Manage* -> *Rules* -> *_<Rule name>_*).
105-
.. Scroll down below the rule details and select the *Exceptions* tab.
105+
.. Scroll down the rule details page, select the *Rule exceptions* tab, then click *Add rule exception*.
106106
+
107107
[role="screenshot"]
108-
image::images/exception-histogram.png[Detail of Exceptions tab, 75%]
109-
.. Click *Add new exception* -> *Add rule exception*.
108+
image::images/rule-exception-tab.png[Detail of rule exceptions tab]
110109

111110
* To add an exception from the Alerts table:
112111
.. Go to *Alerts*.
@@ -166,16 +165,9 @@ Like detection rule exceptions, you can add Endpoint agent exceptions either by
166165

167166
You can also add Endpoint exceptions to rules that are associated with {elastic-endpoint} rule exceptions. To associate rules, when creating or editing a rule, select the <<rule-ui-advanced-params, *{elastic-endpoint} exceptions*>> option.
168167

169-
[IMPORTANT]
170-
=====
171-
When you add an exception to the
172-
<<endpoint-rule-exceptions, Elastic Endpoint Security>> rule, you can select to
173-
add the exception to the endpoint. When selected, the exception is added to
168+
Endpoint exceptions are added to
174169
both the detection rule *and* the {elastic-endpoint} agent on your hosts.
175170

176-
{ref}/binary.html[Binary fields] are not supported in detection rule exceptions.
177-
=====
178-
179171
[IMPORTANT]
180172
=============
181173
Exceptions added to the Elastic Endpoint Security rule affect all alerts sent
@@ -185,13 +177,17 @@ alerts.
185177
Additionally, to add an Endpoint exception to the Elastic Endpoint Security rule, there must be at least one Endpoint Security alert generated in the system. For non-production use, if no alerts exist, you can trigger a test alert using malware emulation techniques or tools such as the Anti Malware Testfile from the https://www.eicar.org/[European Institute for Computer Anti-Virus Research (EICAR)].
186178
=============
187179

180+
[IMPORTANT]
181+
=====
182+
{ref}/binary.html[Binary fields] are not supported in detection rule exceptions.
183+
=====
184+
188185
. Do one of the following:
189186
+
190187
--
191188
* To add an Endpoint exception from the rule details page:
192189
.. Go to the rule details page (*Manage* -> *Rules*), and then search for and select the Elastic *Endpoint Security* rule.
193-
.. Scroll down to the *Trend* histogram and select the *Exceptions* tab.
194-
.. Click *Add new exception* -> *Add Endpoint exception*.
190+
.. Scroll down the rule details page, select the *Endpoint exceptions* tab, then click *Add endpoint exception*.
195191
* To add an Endpoint exception from the Alerts table:
196192
.. Go to *Alerts*.
197193
.. Scroll down to the Alerts table, and from an {elastic-endpoint}
@@ -278,6 +274,14 @@ Creates an exception that excludes all LFC-signed trusted processes:
278274
[role="screenshot"]
279275
image::images/nested-exp.png[]
280276

277+
[float]
278+
[[rules-using-same-exception]]
279+
=== Find rules using the same exception
280+
To find out if an exception is used by other rules, select the *Rule exceptions* or *Endpoint exceptions* tab, navigate to an exception list item, then click *Affects _X_ rules*.
281+
282+
[role="screenshot"]
283+
image::images/exception-affects-multiple-rules.png[]
284+
281285
[float]
282286
[[manage-exceptions]]
283287
=== View and manage exception lists
259 KB
Loading
98.4 KB
Loading

0 commit comments

Comments
 (0)