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/remove-inactive-service-account.md
+6-7Lines changed: 6 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,13 +6,13 @@ ms.topic: how-to
6
6
#customer intent: As a security administrator, I want to improve security posture in my organization by removing inactive service accounts
7
7
---
8
8
9
-
# Security Assessment: Remove Inactive Service Accounts (Preview)
9
+
# Security Assessment: Remove Stale Service Accounts (Preview)
10
10
11
-
This recommendation lists Active Directory service accounts detected as inactive (stale) within the past 180 days.
11
+
This recommendation lists Active Directory service accounts detected as stale within the past 90 days.
12
12
13
-
## Why do inactive service accounts pose a risk?
13
+
## Why do stale service accounts pose a risk?
14
14
15
-
Unused service accounts create significant security risks, as some of them can carry elevated privileges. If attackers gain access, the result can be substantial damage. Dormant service accounts might retain high or legacy permissions. When compromised, they provide attackers with discreet entry points into critical systems, granting far more access than a standard user account.
15
+
Unused service accounts create significant security risks, as some of them can carry elevated privileges. If attackers gain access, the result can be substantial damage. Stale service accounts might retain high or legacy permissions. When compromised, they provide attackers with discreet entry points into critical systems, granting far more access than a standard user account.
16
16
17
17
This exposure creates several risks:
18
18
@@ -25,10 +25,9 @@ This exposure creates several risks:
25
25
26
26
To use this security assessment effectively, follow these steps:
27
27
28
-
1. Review the recommended action at [https://security.microsoft.com/securescore?viewid=actions ](https://security.microsoft.com/securescore?viewid=actions ) for Remove inactive service account.
29
-
1. Review the list of exposed entities to discover which of your service account is inactive.
28
+
1. Review the recommended action at [https://security.microsoft.com/securescore?viewid=actions ](https://security.microsoft.com/securescore?viewid=actions) for Remove stale service account.
30
29
31
-
:::image type="content" source="media/okta-integration/remove-inactive-service-accounts.png" alt-text="Screenshot that shows the recommendation action to remove inactive service accounts." lightbox="media/okta-integration/remove-inactive-service-accounts.png":::
30
+
1. Review the list of exposed entities to discover which of your serviceaccounts are stale and have not performed any login activity in the last 90 days.
32
31
33
32
1. Take appropriate actions on those entities by removing the service account. For example:
Copy file name to clipboardExpand all lines: ATPDocs/whats-new.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -42,11 +42,11 @@ Previously, Defender for Identity tenants received Entra ID risk level in the Id
42
42
43
43
For UEBA tenants without a Microsoft Defender for Identity license, synchronization of Entra ID risk level to the IdentityInfo table remains unchanged.
44
44
45
-
### New security assessment: Remove inactive service accounts (Preview)
45
+
### New security assessment: Remove stale service accounts (Preview)
46
46
47
-
Microsoft Defender for Identity now includes a new security assessment that helps you identify and remove inactive service accounts in your organization. This assessment lists Active Directory service accounts that have been inactive (stale) for the past 180 days, to help you mitigate security risks associated with unused accounts.
47
+
Microsoft Defender for Identity now includes a new security assessment that helps you identify and remove inactive service accounts in your organization. This assessment lists Active Directory service accounts that have been stale for the past 90 days, to help you mitigate security risks associated with unused accounts.
48
48
49
-
For more information, see: [Security Assessment: Remove Inactive Service Accounts (Preview)](remove-inactive-service-account.md)
49
+
For more information, see: Security Assessment: [Remove Stale Service Accounts (Preview)](/defender-for-identity/remove-inactive-service-account)
50
50
51
51
### New Graph based API for response actions (preview)
@@ -52,17 +52,34 @@ In this demonstration article, you have two engine choices to test AMSI:
52
52
```powershell
53
53
$testString = "AMSI Test Sample: " + "7e72c3ce-861b-4339-8740-0ac1484c1386"
54
54
Invoke-Expression $testString
55
-
```
55
+
```powershell
56
56
57
-
2. On your device, open PowerShell as an administrator.
57
+
1. On your device, open PowerShell as an administrator.
58
58
59
-
3. Type `Powershell -ExecutionPolicy Bypass AMSI_PoSh_script.ps1`, and then press **Enter**.
59
+
1. Type `Powershell -ExecutionPolicy Bypass AMSI_PoSh_script.ps1`, and then press **Enter**.
60
60
61
61
The result should be as follows:
62
62
63
-
:::image type="content" source="media/mde-demonstrations-amsi/test-amsi-powershell-results.png" alt-text="Screenshot showing the results of the AMSI test sample. It should show a threat was detected." lightbox="media/mde-demonstrations-amsi/test-amsi-powershell-results.png":::
63
+
```powershell
64
+
Invoke-Expression : At line:1 char:1
65
+
66
+
+ AMSI Test Sample: 7e72c3ce-861b-4339-8740-8ac1484c1386
1. Save the following VBScript as `AMSI_vbscript.vbs`:
@@ -74,20 +91,63 @@ In this demonstration article, you have two engine choices to test AMSI:
74
91
WScript.Echo result
75
92
```
76
93
77
-
2. On your Windows Device, open Command Prompt as an administrator.
94
+
1. On your Windows Device, open Command Prompt as an administrator.
78
95
79
96
1. Type `wscript AMSI_vbscript.vbs`, and then press **Enter**.
80
97
81
98
The result should be as follows:
82
99
83
-
:::image type="content" source="media/mde-demonstrations-amsi/test-amsi-vbscript-results.png" alt-text="Screenshot showing the AMSI test results. It should show that antivirus software blocked the script." lightbox="media/mde-demonstrations-amsi/test-amsi-vbscript-results.png":::
In your protection history, you should be able to see the following information:
89
119
90
-
:::image type="content" source="media/mde-demonstrations-amsi/verifying-results.png" alt-text="Screenshot showing the AMSI test results. The information should show that a threat was blocked and cleaned." lightbox="media/mde-demonstrations-amsi/verifying-results.png":::
### Get the list of Microsoft Defender Antivirus threats
93
153
@@ -101,17 +161,68 @@ You can view detected threats by using the Event log or PowerShell.
101
161
102
162
3. Look for `event ID 1116`. You should see the following information:
103
163
104
-
:::image type="content" source="media/mde-demonstrations-amsi/eventid1116.png" alt-text="Screenshot showing Event ID 1116, which says malware or unwanted software was detected." lightbox="media/mde-demonstrations-amsi/eventid1116.png":::
164
+
```powershell
165
+
166
+
Microsoft Defender Antivirus has detected malware or other potentially unwanted software.
167
+
168
+
For more information please see the following: https://go.microsoft.com/fwlink/?linkid=37020&name=Virus:Win32/MpTest!amsi&t
169
+
170
+
Name: Virus:Win32/MpTest!amsi
171
+
172
+
ID: 2147694217
173
+
174
+
Severity: Severe
175
+
176
+
Category: Virus
177
+
178
+
Path: \Device\HarddiskVolume3\Windows\System32\WindowsPowerShell\v1.0\powershell.exe or C:\Users\Admin\Desktop\AMSI_jscri
179
+
180
+
Detection Origin: Local machine or Unknown
181
+
182
+
Detection Type: Concrete
183
+
184
+
Detection Source: System
185
+
186
+
User: NT AUTHORITY\SYSTEM
105
187
106
-
##### Use PowerShell
188
+
Process Name: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe or C:\Windows\System32\cscript.exe or C:\Windows\Sy
:::image type="content" source="media/mde-demonstrations-amsi/get-mpthreat-results.png" alt-text="Screenshot showing the results of the Get-MpThreat command. It should show that an AMSI threat was detected." lightbox="media/mde-demonstrations-amsi/get-mpthreat-results.png":::
Copy file name to clipboardExpand all lines: defender-endpoint/whats-new-in-microsoft-defender-endpoint.md
+3-6Lines changed: 3 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ author: limwainstein
8
8
ms.reviewer: noamhadash, pahuijbr, yongrhee
9
9
ms.localizationpriority: medium
10
10
ms.date: 08/20/2025
11
-
manager: orspodek
11
+
manager: bagol
12
12
audience: ITPro
13
13
ms.collection:
14
14
- m365-security
@@ -44,11 +44,8 @@ Learn more:
44
44
45
45
|Feature |Preview/GA |Description |
46
46
|---------|------------|-------------|
47
-
|[Microsoft Defender Core service](/defender-endpoint/microsoft-defender-core-service-overview)|GA |- Microsoft Defender Core service, now in GA, helps with the stability and performance of Microsoft Defender Antivirus.<br>- Support for Azure Stack HCI OS is rolling out across commercial and government clouds.|
48
-
49
-
## July 2025
50
-
51
-
- (Preview) Added support for Azure Stack HCI OS, version 23H2 and later. This support will roll out gradually across all clouds and regions in July.
47
+
|Azure Stack HCI OS support (version 23H2 and later) |Preview |Added support for Azure Stack HCI OS, version 23H2 and later. Support for Azure Stack HCI OS is rolling out across commercial and government clouds. |
48
+
|[Microsoft Defender Core service](/defender-endpoint/microsoft-defender-core-service-overview)|GA |Microsoft Defender Core service, now in GA, helps with the stability and performance of Microsoft Defender Antivirus.|
0 commit comments