You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CloudAppSecurityDocs/tutorial-suspicious-activity.md
+13-12Lines changed: 13 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Detect suspicious user activity with UEBA
3
3
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
5
5
ms.topic: tutorial
6
6
---
7
7
@@ -24,13 +24,13 @@ Activities extracted from firewall and proxy traffic logs that are forwarded to
24
24
-**[Proxy log](proxy-intro-aad.md)**
25
25
Activities from your [conditional access app control apps](tutorial-proxy.md#phase-1-monitor-user-activities-for-anomalies).
26
26
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:
28
28
29
29
- Anomaly detection
30
30
- Cloud discovery anomaly detection
31
31
- Rule-based activity detection
32
32
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:
34
34
35
35
> [!div class="checklist"]
36
36
>
@@ -43,11 +43,12 @@ In this tutorial, you'll learn how to tune user activity detections to identify
43
43
44
44
## Phase 1: Configure IP address ranges
45
45
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.
47
47
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.
49
49
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.
@@ -62,9 +63,9 @@ Several built-in anomaly detection policies are available in Defender for Cloud
62
63
-**Impossible travel**
63
64
Activities from the same user in different locations within a period that is shorter than the expected travel time between the two locations.
64
65
-**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.
66
67
-**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.
68
69
-**Ransomware activity**
69
70
File uploads to the cloud that might be infected with ransomware.
70
71
-**Activity from suspicious IP addresses**
@@ -79,13 +80,13 @@ Detects multiple administrative activities in a single session with respect to t
79
80
For a full list of detections and what they do, see [Anomaly detection policies](anomaly-detection-policy.md#anomaly-detection-policies).
80
81
81
82
> [!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).
83
84
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.
85
86
86
87
1.**Scope policies to specific users or groups**
87
88
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:
89
90
90
91
-**Attack simulations**
91
92
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
[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.
131
132
132
133
1.**Tune activity volume**
133
134
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.
Copy file name to clipboardExpand all lines: defender-endpoint/defender-endpoint-false-positives-negatives.md
+13Lines changed: 13 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,6 +37,19 @@ search.appverid: met150
37
37
38
38
In endpoint protection solutions, a false positive is an entity, such as a file or a process that was detected and identified as malicious even though the entity isn't actually a threat. A false negative is an entity that wasn't detected as a threat, even though it actually is malicious. False positives/negatives can occur with any threat protection solution, including [Defender for Endpoint](microsoft-defender-endpoint.md).
39
39
40
+
If you have Microsoft Defender XDR, review the "Alerts sources" as described in [Investigate alerts in Microsoft Defender XDR](/defender-xdr/investigate-alerts?tabs=settings).
41
+
42
+
Continue here if the "Alert source" is "Microsoft Defender for Endpoint".
43
+
44
+
The next step is to review the “detection source”:
45
+
46
+
|Detection source| Information|
47
+
| -------- | -------- |
48
+
|EDR|The alert is related to Microsoft Defender for Endpoint – Endpoint Detection and Response <br/> • Solution: Submit the False Positive to [https://aka.ms/wdsi](/defender-endpoint/defender-endpoint-false-positives-negatives) <br/> • Work-around: Add an EDR exclusion|
49
+
|Antivirus|The alert relates to Microsoft Defender Antivirus in Active mode (Primary) where it will block. If Microsoft Defender Antivirus is in Passive mode, EDR in block mode might just detect.<br/> • Solution: Submit the False Positive to [https://aka.ms/wdsi](https://aka.ms/wdsi) <br/> • Work-around: Add [Indicators - File hash - allow ](/defender-endpoint/defender-endpoint-false-positives-negatives)or an [AV exclusion](/defender-endpoint/defender-endpoint-false-positives-negatives)|
50
+
| Custom TI| Custom indicators (Indicators - [file hash](/defender-endpoint/indicator-file) or [ip address or URL](/defender-endpoint/indicator-ip-domain) or [certificates](/defender-endpoint/indicator-certificates)) <br/> • Solution: How to[ manage indicators](/defender-endpoint/indicator-manage). <br/><br/> Or if you see CustomEnterpriseBlock, it could be <br/> <br/> 1) Automated Investigation and Response (AutoIR) – <br/> • Solution: Submit the False Positive to [https://aka.ms/wdsi](/defender-endpoint/defender-endpoint-false-positives-negatives) <br/> • Work-around: [Automation folder exclusions ](/defender-endpoint/manage-automation-folder-exclusions)<br/> 2) Custom detection rules deriving from Advanced Hunting (AH) – <br/> • Solution: [Manage existing custom detection rules ](/defender-xdr/custom-detection-rules)<br/> 3) EDR in block mode – <br/> • Solution: Submit the False Positive(s) to [https://aka.ms/wdsi](/defender-endpoint/defender-endpoint-false-positives-negatives)<br/> • Work-around: [Indicators – File hash – allow](/defender-endpoint/defender-endpoint-false-positives-negatives) or [AV exclusions](/defender-endpoint/defender-endpoint-false-positives-negatives)<br/> 4) Live Response – <br/> • Solution: Submit the False Positive(s) to [https://aka.ms/wdsi](/defender-endpoint/defender-endpoint-false-positives-negatives)<br/> • Work-around: [Indicators – File hash – allow](/defender-endpoint/defender-endpoint-false-positives-negatives) or [AV exclusions](/defender-endpoint/defender-endpoint-false-positives-negatives)<br/> 5) PUA protection – <br/> • Solution: Submit the False Positive(s) to [https://aka.ms/wdsi](/defender-endpoint/defender-endpoint-false-positives-negatives)<br/> • Work-around: [Indicators – File hash – allow](/defender-endpoint/defender-endpoint-false-positives-negatives) or [AV exclusions](/defender-endpoint/defender-endpoint-false-positives-negatives)|
51
+
| Smartscreen|[ Smartscreen](https://feedback.smartscreen.microsoft.com/smartscreenfaq.aspx)[report unsafe site](https://www.microsoft.com/en-us/wdsi/support/report-unsafe-site) or it could be related to a [Network Protection detection](https://www.microsoft.com/wdsi/support/report-exploit-guard)|
52
+
40
53
:::image type="content" source="media/false-positives-overview.png" alt-text="The definition of false positive and negatives in the Microsoft Defender portal" lightbox="media/false-positives-overview.png":::
41
54
42
55
Fortunately, steps can be taken to address and reduce these kinds of issues. If you're seeing false positives/negatives occurring with Defender for Endpoint, your security operations can take steps to address them by using the following process:
Copy file name to clipboardExpand all lines: defender-endpoint/detect-block-potentially-unwanted-apps-microsoft-defender-antivirus.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -131,7 +131,7 @@ For System Center 2012 Configuration Manager, see [How to Deploy Potentially Unw
131
131
132
132
### Use Group Policy to configure PUA protection
133
133
134
-
1. Download and install [Administrative Templates (.admx) for Windows 11 October 2021 Update (21H2)](https://www.microsoft.com/download/details.aspx?id=103507)
134
+
1. Download and install [the latest Administrative templates for Windows 11](https://www.bing.com/search?q=administrative+template+download+windows+11&FORM=R5FD)
135
135
136
136
2. On your Group Policy management computer, open the [Group Policy Management Console](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc731212(v=ws.11)).
Copy file name to clipboardExpand all lines: defender-endpoint/troubleshoot-onboarding.md
+4-7Lines changed: 4 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ ms.collection:
13
13
ms.topic: troubleshooting
14
14
ms.subservice: onboard
15
15
search.appverid: met150
16
-
ms.date: 11/04/2024
16
+
ms.date: 01/15/2025
17
17
---
18
18
19
19
# Troubleshoot Microsoft Defender for Endpoint onboarding issues
@@ -24,13 +24,13 @@ ms.date: 11/04/2024
24
24
**Applies to:**
25
25
26
26
-[Microsoft Defender for Endpoint Plan 1](microsoft-defender-endpoint.md)
27
+
27
28
-[Microsoft Defender for Endpoint Plan 2](microsoft-defender-endpoint.md)
29
+
28
30
- Windows Server 2012 R2
29
31
- Windows Server 2016
30
32
-[Microsoft Defender XDR](/defender-xdr)
31
33
32
-
> Want to experience Defender for Endpoint? [Sign up for a free trial.](https://signup.microsoft.com/create-account/signup?products=7f379fee-c4f9-4278-b0a1-e4c8c2fcdf7e&ru=https://aka.ms/MDEp2OpenTrial?ocid=docs-wdatp-pullalerts-abovefoldlink)
33
-
34
34
You might need to troubleshoot the Microsoft Defender for Endpoint onboarding process if you encounter issues.
35
35
This page provides detailed steps to troubleshoot onboarding issues that might occur when deploying with one of the deployment tools and common errors that might occur on the devices.
36
36
@@ -299,10 +299,7 @@ If the verification fails and your environment is using a proxy to connect to th
299
299
>
300
300
> If Microsoft Defender Antivirus is in passive mode, these drivers are set to manual (`0`).
301
301
302
-
## Troubleshoot onboarding issues
303
-
304
-
> [!NOTE]
305
-
> The following troubleshooting guidance is only applicable for Windows Server 2016 and earlier versions of Windows Server.
302
+
## Troubleshoot onboarding issues on Windows Server 2016 and earlier versions of Windows Server.
306
303
307
304
If you encounter issues while onboarding a server, go through the following verification steps to address possible issues.
Copy file name to clipboardExpand all lines: defender/threat-intelligence/analyst-insights.md
+1-4Lines changed: 1 addition & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ ms.author: aroland
6
6
manager: dolmont
7
7
ms.service: threat-intelligence
8
8
ms.topic: overview
9
-
ms.date: 11/18/2024
9
+
ms.date: 01/15/2025
10
10
ms.custom:
11
11
- template-overview
12
12
- cx-ti
@@ -15,9 +15,6 @@ ms.custom:
15
15
16
16
# Analyst insights
17
17
18
-
>[!IMPORTANT]
19
-
> On June 30, 2024, The Microsoft Defender Threat Intelligence (Defender TI) standalone portal (`https://ti.defender.microsoft.com`) was retired and is no longer accessible. Customers can continue using Defender TI in the [Microsoft Defender portal](https://aka.ms/mdti-intel-explorer) or with [Microsoft Security Copilot](security-copilot-and-defender-threat-intelligence.md). [Learn more](https://aka.ms/mdti-standaloneportal)
20
-
21
18
In Microsoft Defender Threat Intelligence (Defender TI), the **Analyst insights** section provides you with quick insights about an artifact that might help determine your next step in an investigation. This section lists any insights that apply to the artifact, and insights that don't apply for extra visibility.
22
19
23
20
In the following example, you can quickly determine that the IP address is routable, hosts a web server, and had an open port within the past five days. Furthermore, the system displays rules that weren't triggered, which can be equally helpful when kick starting an investigation.
Copy file name to clipboardExpand all lines: defender/threat-intelligence/data-sets.md
+1-4Lines changed: 1 addition & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ ms.author: aroland
6
6
manager: dolmont
7
7
ms.service: threat-intelligence
8
8
ms.topic: conceptual
9
-
ms.date: 11/18/2024
9
+
ms.date: 01/15/2025
10
10
ms.custom:
11
11
- template-concept
12
12
- cx-ti
@@ -15,9 +15,6 @@ ms.custom:
15
15
16
16
# Data sets
17
17
18
-
>[!IMPORTANT]
19
-
> On June 30, 2024, The Microsoft Defender Threat Intelligence (Defender TI) standalone portal (`https://ti.defender.microsoft.com`) was retired and is no longer accessible. Customers can continue using Defender TI in the [Microsoft Defender portal](https://aka.ms/mdti-intel-explorer) or with [Microsoft Security Copilot](security-copilot-and-defender-threat-intelligence.md). [Learn more](https://aka.ms/mdti-standaloneportal)
20
-
21
18
Microsoft centralizes numerous data sets into Microsoft Defender Threat Intelligence (Defender TI), making it easier for Microsoft's customers and community to conduct infrastructure analysis. Microsoft's primary focus is to provide as much data as possible about internet infrastructure to support various security use cases.
22
19
23
20
Microsoft collects, analyzes, and indexes internet data to help you:
Copy file name to clipboardExpand all lines: defender/threat-intelligence/gathering-threat-intelligence-and-infrastructure-chaining.md
+1-5Lines changed: 1 addition & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ ms.author: aroland
6
6
manager: dolmont
7
7
ms.service: threat-intelligence
8
8
ms.topic: tutorial
9
-
ms.date: 11/18/2024
9
+
ms.date: 01/15/2025
10
10
ms.custom:
11
11
- template-overview
12
12
- cx-ti
@@ -16,10 +16,6 @@ ms.custom:
16
16
17
17
# Tutorial: Gathering threat intelligence and infrastructure chaining
18
18
19
-
>[!IMPORTANT]
20
-
> On June 30, 2024, The Microsoft Defender Threat Intelligence (Defender TI) standalone portal (`https://ti.defender.microsoft.com`) was retired and is no longer accessible. Customers can continue using Defender TI in the [Microsoft Defender portal](https://aka.ms/mdti-intel-explorer) or with [Microsoft Security Copilot](security-copilot-and-defender-threat-intelligence.md). [Learn more](https://aka.ms/mdti-standaloneportal)
21
-
22
-
23
19
This tutorial walks you through how to perform several types of indicator searches and gather threat and adversary intelligence using Microsoft Defender Threat Intelligence (Defender TI) in the Microsoft Defender portal.
0 commit comments