Skip to content

Commit f89f4e9

Browse files
Merge pull request #276003 from batamig/may-fixes-2
Sentinel May automation fixes
2 parents 7083859 + c7bb577 commit f89f4e9

File tree

1 file changed

+5
-2
lines changed

1 file changed

+5
-2
lines changed

articles/sentinel/automate-incident-handling-with-automation-rules.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -99,13 +99,16 @@ When an automation rule is triggered, it checks the triggering incident or alert
9999

100100
For rules defined using the trigger **When an incident is created**, you can define conditions that check the **current state** of the values of a given list of incident properties, using one or more of the following operators:
101101

102-
An incident property's value
103102
- **equals** or **does not equal** the value defined in the condition.
104103
- **contains** or **does not contain** the value defined in the condition.
105104
- **starts with** or **does not start with** the value defined in the condition.
106105
- **ends with** or **does not end with** the value defined in the condition.
107106

108-
The **current state** in this context refers to the moment the condition is evaluated - that is, the moment the automation rule runs. If more than one automation rule is defined to run in response to the creation of this incident, then changes made to the incident by an earlier-run automation rule are considered the current state for later-run rules.
107+
For example, if you define **Analytic rule name** as **Contains == Brute force attack against a Cloud PC**, an analytic rule with the **Brute force attack against Azure portal** doesn't meet the condition. However, if you define **Analytic rule name** as **Does not contain == User credentials**, then both the **Brute force attack against a Cloud PC** and **Brute force against Azure portal** analytics rules meet the condition.
108+
109+
> [!NOTE]
110+
> The **current state** in this context refers to the moment the condition is evaluated - that is, the moment the automation rule runs. If more than one automation rule is defined to run in response to the creation of this incident, then changes made to the incident by an earlier-run automation rule are considered the current state for later-run rules.
111+
>
109112
110113
#### Incident update trigger
111114

0 commit comments

Comments
 (0)