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/service-account-discovery.md
+16-14Lines changed: 16 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ ms.topic: conceptual
5
5
ms.date: 03/25/2025
6
6
---
7
7
8
-
# Investigate and protect Service Accounts | Microsoft Defender for Identity
8
+
# Investigate and protect Service Accounts
9
9
10
10
### What are Service Accounts?
11
11
@@ -17,7 +17,7 @@ Service accounts are classified into several types:
17
17
- sMSA (Managed Service Accounts): Designed for individual services on a single server rather than groups.
18
18
- User Account: These standard user accounts are typically used for interactive logins but can also be configured to run services.
19
19
20
-
The auto discovery feature quickly identifies gMSA and sMSA accounts as well as user accounts within Active Directory that meet specific criteria.These criteria include having a [Service Principal Name ](/windows/win32/ad/service-principal-names)(SPN) or a "password never expires" attribute assigned. The feature then classifies these accounts as service accounts. These accounts are then highlighted and presented, along with relevant information including insights into recent authentications and the sources and destinations of those interactions, as part of a dedicated inventory within the Defender experience. This helps you better understand the accounts' purpose so you can more easily spot anomalous activity and understand its implications.
20
+
The auto discovery feature quickly identifies gMSA and sMSA accounts and user accounts within Active Directory that meet specific criteria.These criteria include having a [Service Principal Name ](/windows/win32/ad/service-principal-names)(SPN) or a "password never expires" attribute assigned. The feature then classifies these accounts as service accounts. These accounts are then highlighted and presented, along with relevant information including insights into recent authentications and the sources and destinations of those interactions, as part of a dedicated inventory within the Defender experience. This helps you better understand the accounts' purpose so you can more easily spot anomalous activity and understand its implications.
21
21
22
22
Service account types are displayed in the Identity Info table within Advanced Hunting.
23
23
@@ -77,7 +77,7 @@ You can use the sort and filter functionality on each service account tab to get
77
77
### Connections
78
78
79
79
80
-
For a deeper dive into what's happening in your service account click on the domain name to see the following information:
80
+
For a deeper dive into what's happening in your service account select the domain name to see the following information:
81
81
82
82
When you investigate a specific Service account, you see the following details under the connections tab:
83
83
@@ -96,21 +96,23 @@ When you investigate a specific Service account, you see the following details u
96
96
Last seen | The date and time of the most recent sign in event over this connection. |
97
97
98
98
99
-
### Create custom service account classification rules
99
+
### Define Service Account classification rules
100
100
101
-
Create custom service account classification rules to help you identify and classify service accounts based on specific criteria that are relevant to your organization. This allows you to tailor the service account discovery process to better suit your needs.
101
+
Service account classification rules let you define your own criteria for identifying service accounts. These rules help you include service accounts that Defender for Identity doesn't identify automatically. For example, some organizations name all their service accounts with a prefix like `srv`. Defender for Identity doesn't automatically detect such naming conventions. By creating a classification rule based on that pattern, you can include those accounts in the Service accounts view.
102
102
103
-
You can create custom service account classification rules by selecting the following supported filters:
103
+
Classification rules work alongside Defender for Identity’s automatic discovery and provide a more complete and customized view of service accounts in your environment.
104
104
105
-
- Account Display Name
106
-
- Account Domain
107
-
- Account Name
108
-
- Organizational Unit
105
+
To create a rule:
109
106
110
-
Service accounts discovered via the custom classifications are displayed on the Service Accounts page, alongside the automatically discovered service accounts that MDI identifies such as users with SPN + password set to never expire, gMSA, and sMSA.
111
-
112
-
> [!NOTE]
113
-
> Service accounts labeled with the prefix srv are not detected.
107
+
1. Go to Settings > Microsoft Defender XDR > Service accounts classification.
108
+
1. Select on **+ Create a new rule**.
109
+
1. Enter a name for the rule. (Optional: add a description.)
110
+
1. Select one or more of the following filters:
111
+
-**Account display name**
112
+
-**Account domain**
113
+
-**Account SAM name**
114
+
-**Organizational unit**
115
+
1. Select Create to save the rule.
114
116
115
117
116
118
For more information about the following tabs, **Overview**, **Incidents and alerts**,**Observed in organization**, **Timeline**, and **Attack paths**, see: [Investigate assets](/defender-for-identity/investigate-assets#identity-details).
Copy file name to clipboardExpand all lines: ATPDocs/whats-new.md
+22-14Lines changed: 22 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,18 +23,26 @@ For more information, see also:
23
23
24
24
For updates about versions and features released six months ago or earlier, see the [What's new archive for Microsoft Defender for Identity](whats-new-archive.md).
25
25
26
+
## June 2025
27
+
28
+
### Service account classification rules now available
29
+
30
+
You can now create custom classification rules to identify service accounts based on your organization’s specific criteria. This complements automatic discovery, enabling more accurate identification of service accounts. For example, by defining rules based on naming patterns or organizational units.
31
+
32
+
For more information, see [Service account discovery](service-account-discovery.md#add-service-account-classification-rules).
33
+
26
34
## May 2025
27
35
28
36
### Expanded New Sensor Deployment Support for Domain Controllers (Preview)
29
37
Defender for Identity now supports deploying its new sensor on Domain Controllers without requiring Defender for Endpoint onboarding. This simplifies sensor activation and expands deployment flexibility. [Learn more](deploy/activate-capabilities.md).
30
38
31
39
32
40
### Improved Visibility into Defender for Identity New Sensor Eligibility in the Activation page
33
-
The Activation Page now displays all servers from your device inventory, including those not currently eligible for the new Defender for Identity sensor. This enhancement increases transparency into sensor eligibility, helping you identify non-eligible servers and take action to update and onboard them for enhanced identity protection.
41
+
The Activation Page now displays all servers from your device inventory, including those not currently eligible for the new Defender for Identity sensor. This enhancement increases transparency into sensor eligibility, helping you identify noneligible servers and take action to update and onboard them for enhanced identity protection.
34
42
35
43
36
44
### Local administrators collection (using SAM-R queries) feature will be disabled
37
-
The remote collection of local administrators group members from endpoints using SAM-R queries in Microsoft Defender for Identity will be disabled by mid-May 2025. This data is currently used to build potential lateral movement path maps, which will no longer be updated after this change. An alternative method is being explored. The change will occur automatically by the specified date, and no administrative action is required.
45
+
The remote collection of local administrators group members from endpoints using SAM-R queries in Microsoft Defender for Identity will be disabled by mid-May 2025. This data is currently used to build potential lateral movement path maps, which will no longer be updated after this change. An alternative method is being explored. The change occurs automatically by the specified date, and no administrative action is required.
38
46
39
47
### New Health Issue
40
48
@@ -165,7 +173,7 @@ For more information, see:
165
173
The new Identity security posture assessments (ISPMs) can help customers monitor misconfiguration by watching for weak spots and reduce the risk of potential attack on on-premises infrastructure.
166
174
These new identity recommendations, as part of Microsoft Secure Score, are new security posture reports related to Active Directory infrastructure and Group policy Objects:
167
175
168
-
-[Accounts with non-default Primary Group ID](/defender-for-identity/accounts-with-non-default-pgid)
176
+
-[Accounts with nondefault Primary Group ID](/defender-for-identity/accounts-with-non-default-pgid)
169
177
170
178
-[Change Domain Controller computer account old password](/defender-for-identity/domain-controller-account-password-change)
171
179
@@ -207,7 +215,7 @@ As part of our ongoing effort to enhance Microsoft Defender for Identity coverag
207
215
***Suspicious Interactive Logon to the Microsoft Entra Connect Server**
208
216
* Direct logins to Microsoft Entra Connect servers are highly unusual and potentially malicious. Attackers often target these servers to steal credentials for broader network access. Microsoft Defender for Identity can now detect abnormal logins to Microsoft Entra Connect servers, helping you identify and respond to these potential threats faster. It's specifically applicable when the Microsoft Entra Connect server is a standalone server and not operating as a Domain Controller.
209
217
***User Password Reset by Microsoft Entra Connect Account**
210
-
* The Microsoft Entra Connect connector account often holds high privileges, including the ability to reset user’s passwords. Microsoft Defender for Identity now has visibility into those actions and will detect any usage of those permissions that were identified as malicious and non-legitimate. This alert will be triggered only if the [password writeback feature](/entra/identity/authentication/concept-sspr-writeback) is disabled.
218
+
* The Microsoft Entra Connect connector account often holds high privileges, including the ability to reset user’s passwords. Microsoft Defender for Identity now has visibility into those actions and will detect any usage of those permissions that were identified as malicious and non-legitimate. This alert is triggered only if the [password writeback feature](/entra/identity/authentication/concept-sspr-writeback) is disabled.
211
219
***Suspicious writeback by Microsoft Entra Connect on a sensitive user**
212
220
* While Microsoft Entra Connect already prevents writeback for users in privileged groups, Microsoft Defender for Identity expands this protection by identifying additional types of sensitive accounts. This enhanced detection helps prevent unauthorized password resets on critical accounts, which can be a crucial step in advanced attacks targeting both cloud and on-premises environments.
213
221
@@ -236,7 +244,7 @@ For more information, see:
236
244
237
245
## July 2024
238
246
239
-
6 New detections are new in public preview:
247
+
Six New detections are new in public preview:
240
248
***Possible NetSync attack**
241
249
* NetSync is a module in Mimikatz, a post-exploitation tool, that requests the password hash of a target device's password by pretending to be a domain controller. An attacker might be performing malicious activities inside the network using this feature to gain access to the organization's resources.
242
250
***Possible takeover of a Microsoft Entra seamless SSO account**
@@ -287,7 +295,7 @@ With this data customers can now easily create their own [custom detection rules
Now, you can copy our recommended query as provided below, and click on “Create detection rule”. Please be aware that our provided query also tracks failed logon attempts, which may generate information unrelated to a potential attack. Therefore, feel free to customize the query to suit your specific requirements.
298
+
Now, you can copy our recommended query as provided below, and click on “Create detection rule”. Be aware that our provided query also tracks failed logon attempts, which may generate information unrelated to a potential attack. Therefore, feel free to customize the query to suit your specific requirements.
291
299
292
300
293
301
```
@@ -459,13 +467,13 @@ This version includes improvements and bug fixes for cloud services and the Defe
459
467
> [!NOTE]
460
468
> If you're seeing a decreased number of *Remote code execution attempt* alerts, see our updated [September announcements](#september-2023), which include an [update to the Defender for Identity detection logic](#decreased-number-of-alerts-for-remote-code-execution-attempts). Defender for Identity continues to record the remote code execution activities as before.
461
469
462
-
### New Identities area and dashboard in Microsoft 365 Defender (Preview)
470
+
### New Identities area and dashboard in Microsoft Defender XDR (Preview)
463
471
464
-
Defender for Identity customers now have a new **Identities** area in Microsoft 365 Defender for information about identity security with Defender for Identity.
472
+
Defender for Identity customers now have a new **Identities** area in Microsoft Defender XDR for information about identity security with Defender for Identity.
465
473
466
-
In Microsoft 365 Defender, select **Identities** to see any of the following new pages:
474
+
In Microsoft Defender XDR, select **Identities** to see any of the following new pages:
467
475
468
-
-**Dashboard**: This page shows graphs and widgets to help you monitor identity threat detection and response activities. For example:
476
+
-**Dashboard**: This page shows graphs and widgets to help you monitor identity threat detection and response activities. For example:
@@ -481,7 +489,7 @@ This version includes improvements and bug fixes for cloud services and the Defe
481
489
482
490
### Security posture assessments for AD CS sensors (Preview)
483
491
484
-
Defender for Identity's security posture assessments proactively detect and recommend actions across your on-premises Active Directory configurations.
492
+
Defenders for Identity's security posture assessments proactively detect and recommend actions across your on-premises Active Directory configurations.
485
493
486
494
Recommended actions now include the following new security posture assessments, specifically for certificate templates and certificate authorities.
487
495
@@ -499,7 +507,7 @@ Recommended actions now include the following new security posture assessments,
-[Enforce encryption for RPC certificate enrollment interface (ESC11)](security-assessment-enforce-encryption-rpc.md)
501
509
502
-
The new assessments are available in Microsoft Secure Score, surfacing security issues and severe misconfigurations that pose risks to the entire organization, alongside detections. Your score is updated accordingly.
510
+
The new assessments are available in Microsoft Secure Score, surfacing security issues, and severe misconfigurations that pose risks to the entire organization, alongside detections. Your score is updated accordingly.
503
511
504
512
For example:
505
513
@@ -508,7 +516,7 @@ For example:
508
516
For more information, see [Microsoft Defender for Identity's security posture assessments](security-assessment.md).
509
517
510
518
> [!NOTE]
511
-
> While *certificate template* assessments are available to all customers that have AD CS installed on their environment, *certificate authority* assessments are available only to customers who've installed a sensor on an AD CS server. For more information, see [New sensor type for Active Directory Certificate Services (AD CS)](#new-sensor-type-for-active-directory-certificate-services-ad-cs).
519
+
> While *certificate template* assessments are available to all customers that have AD CS installed on their environment, *certificate authority* assessments are available only to customers who have installed a sensor on an AD CS server. For more information, see [New sensor type for Active Directory Certificate Services (AD CS)](#new-sensor-type-for-active-directory-certificate-services-ad-cs).
512
520
513
521
### Defender for Identity release 2.223
514
522
@@ -581,7 +589,7 @@ While this change results in a decreased number of *Remote code execution attemp
581
589
582
590
### Alert sensitivity settings and learning period enhancements
583
591
584
-
Some Defender for Identity alerts wait for a *learning period* before alerts are triggered, while building a profile of patterns to use when distinguishing between legitimate and suspicious activities.
592
+
Some Defenders for Identity alerts wait for a *learning period* before alerts are triggered, while building a profile of patterns to use when distinguishing between legitimate and suspicious activities.
585
593
586
594
Defender for Identity now provides the following enhancements for the learning period experience:
0 commit comments