Skip to content

Commit 6381a77

Browse files
Merge branch 'main' into patch-1
2 parents bf7e351 + 2f2a7db commit 6381a77

File tree

211 files changed

+2357
-2112
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

211 files changed

+2357
-2112
lines changed

ATPDocs/microsoft-365-security-center-mdi.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -106,7 +106,7 @@ The following table lists the changes in navigation between Microsoft Defender f
106106

107107
For more information, see:
108108

109-
- [Related videos for Microsoft Defender for Identity](https://www.microsoft.com/videoplayer/embed/RE4HcEU)
109+
- [Related videos for Microsoft Defender for Identity](https://learn-video.azurefd.net/vod/player?id=f4589332-7b78-40f0-b456-b896851a5aae)
110110
- [Microsoft Defender XDR](/defender-xdr/microsoft-365-defender)
111111
- [Microsoft Defender for Identity](/defender-for-identity/)
112112

CloudAppSecurityDocs/activity-filters-queries.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,8 +20,11 @@ Below is a list of the activity filters that can be applied. Most filters suppor
2020
- Activity objects – Search for the objects the activity was done on. This filter applies to files, folders, users, or app objects.
2121
- Activity object ID - the ID of the object (file, folder, user, or app ID).
2222

23-
- Item - Enables you to search by the name or ID of any activity object (for example, user names, files, parameters, sites). For the **Activity object Item** filter, you can select whether to filter for items that **Contain**, **Equal**, or **Starts with** the specific item.
23+
- Item - Enables you to search by the name or ID of any activity object (for example, user names, files, parameters, sites). For the **Activity object Item** filter, you can select whether to filter for items that **Contains**, **Equals**, or **Starts with** the specific item.
2424

25+
> [!NOTE]
26+
> Activity-Policy's **Activity object Item** filter supports the **Equals** operator only.
27+
2528
- Action type - Search for a more specific action performed in an app.
2629

2730
- Activity type - Search for the app activity.

CloudAppSecurityDocs/app-governance-app-policies-create.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ Use app governance to create OAuth policies for apps connected to Microsoft 365,
1717

1818
<br>
1919

20-
>[!VIDEO https://www.microsoft.com/videoplayer/embed/RE4YU37]
20+
>[!VIDEO https://learn-video.azurefd.net/vod/player?id=b10dbf02-9f56-4f37-8c68-8221be5b4aea]
2121
2222
<a name='create-oauth-app-policies-for-azure-ad'></a>
2323

CloudAppSecurityDocs/app-governance-manage-app-governance.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ Cyber attacks have become increasingly sophisticated in the ways they exploit th
1111

1212
To understand the potential risks and stop these types of attacks, you need to gain clear visibility into your organization’s app compliance posture. You need to be able to quickly identify when an app exhibits anomalous behaviors and respond when these behaviors present risks to your environment, data, and users. <br><br>
1313

14-
> [!VIDEO https://www.microsoft.com/en-us/videoplayer/embed/RE4S7sp]
14+
> [!VIDEO https://learn-video.azurefd.net/vod/player?id=ed7ad7f7-58dc-4a09-ace3-e1d6b8f55353]
1515
1616
## App governance features
1717

CloudAppSecurityDocs/app-governance-predefined-policies.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ description: Get started learning about predefined app policies.
1010
App governance contains a set of out of the box policies to detect anomalous app behaviors. These policies are activated by default, but you can deactivate them if you choose to.<br>
1111
<br>
1212

13-
> [!VIDEO https://www.microsoft.com/videoplayer/embed/RE4YpJN]
13+
> [!VIDEO https://learn-video.azurefd.net/vod/player?id=22872b35-18aa-424d-bec7-3f77869a5e47]
1414
1515
## Working with predefined policies
1616

CloudAppSecurityDocs/app-governance-secure-apps-app-hygiene-features.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ These features enable automatic control over these apps and provide extra app be
1717

1818
Watch this video for a brief explanation of these features:
1919

20-
> [!VIDEO https://www.microsoft.com/videoplayer/embed/RWWYEm]
20+
> [!VIDEO https://learn-video.azurefd.net/vod/player?id=d22073a4-555a-413a-8e01-fc0f42d97f6f]
2121
2222
## App insights
2323

CloudAppSecurityDocs/mde-investigation.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -110,7 +110,7 @@ Sometimes, access to an unsanctioned app isn't blocked, either because the endpo
110110
111111
## Related videos
112112
113-
- [Hunting with Microsoft Cloud App Security data](https://www.microsoft.com/videoplayer/embed/RWFISa)
113+
- [Hunting with Microsoft Cloud App Security data](https://learn-video.azurefd.net/vod/player?id=ffdedc73-6edf-45a9-8c90-566296e8d4ec)
114114
115115
- [Discover and block Shadow IT using Defender for Endpoint](https://www.youtube.com/watch?v=MsHkTOoqSQo)
116116

CloudAppSecurityDocs/microsoft-365-security-center-defender-cloud-apps.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -67,7 +67,7 @@ Learn how to protect your cloud apps in Microsoft Defender XDR:
6767

6868
**Protecting cloud apps in Microsoft Defender XDR**:<br>
6969

70-
> [!VIDEO https://www.microsoft.com/videoplayer/embed/RE59yVU title="Protecting cloud apps in Microsoft Defender XDR"]
70+
> [!VIDEO https://learn-video.azurefd.net/vod/player?id=a722f8cd-806b-40dd-ad93-139fa2b487b9 title="Protecting cloud apps in Microsoft Defender XDR"]
7171
7272
<br>
7373

CloudAppSecurityDocs/protect-workday.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -59,7 +59,7 @@ Watch our quick start video showing how to configure the prerequisites and perfo
5959
6060
<br />
6161

62-
> [!VIDEO https://www.microsoft.com/videoplayer/embed/RE4n1ZO]
62+
> [!VIDEO https://learn-video.azurefd.net/vod/player?id=abfc7df7-12cc-4c9b-bb81-cf00450f9b76]
6363
6464
### Prerequisites
6565

CloudAppSecurityDocs/tutorial-suspicious-activity.md

Lines changed: 13 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Detect suspicious user activity with UEBA
33
description: This tutorial describes the process for tuning user activity detections in Microsoft Defender for Cloud Apps.
4-
ms.date: 02/22/2023
4+
ms.date: 01/14/2025
55
ms.topic: tutorial
66
---
77

@@ -24,13 +24,13 @@ Activities extracted from firewall and proxy traffic logs that are forwarded to
2424
- **[Proxy log](proxy-intro-aad.md)**
2525
Activities from your [conditional access app control apps](tutorial-proxy.md#phase-1-monitor-user-activities-for-anomalies).
2626

27-
Next, you'll want to tune your policies. The following policies can be fine-tuned by setting filters, dynamic thresholds (UEBA) to help train their detection models, and suppressions to reduce common false positive detections:
27+
Next, you want to tune your policies. The following policies can be fine-tuned by setting filters, dynamic thresholds (UEBA) to help train their detection models, and suppressions to reduce common false positive detections:
2828

2929
- Anomaly detection
3030
- Cloud discovery anomaly detection
3131
- Rule-based activity detection
3232

33-
In this tutorial, you'll learn how to tune user activity detections to identify true compromises and reduce alert fatigue resulting from handling large volumes of false positive detections:
33+
In this tutorial, you learn how to tune user activity detections to identify true compromises and reduce alert fatigue resulting from handling large volumes of false positive detections:
3434

3535
> [!div class="checklist"]
3636
>
@@ -43,11 +43,12 @@ In this tutorial, you'll learn how to tune user activity detections to identify
4343
4444
## Phase 1: Configure IP address ranges
4545

46-
Before configuring individual policies, it advisable to configure IP ranges so that they are available to use in fine-tuning any type of suspicious user activity detection policies.
46+
Before configuring individual policies, it advisable to configure IP ranges so that they're available to use in fine-tuning any type of suspicious user activity detection policies.
4747

48-
Because IP address information is crucial for almost all investigations, [configuring known IP addresses](ip-tags.md) helps our machine learning algorithms identify known locations and consider them as part of the machine learning models. For example, adding the IP address range of your VPN will help the model to correctly classify this IP range and automatically exclude it from impossible travel detections because the VPN location doesn't represent the true location of that user.
48+
Because IP address information is crucial for almost all investigations, [configuring known IP addresses](ip-tags.md) helps our machine learning algorithms identify known locations and consider them as part of the machine learning models. For example, adding the IP address range of your VPN helps the model to correctly classify this IP range and automatically exclude it from impossible travel detections because the VPN location doesn't represent the true location of that user.
4949

50-
Note: Configured IP ranges are not limited to detections and are used throughout Defender for Cloud Apps in areas such as activities in the activity log, Conditional Access, etc. Keep this in mind when configuring the ranges. So, for example, identifying your physical office IP addresses allows you to customize the way logs and alerts are displayed and investigated.
50+
> [!NOTE]
51+
> Configured IP ranges aren't limited to detections and are used throughout Defender for Cloud Apps in areas such as activities in the activity log, Conditional Access, etc. Keep this in mind when configuring the ranges. So, for example, identifying your physical office IP addresses allows you to customize the way logs and alerts are displayed and investigated.
5152
5253
### Review out-of-the-box anomaly detection alerts
5354

@@ -62,9 +63,9 @@ Several built-in anomaly detection policies are available in Defender for Cloud
6263
- **Impossible travel**
6364
Activities from the same user in different locations within a period that is shorter than the expected travel time between the two locations.
6465
- **Activity from infrequent country**
65-
Activity from a location that was not recently or never visited by the user.
66+
Activity from a location that wasn't recently or never visited by the user.
6667
- **Malware detection**
67-
Scans files in your cloud apps and runs suspicious files through Microsoft's threat intelligence engine to determine whether they are associated with known malware.
68+
Scans files in your cloud apps and runs suspicious files through Microsoft's threat intelligence engine to determine whether they're associated with known malware.
6869
- **Ransomware activity**
6970
File uploads to the cloud that might be infected with ransomware.
7071
- **Activity from suspicious IP addresses**
@@ -79,13 +80,13 @@ Detects multiple administrative activities in a single session with respect to t
7980
For a full list of detections and what they do, see [Anomaly detection policies](anomaly-detection-policy.md#anomaly-detection-policies).
8081

8182
> [!NOTE]
82-
> While some of the anomaly detections are primarily focused on detecting problematic security scenarios, others can assist in identifying and investigating anomalous user behavior that may not necessarily indicate a compromise. For such detections we created another data type called "behaviors" which is available in the Microsoft Defender XDR advanced hunting experience. For more information see [Behaviors](behaviors.md).
83+
> While some of the anomaly detections are primarily focused on detecting problematic security scenarios, others can assist in identifying and investigating anomalous user behavior that may not necessarily indicate a compromise. For such detections we created another data type called "behaviors" which is available in the Microsoft Defender XDR advanced hunting experience. For more information, see [Behaviors](behaviors.md).
8384
84-
Once you are familiar with the policies, you should consider how you want to fine-tune them for your organization's specific requirements to better target activities that you may want to investigate further.
85+
Once you're familiar with the policies, you should consider how you want to fine-tune them for your organization's specific requirements to better target activities that you may want to investigate further.
8586

8687
1. **Scope policies to specific users or groups**
8788

88-
Scoping policies to specific users can help reduce noise from alerts that are not relevant to your organization. Each policy can be [configured to include or exclude specific users and groups](anomaly-detection-policy.md#scope-anomaly-detection-policies), such as in the following examples:
89+
Scoping policies to specific users can help reduce noise from alerts that aren't relevant to your organization. Each policy can be [configured to include or exclude specific users and groups](anomaly-detection-policy.md#scope-anomaly-detection-policies), such as in the following examples:
8990

9091
- **Attack simulations**
9192
Many organizations use a user or a group to constantly simulate attacks. Obviously, it doesn't make sense to constantly receive alerts from these users' activities. Therefore, you can configure your policies to exclude these users or groups. This also helps the machine learning models identify these users and fine-tune their dynamic thresholds accordingly.
@@ -127,7 +128,7 @@ To prevent alert fatigue, configure the sensitivity of alerts. You can use the s
127128

128129
## Phase 4: Tune rule-based detection (activity) policies
129130

130-
[Rule-based detection policies](user-activity-policies.md) give you the ability to complement anomaly detection policies with organization-specific requirements. We recommend creating rules-based policies using one of our Activity policy templates (go to **Control** > **Templates** and set the **Type** filter to **Activity policy**) and then [configuring them](activity-filters-queries.md) to detect behaviors that are not normal for your environment. For example, for some organization that don't have any presence in a particular country/region, it may make sense to create a policy that detects the anomalous activities from that country/region and alert on them. For others, who have large branches in that country/region, activities from that country/region would be normal and it wouldn't make sense to detect such activities.
131+
[Rule-based detection policies](user-activity-policies.md) give you the ability to complement anomaly detection policies with organization-specific requirements. We recommend creating rules-based policies using one of our Activity policy templates (go to **Control** > **Templates** and set the **Type** filter to **Activity policy**) and then [configuring them](activity-filters-queries.md) to detect behaviors that aren't normal for your environment. For example, for some organization that don't have any presence in a particular country/region, it may make sense to create a policy that detects the anomalous activities from that country/region and alert on them. For others, who have large branches in that country/region, activities from that country/region would be normal and it wouldn't make sense to detect such activities.
131132

132133
1. **Tune activity volume**
133134
Choose the volume of activity required before the detection raises an alert. Using our country/region example, if you have no presence in a country/region, even a single activity is significant and warrants an alert. However, a single sign-in failure could be human error and only of interest if there are many failures in a short period.

0 commit comments

Comments
 (0)