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: defender-endpoint/android-configure.md
+9-1Lines changed: 9 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -109,7 +109,15 @@ In the Microsoft Intune admin center, navigate to Apps > App configuration polic
109
109
> [!NOTE]
110
110
> - The other config keys of Network Protection will only work if the parent key '**Enable Network Protection in Microsoft Defender'** is enabled.
111
111
> - To ensure comprehensive protection against Wi-Fi threats, users should enable location permission and select the "Allow All the Time" option. This permission is optional but highly recommended, even when the app is not actively in use. If location permission is denied, Defender for Endpoint will only offer limited protection against network threats and will only safeguard users from rogue certificates.
112
-
**An open wi-fi network alert** is generated whenever a user connects to an open Wi-Fi network. If the user reconnects to the same network within a seven-day period, no new alert will be generated. However, connecting to a different open Wi-Fi network will result in an immediate alert.
112
+
113
+
> [!IMPORTANT]
114
+
> Starting May 19, 2025, alerts are no longer generated in the Microsoft Defender portal for mobile devices connecting or disconnecting to an open wireless network and for downloading/installing/deleting self-signed certificates. Instead, these activities are now generated as events and are viewable in the device timeline.</br></br>
115
+
> Here are a key changes about this new experience:</br>
116
+
> - For these changes to take effect, end-users must update to the latest version of Defender for Endpoint on Android available on May 2025. Otherwise, the previous experience of generating alerts will still be in place. If auto-remediation key is enabled by the admin, old alerts are resolved automatically after the changes take effect.</br>
117
+
> - WWhen an end-user connects or disconnects to an open wireless network multiple times within the same 24-hour period, only one event each for the connection and disconnection is generated in that 24-hour period and sent to the device timeline.</br>
118
+
> - Enable Users to Trust Networks: After the update, connection and disconnection events to open wireless networks, including to trusted networks, are sent to the device timeline as events.
119
+
> - Users allow-listed certificates: After the update, downloading/installing/deleting self-signed certificates events, including user-trusted certificates, are sent to the device timeline as events.</br>
120
+
> - The previous experience of generating alerts for these activities still continue to apply to GCC tenants.
Copy file name to clipboardExpand all lines: defender-endpoint/android-whatsnew.md
+12-1Lines changed: 12 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ ms.collection:
15
15
ms.topic: reference
16
16
ms.subservice: android
17
17
search.appverid: met150
18
-
ms.date: 04/18/2025
18
+
ms.date: 05/15/2025
19
19
---
20
20
21
21
# What's new in Microsoft Defender for Endpoint on Android
@@ -28,6 +28,17 @@ ms.date: 04/18/2025
28
28
29
29
Want to experience Microsoft Defender for Endpoint? [Sign up for a free trial.](https://go.microsoft.com/fwlink/p/?linkid=2225630)
30
30
31
+
#### Alerts for activities related to open wireless connection and certificates are now detected as events
32
+
33
+
May 2025
34
+
35
+
Starting May 19, 2025, security operations center (SOC) analysts can now view the following as events instead of alerts:
36
+
37
+
- Connecting or disconnecting to open wireless networks
38
+
- Download/installation/removal of self-signed certificates
39
+
40
+
These events can be viewed in the Timeline tab of a device page. For more information, see [Network protection](android-configure.md#network-protection).
41
+
31
42
#### Deploy Defender for Endpoint prerelease builds on Android devices using Google Play preproduction tracks
Copy file name to clipboardExpand all lines: defender-endpoint/ios-configure-features.md
+8-4Lines changed: 8 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ ms.collection:
14
14
ms.topic: conceptual
15
15
ms.subservice: ios
16
16
search.appverid: met150
17
-
ms.date: 03/27/2025
17
+
ms.date: 05/15/2025
18
18
---
19
19
20
20
# Configure Microsoft Defender for Endpoint on iOS features
@@ -167,9 +167,13 @@ Use the following procedure to set up MAM config for unenrolled devices for netw
167
167
168
168
6. Review and create the configuration policy.
169
169
170
-
> [!NOTE]
171
-
> **Open Wi-Fi Network Alert:**
172
-
> An alert is generated whenever a user connects to an open Wi-Fi network. If the user reconnects to the same network within a seven-day period, no new alert is generated. However, connecting to a different open Wi-Fi network results in an immediate alert.
170
+
> [!IMPORTANT]
171
+
> Starting May 19, 2025, alerts in the Microsoft Defender portal are no longer generated when users connect to an open wireless network. Instead, this activity now generates events and are viewable in the device timeline. With this change, security operations center (SOC) analysts can now view connection/disconnection to open wireless networks as events. If auto-remediation key is enabled, old alerts are resolved automatically after the changes take effect.</br></br>
172
+
> Here are key points about this change:</br>
173
+
> - For these changes to take effect, end-users must update to the latest version of Defender for Endpoint on iOS available on May 2025. Otherwise, the previous experience of generating alerts will still be in place. If auto-remediation key is enabled by the admin, old alerts are resolved automatically after the changes take effect.</br>
174
+
> - When an end-user connects or disconnects to an open wireless network multiple times within the same 24-hour period, only one event each for the connection and disconnection is generated in that 24-hour period and sent to the device timeline.</br>
175
+
> - Enable Users to Trust Networks: After the update, connection and disconnection events to open wireless networks, including to user trusted networks, are sent to the device timeline as events.</br>
176
+
> - This change doesn't impact GCC customers. The previous experience of receiving alerts while connecting to open wireless networks still apply to them.
Copy file name to clipboardExpand all lines: defender-endpoint/ios-whatsnew.md
+9-1Lines changed: 9 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ ms.author: ewalsh
6
6
author: emmwalshh
7
7
ms.reviewer: sunasing; denishdonga
8
8
ms.localizationpriority: medium
9
-
ms.date: 03/28/2025
9
+
ms.date: 05/15/2025
10
10
manager: deniseb
11
11
audience: ITPro
12
12
ms.collection:
@@ -29,6 +29,14 @@ search.appverid: met150
29
29
30
30
Want to experience Microsoft Defender for Endpoint? [Sign up for a free trial.](https://go.microsoft.com/fwlink/p/?linkid=2225630)
31
31
32
+
#### Alerts for activities related to open wireless connections are now detected as events
33
+
34
+
**May 2025**
35
+
36
+
Starting May 19, 2025, when a user connects to an open wireless network on a mobile device, an alert is no longer generated on the Microsoft Defender portal. Instead, this activity is added as an event and viewable under the device timeline.
37
+
38
+
For more information, see [Configure network protection](ios-configure-features.md#configure-network-protection).
39
+
32
40
#### Improving Usability: Key updates to the Microsoft Defender app interface on iOS
Copy file name to clipboardExpand all lines: defender-xdr/whats-new.md
+8-1Lines changed: 8 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,11 +32,17 @@ For more information on what's new with other Microsoft Defender security produc
32
32
33
33
You can also get product updates and important notifications through the [message center](https://admin.microsoft.com/Adminportal/Home#/MessageCenter).
34
34
35
+
35
36
## May 2025
36
37
37
38
- (Preview) You can now highlight your security operations achievements and the impact of Microsoft Defender using the **unified security summary**. The unified security summary is available in the Microsoft Defender portal and streamlines the process for SOC teams to generate security reports, saving time usually spent on collecting data from various sources and creating reports. For more information, see [Visualize security impact with the unified security summary](security-summary-report.md).
38
39
- Defender portal users who have onboarded Microsoft Sentinel and have enabled the [User and Entity Behavior Analytics (UEBA)](/azure/sentinel/ueba-reference) can now take advantage of the new unified [`IdentityInfo` table](advanced-hunting-identityinfo-table.md) in advanced hunting. This latest version now includes the largest possible set of fields common to both Defender and Azure portals.
39
-
40
+
- (Preview) The following advanced hunting schema tables are now available for preview to help you look through Microsoft Teams events and related information:
41
+
- The [MessageEvents](advanced-hunting-messageevents-table.md) table contains details about messages sent and received within your organization at the time of delivery
42
+
- The [MessagePostDeliveryEvents](advanced-hunting-messagepostdeliveryevents-table.md) table contains information about security events that occurred after the delivery of a Microsoft Teams message in your organization
43
+
- The [MessageUrlInfo](advanced-hunting-messageurlinfo-table.md) table contains information about URLs sent through Microsoft Teams messages in your organization
44
+
45
+
40
46
## April 2025
41
47
42
48
- (Preview) You can now create data security investigations in the Microsoft Defender portal with the integration of Microsoft Purview Data Security Investigations (preview) and Microsoft Defender XDR. This integration allows security operations center (SOC) teams to enhance their investigation and response to potential data security incidents like data breaches or data leaks. For more information, see [Create data security investigations in the Microsoft Defender portal](create-dsi-in-defender.md).
@@ -48,6 +54,7 @@ You can also get product updates and important notifications through the [messag
48
54
- The `OnboardingStatus` and `NetworkAdapterDnsSuffix` columns are now available in the [`DeviceNetworkInfo`](advanced-hunting-devicenetworkinfo-table.md) table in advanced hunting.
49
55
50
56
57
+
51
58
## March 2025
52
59
53
60
- (Preview) The incident description has moved within the incident page. The incident description is now displayed after the incident details. For more information, see [Incident details](investigate-incidents.md#incident-details).
Copy file name to clipboardExpand all lines: unified-secops-platform/malware-naming.md
+55-37Lines changed: 55 additions & 37 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,5 @@
1
1
---
2
2
title: How Microsoft names malware
3
-
ms.reviewer:
4
3
description: Understand the malware naming convention used by Microsoft Defender Antivirus and other Microsoft antimalware.
5
4
ms.service: unified-secops-platform
6
5
ms.localizationpriority: medium
@@ -12,7 +11,7 @@ ms.collection:
12
11
- must-keep
13
12
ms.topic: reference
14
13
search.appverid: met150
15
-
ms.date: 01/29/2024
14
+
ms.date: 05/09/2025
16
15
---
17
16
18
17
# Malware names
@@ -25,30 +24,24 @@ When our analysts research a particular threat, they determine what each of the
25
24
26
25
## Type
27
26
28
-
Describes what the malware does on your computer. Worms, viruses, trojans, backdoors, and ransomware are some of the most common types of malware.
27
+
Type describes what the malware does on your computer. The following are the different types of malware that Microsoft products detect.
28
+
29
+
### Malware
30
+
31
+
Following are the types of malware that Microsoft detects. To know more about how Microsoft defines malware, see [How Microsoft identifies malware and potentially unwanted applications - Malware](criteria.md#malware).
32
+
29
33
```
30
-
* Adware
31
34
* Backdoor
32
-
* Behavior
33
-
* BrowserModifier
34
35
* Constructor
35
36
* DDoS
36
37
* Exploit
37
38
* HackTool
38
39
* Joke
39
-
* Misleading
40
-
* MonitoringTool
41
-
* Program
42
40
* Password Stealer (PWS)
43
41
* Ransom
44
-
* RemoteAccess
45
42
* Rogue
46
-
* SettingsModifier
47
-
* SoftwareBundler
48
43
* Spammer
49
44
* Spoofer
50
-
* Spyware
51
-
* Tool
52
45
* Trojan
53
46
* TrojanClicker
54
47
* TrojanDownloader
@@ -59,6 +52,52 @@ Describes what the malware does on your computer. Worms, viruses, trojans, backd
59
52
* Virus
60
53
* Worm
61
54
```
55
+
56
+
### Unwanted software
57
+
58
+
Following are the types of unwanted software that Microsoft products detect. For more information on what unwanted software is and what is classified as unwanted software, see [Unwanted software](criteria.md#unwanted-software).
59
+
60
+
```
61
+
* Adware
62
+
* BrowserModifier
63
+
* Misleading
64
+
* MonitoringTool
65
+
* Program
66
+
* SoftwareBundler
67
+
* UwS
68
+
```
69
+
70
+
### Potentially unwanted applications
71
+
72
+
Following are the types of potentially unwanted applications (PUAs) that Microsoft products detect. To know what PUAs are, see [Potentially unwanted application (PUA)](criteria.md#potentially-unwanted-application-pua).
73
+
74
+
```
75
+
* PUA
76
+
* App
77
+
* PUAAdvertising
78
+
* PUATorrent
79
+
* PUAMiner
80
+
* PUAMarketing
81
+
* PUABundler
82
+
* PUADlManager
83
+
```
84
+
### Tampering software
85
+
86
+
Tampering software, detected as ***Tampering** are tools that can lower device security. To know more, see [Tampering software](criteria.md#tampering-software).
87
+
88
+
### Vulnerable software
89
+
90
+
Following are the types of vulnerable software that Microsoft products detect. Know more about this detection in [Vulnerable software](criteria.md#vulnerable-software).
91
+
92
+
```
93
+
* Vulnerable
94
+
* VulnerableDriver
95
+
```
96
+
97
+
### Other malware types
98
+
99
+
Microsoft also detects ***Behavior** and ***Tool** types of malware.
100
+
62
101
## Platforms
63
102
64
103
Platforms guide the malware to its compatible operating system (such as Windows, macOS, and Android). The platform's guidance is also used for programming languages and file formats.
@@ -157,29 +196,8 @@ Grouping of malware based on common characteristics, including attribution to th
157
196
158
197
## Variant letter
159
198
160
-
Used sequentially for every distinct version of a malware family. For example, the detection for the variant **".AF"**would have been created after the detection for the variant **".AE"**.
199
+
Used sequentially for every distinct version of a malware family. For example, the detection for the variant **".AF"**is created after the detection for the variant **".AE"**.
161
200
162
201
## Suffixes
163
202
164
-
Provides extra detail about the malware, including how it's used as part of a multicomponent threat. In the preceding example, **"!lnk"** indicates that the threat component is a shortcut file used by Trojan: **Win32/Reveton.T**.
165
-
```
166
-
* .dam: damaged malware
167
-
* .dll: Dynamic Link Library component of a malware
168
-
* .dr: dropper component of a malware
169
-
* .gen: malware that is detected using a generic signature
170
-
* .kit: virus constructor
171
-
* .ldr: loader component of a malware
172
-
* .pak: compressed malware
173
-
* .plugin: plug-in component
174
-
* .remnants: remnants of a virus
175
-
* .worm: worm component of that malware
176
-
* !bit: an internal category used to refer to some threats
177
-
* !cl: an internal category used to refer to some threats
178
-
* !dha: an internal category used to refer to some threats
179
-
* !pfn: an internal category used to refer to some threats
180
-
* !plock: an internal category used to refer to some threats
181
-
* !rfn: an internal category used to refer to some threats
182
-
* !rootkit: rootkit component of that malware
183
-
* @m: worm mailers
184
-
* @mm: mass mailer worm
185
-
```
203
+
A suffix that begins with **!** is an indicator used by Microsoft internally.
0 commit comments