Skip to content

Commit 447e39a

Browse files
author
cabailey
committed
updates from Ram
1 parent 65899aa commit 447e39a

File tree

1 file changed

+20
-10
lines changed

1 file changed

+20
-10
lines changed

articles/sentinel/fusion.md

Lines changed: 20 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -44,17 +44,19 @@ Rule templates are not applicable for the advanced multistage attack detection.
4444

4545
Using advanced multistage attack detection, Azure Sentinel supports the following scenarios that combine anomaly events from Azure Active Directory Identity Protection and Microsoft Cloud App Security:
4646

47-
- [Impossible travel to atypical location](#impossible-travel-to-atypical-location)
48-
- [Sign-in activity for unfamiliar location](#sign-in-activity-for-unfamiliar-location)
49-
- [Sign-in activity from infected device](#sign-in-activity-from-infected-device)
50-
- [Sign-in activity from anonymous IP address](#sign-in-activity-from-anonymous-ip-address)
51-
- [Sign-in activity from user with leaked credentials](#sign-in-activity-from-user-with-leaked-credentials)
47+
- [Impossible travel to atypical location followed by anomalous Office 365 activity](#impossible-travel-to-atypical-location)
48+
- [Sign-in activity for unfamiliar location followed by anomalous Office 365 activity](#sign-in-activity-for-unfamiliar-location)
49+
- [Sign-in activity from infected device followed by anomalous Office 365 activity](#sign-in-activity-from-infected-device)
50+
- [Sign-in activity from anonymous IP address followed by anomalous Office 365 activity](#sign-in-activity-from-anonymous-ip-address)
51+
- [Sign-in activity from user with leaked credentials followed by anomalous Office 365 activity](#sign-in-activity-from-user-with-leaked-credentials)
5252

5353
You must have the [Azure AD Identity Protection data connector](connect-azure-ad-identity-protection.md) and the [Cloud App Security](connect-cloud-app-security.md) connectors configured.
5454

5555
In the descriptions that follow, Azure Sentinel will display the actual value from your data that is represented on this page as variables in brackets. For example, the actual display name of an account rather than \<*account name*>, and the actual number rather than \<*number*>.
5656

57-
### Impossible travel to atypical location
57+
### Impossible travel to atypical location followed by anomalous Office 365 activity
58+
59+
There are seven possible Azure Sentinel incidents that combine impossible travel to atypical location alerts from Azure Identity Protection and anomalous Office 365 alerts generated by Microsoft Cloud App Security.
5860

5961
- **Impossible travel to atypical locations leading to Office 365 mailbox exfiltration**
6062

@@ -101,7 +103,9 @@ In the descriptions that follow, Azure Sentinel will display the actual value fr
101103
This activity pattern is indicative of a potential ransomware attack.
102104

103105

104-
### Sign-in activity for unfamiliar location
106+
### Sign-in activity for unfamiliar location followed by anomalous Office 365 activity
107+
108+
There are seven possible Azure Sentinel incidents that combine sign-in activity for unfamiliar location alerts from Azure Identity Protection and anomalous Office 365 alerts generated by Microsoft Cloud App Security.
105109

106110
- **Sign-in event from an unfamiliar location leading to Exchange Online mailbox exfiltration**
107111

@@ -147,7 +151,9 @@ In the descriptions that follow, Azure Sentinel will display the actual value fr
147151

148152
This activity pattern is indicative of a potential ransomware attack.
149153

150-
### Sign-in activity from infected device
154+
### Sign-in activity from infected device followed by anomalous Office 365 activity
155+
156+
There are seven possible Azure Sentinel incidents that combine sign-in activity from infected device alerts from Azure Identity Protection and anomalous Office 365 alerts generated by Microsoft Cloud App Security.
151157

152158
- **Sign-in event from an infected device leading to Office 365 mailbox exfiltration**
153159

@@ -193,7 +199,9 @@ In the descriptions that follow, Azure Sentinel will display the actual value fr
193199

194200
This activity pattern is indicative of a potential ransomware attack.
195201

196-
### Sign-in activity from anonymous IP address
202+
### Sign-in activity from anonymous IP address followed by anomalous Office 365 activity
203+
204+
There are seven possible Azure Sentinel incidents that combine sign-in activity from anonymous IP address alerts from Azure Identity Protection and anomalous Office 365 alerts generated by Microsoft Cloud App Security.
197205

198206
- **Sign-in event from an anonymous IP address leading to Office 365 mailbox exfiltration**
199207

@@ -239,7 +247,9 @@ In the descriptions that follow, Azure Sentinel will display the actual value fr
239247

240248
This activity pattern is indicative of a potential ransomware attack.
241249

242-
### Sign-in activity from user with leaked credentials
250+
### Sign-in activity from user with leaked credentials followed by anomalous Office 365 activity
251+
252+
There are seven possible Azure Sentinel incidents that combine sign-in activity from user with leaked credentials alerts from Azure Identity Protection and anomalous Office 365 alerts generated by Microsoft Cloud App Security.
243253

244254
- **Sign-in event from User with leaked credentials leading to Office 365 mailbox exfiltration**
245255

0 commit comments

Comments
 (0)