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: ATPDocs/investigate-assets.md
+3-4Lines changed: 3 additions & 4 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: Investigate assets
3
3
description: This article explains how to investigate suspicious users, computers, and devices with Microsoft Defender for Identity.
4
-
ms.date: 01/17/2024
4
+
ms.date: 07/01/2025
5
5
ms.topic: how-to
6
6
ms.reviewer: LiorShapiraa
7
7
---
@@ -46,8 +46,7 @@ Find identity information in the following Microsoft Defender XDR areas:
46
46
47
47
For example, the following image shows the details on an identity details page:
48
48
49
-

50
-
49
+
:::image type="content" source="media/investigate-assets/investigate-assets.png" alt-text="Screenshot that shows a specific user's page in the Microsoft Defender portal." lightbox="media/investigate-assets/investigate-assets.png":::
51
50
52
51
53
52
### Identity details
@@ -57,7 +56,7 @@ When you investigate a specific identity, you'll see the following details on an
57
56
58
57
|Identity details page area |Description |
59
58
|---------|---------|
60
-
|[Overview tab](/microsoft-365/security/defender/investigate-users#overview)| General identity data, such as the Microsoft Entra identity risk level, the number of devices the user is signed in to, when the user was first and last seen, the user's accounts and more important information. <br><br>Use the **Overview** tab to also view graphs for incidents and alerts, the investigation priority score, an organizational tree, entity tags, and a scored activity timeline. |
59
+
|[Overview tab](/microsoft-365/security/defender/investigate-users#overview)| General identity data, such as the Microsoft Entra identity risk level, the number of devices the user is signed in to, when the user was first and last seen, the user's accounts and more important information. <br><br>Use the **Overview** tab to also view graphs for incidents and alerts, and an organizational tree, entity tags. |
61
60
|[Incidents and alerts](/microsoft-365/security/defender/investigate-users#incidents-and-alerts)| Lists active incidents and alerts involving the user from the last 180 days, including details like alert severity and the time the alert was generated. |
62
61
|[Observed in organization](/microsoft-365/security/defender/investigate-users#observed-in-organization)| Includes the following sub-areas: <br>- **Devices**: The devices that the identity signed in to, including most and least used in the last 180 days. <br>- **Locations**: The identity's observed locations over the last 30 days. <br>- **Groups**: All observed on-premises groups for the identity. <br> - **Lateral movement paths** - all profiled lateral movement paths from the on-premises environment. |
63
62
|[Identity timeline](/microsoft-365/security/defender/investigate-users#timeline)| The timeline represents activities and alerts observed from a user's identity from the last 180 days, unifying identity entries across Microsoft Defender for Identity, Microsoft Defender for Cloud Apps, and Microsoft Defender for Endpoint. <br><br>Use the timeline to focus on activities a user performed or were performed on them in specific timeframes. Select the default **30 days** to change the time range to another built-in value, or to a custom range. |
- Direct integrations with other services like Microsoft Defender for Cloud Apps and Microsoft Entra for a hybrid view of what's taking place in both on-premises and hybrid environments
Copy file name to clipboardExpand all lines: ATPDocs/ops-guide/ops-guide-daily.md
-29Lines changed: 0 additions & 29 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -52,35 +52,6 @@ For more information, see [Work with Defender for Identity's ITDR dashboard (Pre
52
52
53
53
1. When the incident is remediated, resolve it to resolve all linked and related active alerts and set a classification.
54
54
55
-
## Investigate users with a high investigation score
56
-
57
-
**Where**: In Microsoft Defender XDR and in Microsoft Entra.
58
-
59
-
In Microsoft Defender XDR:
60
-
61
-
1. Check the **Users at risk** widget on the **Home** page or the **Entra ID users at risk** on the **Identities > Dashboard** page.
62
-
63
-
1. If you have users listed at *High risk*:
64
-
65
-
- Select **View all users** to review high risk identities in Microsoft Entra.
66
-
- Go to the **Identities** page and sort the grid to view users with high **Investigation priority** scores at the top. Select an identity to view the identity details page, including more details in the **Investigation priority** widget.
67
-
68
-
The investigation priority widget includes the calculated investigation priority score breakdown and a two-week trend for an identity, including whether the identity score is on the high percentile for that tenant.
69
-
70
-
Find more identity-related information on:
71
-
72
-
- Individual alert or incident details pages
73
-
- Device details pages
74
-
- Advanced hunting queries
75
-
- The Action center page
76
-
77
-
**Persona**: SOC analysts
78
-
79
-
For more information, see:
80
-
81
-
-[Investigate users in Microsoft Defender XDR](/microsoft-365/security/defender/investigate-users)
82
-
-[Investigate assets](../investigate-assets.md)
83
-
-[Work with Defender for Identity's ITDR dashboard (Preview)](../dashboard.md)
Copy file name to clipboardExpand all lines: ATPDocs/technical-faq.yml
+1-3Lines changed: 1 addition & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -68,8 +68,6 @@ sections:
68
68
69
69
- **[Microsoft Secure Score posture assessments](/defender-for-identity/security-assessment)**: Identifies common misconfigurations and exploitable components and provides remediation paths to reduce the attack surface.
70
70
71
-
- **[UEBA capabilities](/cloud-app-security/tutorial-ueba)**: Insights into individual user risk through user investigation priority scoring. The score can assist SecOps in their investigations and help analysts understand unusual activities for the user and the organization.
72
-
73
71
- **Native integrations**: Integrates with Microsoft Defender for Cloud Apps and Microsoft Entra ID Protection to provide a hybrid view of what's taking place in both on-premises and hybrid environments.
74
72
75
73
- **Contributes to Microsoft Defender XDR**: Contributes alert and threat data to Microsoft Defender XDR. Microsoft Defender XDR uses the Microsoft 365 security portfolio (identities, endpoints, data, and applications) to automatically analyze cross-domain threat data, building a complete picture of each attack in a single dashboard.
@@ -150,7 +148,7 @@ sections:
150
148
151
149
- question: Does Microsoft Defender for Identity require synchronizing users to Microsoft Entra ID?
152
150
answer: |
153
-
Microsoft Defender for Identity provides security value for all Active Directory accounts including those that are not synced to Microsoft Entra ID. User accounts that are synced to Microsoft Entra ID will also benefit of security value provided by Microsoft Entra ID (based on license level) and of Investigation Priority Scoring.
151
+
Microsoft Defender for Identity provides security value for all Active Directory accounts including those that are not synced to Microsoft Entra ID. User accounts that are synced to Microsoft Entra ID benefit from the security value provided by Microsoft Entra ID based on license level. For more detailse see: [Identity inventory](/defender-for-identity/identity-inventory).
Copy file name to clipboardExpand all lines: CloudAppSecurityDocs/posture-overview.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
@@ -45,7 +45,7 @@ To ensure that your application connector is set to show data in Microsoft Secur
45
45
> [!NOTE]
46
46
> If you have multiple instances of the same app, you can send security recommendations for each instance separately. Security recommendations for the selected instance are added to Microsoft Security Exposure Management in addition to the current recommendations.
47
47
48
-
Security recommendations appear automatically in Microsoft Security Exposure Management. Recommendations are based on Microsoft benchmarks, and they might take up to 24 hours to update.
48
+
Security recommendations appear automatically in Microsoft Security Exposure Management. Recommendations are based on Microsoft benchmarks, and they might take time to update.
49
49
50
50
In [Microsoft Secure Score](/microsoft-365/security/defender/microsoft-secure-score), filter the **Recommended actions** tab by product to view any recommended actions. If you have multiple instances of an app, you can choose to filter recommendations from specific instances only. The following example shows options for filtering specific instances.
Copy file name to clipboardExpand all lines: defender-endpoint/linux-support-connectivity.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
@@ -56,7 +56,7 @@ Testing connection with https://uk-v20.events.data.microsoft.com/ping ... [OK]
56
56
Testing connection with https://v20.events.data.microsoft.com/ping ... [OK]
57
57
```
58
58
59
-
If the connectivity test fails, check if the device has Internet access. Also check to see if network connections are blocked by a proxy or firewall. For more information, see [Verify that devices can connect to Defender for Endpoint cloud services](mde-linux-prerequisites.md#verify-that-devices-can-connect-to-defender-for-endpoint-cloud-services).
59
+
If the connectivity test fails, check if the device has Internet access. Also check to see if network connections are blocked by a proxy or firewall. For more information, see [Verify that devices can connect to Defender for Endpoint cloud services](mde-linux-prerequisites.md#verify-if-devices-can-connect-to-defender-for-endpoint-cloud-services).
60
60
61
61
Failures with curl error 35 or 60, indicate certificate pinning rejection. Check to see if the connection is under SSL or HTTPS inspection. If so, add Microsoft Defender for Endpoint to the allowlist.
Copy file name to clipboardExpand all lines: defender-endpoint/mde-linux-deployment-on-sap.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
@@ -65,7 +65,7 @@ Here are some important point about SAP applications on Linux Server:
65
65
66
66
- Microsoft Defender for Endpoint [Build: 101.24082.0004 | Release version: 30.124082.0004.0](/defender-endpoint/linux-whatsnew#oct-2024-build-101240820004--release-version-3012408200040) or later must be deployed.
67
67
- Microsoft Defender for Endpoint on Linux supports [Linux releases](/defender-endpoint/mde-linux-prerequisites) used by SAP applications.
68
-
- Microsoft Defender for Endpoint on Linux requires connectivity to specific Internet endpoints from VMs to update antivirus definitions. For more information, see [Verify that devices can connect to Defender for Endpoint cloud services](mde-linux-prerequisites.md#verify-that-devices-can-connect-to-defender-for-endpoint-cloud-services).
68
+
- Microsoft Defender for Endpoint on Linux requires connectivity to specific Internet endpoints from VMs to update antivirus definitions. For more information, see [Verify that devices can connect to Defender for Endpoint cloud services](mde-linux-prerequisites.md#verify-if-devices-can-connect-to-defender-for-endpoint-cloud-services).
69
69
- Microsoft Defender for Endpoint on Linux requires some `crontab` (or other task scheduler) entries to schedule scans, log rotation, and Microsoft Defender for Endpoint updates. Enterprise security teams normally manage these entries. For more information, see [How to schedule an update for Microsoft Defender for Endpoint on Linux](linux-update-mde-linux.md).
70
70
71
71
As of December 2024, Defender for Endpoint on Linux can safely be configured with real-time protection enabled.
Copy file name to clipboardExpand all lines: defender-endpoint/mde-linux-prerequisites.md
+2-3Lines changed: 2 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -92,7 +92,7 @@ The following Linux server distributions and x64 (AMD64/EM64T) versions are supp
92
92
- Oracle Linux 9.x
93
93
- Amazon Linux 2
94
94
- Amazon Linux 2023
95
-
- Fedora 33-38
95
+
- Fedora 33-42
96
96
- Rocky 8.7 and higher
97
97
- Rocky 9.2 and higher
98
98
- Alma 8.4 and higher
@@ -123,7 +123,6 @@ The following Linux server distributions and x64 (AMD64/EM64T) versions are supp
123
123
> Running Defender for Endpoint on Linux with other fanotify-based security solutions isn't supported. It can lead to unpredictable results, including hanging the operating system.
124
124
> If there are any other applications on the system that use fanotify in blocking mode, applications are listed in the conflicting_applications field of the mdatp health command output.
125
125
> The Linux FAPolicyD feature uses fanotify in blocking mode, and is therefore unsupported when running Defender for Endpoint in active mode. You can still safely take advantage of Defender for Endpoint on Linux EDR functionality after configuring the antivirus functionality Real Time Protection Enabled to passive mode. See [Enforcement level for Microsoft Defender Antivirus](/defender-endpoint/linux-preferences#enforcement-level-for-microsoft-defender-antivirus).
126
-
127
126
## Supported filesystems for real-time protection and quick, full, and custom scans
128
127
129
128
|Real-time protection and quick/full scans|Custom scans|
@@ -149,7 +148,7 @@ The following Linux server distributions and x64 (AMD64/EM64T) versions are supp
149
148
> NFS v3 mount points to be scanned thoroughly and are required to set the `no_root_squash` export option on these mount points.
150
149
> Without this option, scanning NFS v3 can potentially fail due to lack of permissions.
151
150
152
-
## Verify that devices can connect to Defender for Endpoint cloud services
151
+
## Verify if devices can connect to Defender for Endpoint cloud services
153
152
154
153
1. Prepare your environment, as described in Step 1 of the following article [Configure your network environment to ensure connectivity with Defender for Endpoint service](/defender-endpoint/configure-environment).
Copy file name to clipboardExpand all lines: defender-endpoint/switch-to-mde-phase-1.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
@@ -111,7 +111,7 @@ To enable communication between your devices and Defender for Endpoint, you migh
111
111
|---|---|---|
112
112
|[Defender for Endpoint Plan 1](defender-endpoint-plan-1.md)|[Windows 11](/windows/whats-new/windows-11-overview)<br/>[Windows 10](/windows/release-health/release-information)<br/>Windows Server 2025<br/> [Windows Server 2022](/windows-server/get-started/whats-new-in-windows-server-2022) <br/> [Windows Server 2019](/windows/release-health/status-windows-10-1809-and-windows-server-2019) <br/> [Windows Server 1803, or later](/windows-server/get-started/whats-new-in-windows-server-1803) <br/> [Windows Server 2016](/windows-server/get-started/whats-new-in-windows-server-2016)\*<br/>[Windows Server 2012 R2](/windows/release-health/status-windows-8.1-and-windows-server-2012-r2)\*|[Configure and validate Microsoft Defender Antivirus network connections](configure-network-connections-microsoft-defender-antivirus.md)|
113
113
|[Defender for Endpoint Plan 1](defender-endpoint-plan-1.md)|macOS (see [System requirements](microsoft-defender-endpoint-mac-prerequisites.md))|[Defender for Endpoint on macOS: Network connections](microsoft-defender-endpoint-mac-prerequisites.md#network-connectivity)|
114
-
|[Defender for Endpoint Plan 1](defender-endpoint-plan-1.md)|Linux (see [System requirements](/defender-endpoint/mde-linux-prerequisites))|[Verify that devices can connect to Defender for Endpoint cloud services](mde-linux-prerequisites.md#verify-that-devices-can-connect-to-defender-for-endpoint-cloud-services)|
114
+
|[Defender for Endpoint Plan 1](defender-endpoint-plan-1.md)|Linux (see [System requirements](/defender-endpoint/mde-linux-prerequisites))|[Verify that devices can connect to Defender for Endpoint cloud services](mde-linux-prerequisites.md#verify-if-devices-can-connect-to-defender-for-endpoint-cloud-services)|
115
115
|[Defender for Endpoint Plan 2](microsoft-defender-endpoint.md)|[Windows 11](/windows/whats-new/windows-11-overview)<br/>[Windows 10](/windows/release-health/release-information)<br/>Windows Server 2025 (beginning in February 2025 and rolling out over the next several weeks)<br/>[Windows Server 2022](/windows-server/get-started/whats-new-in-windows-server-2022) <br/>[Windows Server 2019](/windows/release-health/status-windows-10-1809-and-windows-server-2019) <br/>[Windows Server 1803, or later](/windows-server/get-started/whats-new-in-windows-server-1803) <br/>[Windows Server 2016](/windows/release-health/status-windows-10-1607-and-windows-server-2016)\* <br/>[Windows Server 2012 R2](/windows/release-health/status-windows-8.1-and-windows-server-2012-r2)\*|[Configure machine proxy and internet connectivity settings](configure-proxy-internet.md)|
116
116
|[Defender for Endpoint Plan 2](microsoft-defender-endpoint.md)|[Windows Server 2008 R2 SP1](/windows/release-health/status-windows-7-and-windows-server-2008-r2-sp1) <br/>[Windows 8.1](/windows/release-health/status-windows-8.1-and-windows-server-2012-r2)<br/>[Windows 7 SP1](/windows/release-health/status-windows-7-and-windows-server-2008-r2-sp1)|[Configure proxy and internet connectivity settings](onboard-downlevel.md#configure-proxy-and-internet-connectivity-settings)|
117
117
|[Defender for Endpoint Plan 2](microsoft-defender-endpoint.md)|macOS (see [System requirements](microsoft-defender-endpoint-mac.md))|[Defender for Endpoint on macOS: Network connections](microsoft-defender-endpoint-mac-prerequisites.md#network-connectivity)|
0 commit comments