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/ios-whatsnew.md
+23-6Lines changed: 23 additions & 6 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: deniseb
6
6
author: denisebmsft
7
7
ms.reviewer: sunasing; denishdonga
8
8
ms.localizationpriority: medium
9
-
ms.date: 02/11/2025
9
+
ms.date: 03/14/2025
10
10
manager: deniseb
11
11
audience: ITPro
12
12
ms.collection:
@@ -29,24 +29,41 @@ 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&clcid=0x409&culture=en-us&country=us)
31
31
32
-
#### Microsoft Defender for Mobile: Open Wi-Fi Detection Update
32
+
#### Improving Usability: Key updates to the Microsoft Defender app interface on iOS
33
+
34
+
**March 2025**
35
+
36
+
As part of our ongoing commitment to delivering an exceptional user experience, we are excited to announce a series of upcoming changes to the user interface and overall experience of the Defender for Endpoint mobile app. These enhancements are designed to improve usability, streamline navigation, and ensure our app meets the evolving needs of our users.
37
+
38
+
**Key Changes:**
39
+
40
+
We are pleased to introduce the **Device Protection** feature card for our enterprise users which includes Web Protection, Device Health and Jail break feature that has been designed to be more user-friendly and accessible. The updated feature cards now include recommendation cards. The first recommendation card will prominently display any active alerts, ensuring you stay informed.
41
+
42
+
**The main changes involved are**:
43
+
44
+
- Main dashboard changes
45
+
- A feature card lists the features
46
+
- Detailed feature experience
47
+
- Recommendation cards for alerts
48
+
49
+
For more information, see [User Experience in Microsoft Defender for Endpoint on iOS](/defender-endpoint/ios-new-ux).
50
+
51
+
#### Microsoft Defender for Endpoint: Open Wi-Fi Detection Update
33
52
34
53
**February 2025:**
35
54
36
-
As part of our Microsoft Defender for Mobile application, we offer Open Wi-Fi detection within our Network Protection feature set. When enabled, this feature raises an alert in the Security portal. Currently, the alert is informational and doesn't require any action by the SOC analyst or admin. It serves as a key piece of information that helps with triaging incidents involving mobile devices.
55
+
As part of our Microsoft Defender application, we offer open Wi-Fi detection within the network protection feature set. When enabled, this feature raises an alert in the Microsoft Defender portal. Currently, the alert is informational and doesn't require any action by the SOC analyst or admin. It serves as a key piece of information that helps with triaging incidents involving mobile devices.
37
56
38
57
**Current Behavior:**
39
58
40
59
- Every time the end user connects to an open Wi-Fi network, an alert is raised.
41
-
42
60
- If the user goes out of the open Wi-Fi range and reconnects to the same network, another alert is raised.
43
61
44
62
Based on our research insights and inputs from Microsoft and other SOC teams, we're implementing a caching behavior to ensure the value of the alerts remains and also doesn't cause fatigue to SOC teams due to sheer volume.
45
63
46
-
**New behavior:**
64
+
**New behavior:**
47
65
48
66
- Every time the end user connects to an open Wi-Fi network, an alert is raised.
49
-
50
67
- If a user reconnects to the same open wi-fi in the next seven days, another alert won't be raised.
51
68
52
69
Note that if a user connects to a different open Wi-Fi network, an alert is immediately generated, and there's no change to that behavior.
Copy file name to clipboardExpand all lines: defender-office-365/attack-simulation-training-teams.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,17 +10,17 @@ ms.localizationpriority: medium
10
10
ms.collection:
11
11
- m365-security
12
12
- tier2
13
-
description: Admins can learn about the addition of Microsoft Teams in delivering simulated phishing attacks in Attack simulation training in Microsoft Defender for Office 365 Plan 2.
13
+
description: Admins can learn about the addition in Microsoft Defender for Office 365 Plan 2 of delivering simulated phishing attacks in Attack simulation training to Microsoft Teams.
14
14
search.appverid: met150
15
-
ms.date: 3/15/2024
15
+
ms.date: 3/13/2025
16
16
appliesto:
17
17
- ✅ <a href="https://learn.microsoft.com/defender-office-365/mdo-about#defender-for-office-365-plan-1-vs-plan-2-cheat-sheet" target="_blank">Microsoft Defender for Office 365 Plan 2</a>
18
18
---
19
19
20
20
# Microsoft Teams in Attack simulation training
21
21
22
22
> [!IMPORTANT]
23
-
> Microsoft Teams' Attack simulation training is currently in Private Preview, and the intake for this preview is now closed. The information in this article is subject to change.
23
+
> Microsoft Teams' Attack simulation training is currently in Private Preview. The information in this article is subject to change.
24
24
25
25
In organizations with Microsoft Defender for Office 365 Plan 2 or Microsoft Defender XDR, admins can now use Attack simulation training to deliver simulated phishing messages in Microsoft Teams. For more information about attack simulation training, see [Get started using Attack simulation training in Defender for Office 365](attack-simulation-training-get-started.md).
26
26
@@ -41,10 +41,10 @@ The addition of Teams in Attack simulation training affects the following featur
41
41
42
42
In addition to having user reporting for Teams messages turned on as described in [User reported message settings in Microsoft Teams](submissions-teams.md), you also need to configure the Teams accounts that can be used as sources for simulation messages in Attack simulation training. To configure the accounts, do the following steps:
43
43
44
-
1. Identify or create a user who's a member of the [Global Administrator](/entra/identity/role-based-access-control/permissions-reference#global-administrator)<sup>\*</sup>, [Security Administrator](/entra/identity/role-based-access-control/permissions-reference#security-administrator), or [Attack Simulation Administrator](/entra/identity/role-based-access-control/permissions-reference#attack-simulation-administrator) roles in Microsoft Entra ID. Assign a Microsoft 365, Office 365, Microsoft Teams Essentials, Microsoft 365 Business Basic, or a Microsoft 365 Business Standard license for [Microsoft Teams](/office365/servicedescriptions/teams-service-description). You need to know the password.
44
+
1. Identify or create a user who's a member of the [Global Administrator](/entra/identity/role-based-access-control/permissions-reference#global-administrator), [Security Administrator](/entra/identity/role-based-access-control/permissions-reference#security-administrator), or [Attack Simulation Administrator](/entra/identity/role-based-access-control/permissions-reference#attack-simulation-administrator) roles in Microsoft Entra ID. Assign a Microsoft 365, Office 365, Microsoft Teams Essentials, Microsoft 365 Business Basic, or a Microsoft 365 Business Standard license for [Microsoft Teams](/office365/servicedescriptions/teams-service-description). You need to know the password.
45
45
46
46
> [!IMPORTANT]
47
-
> <sup>\*</sup> Microsoft recommends that you use roles with the fewest permissions. Using lower permissioned accounts helps improve security for your organization. Global Administrator is a highly privileged role that should be limited to emergency scenarios when you can't use an existing role.
47
+
> Microsoft recommends that you use roles with the fewest permissions. Using lower permissioned accounts helps improve security for your organization. Global Administrator is a highly privileged role that should be limited to emergency scenarios when you can't use an existing role.
48
48
49
49
2. Using the account from Step 1, open the Microsoft Defender portal at <https://security.microsoft.com> and go to **Email & collaboration**\>**Attack simulation training**\>**Settings** tab. Or, to go directly to the **Settings** tab, use <https://security.microsoft.com/attacksimulator?viewid=setting>.
50
50
3. On the **Settings** tab, select **Manager user accounts** in the **Teams simulation configuration** section.
@@ -93,7 +93,7 @@ Whether you create a payload on the **Payloads** page of the **Content library**
93
93
94
94
- If you select :::image type="icon" source="media/m365-cc-sc-create-icon.png" border="false"::: **Create a payload** on the **Tenant payload** tab to create a payload, the first page of the new payload wizard is **Select type** where you can select **Teams**. Selecting **Teams** introduces the following changes to the rest of the new payload wizard:
95
95
96
-
- On the **[Select technique](attack-simulation-training-payloads.md#create-payloads)** page, the **Malware Attachment** and **Link in Attachment** social engineering techniques aren't available for Teams.
96
+
- On the **[Select technique](attack-simulation-training-payloads.md#create-payloads)** page, the **Malware Attachment**, **Link in Attachment**, and **How-to Guide** techniques aren't available for Teams.
97
97
98
98
- The **Configure payload** page has the following changes for Teams:
99
99
-**Sender details** section: The only available setting for Teams is **Chat topic** where you enter a tile for the Teams message.
In organizations with Microsoft Defender for Office 365 Plan 2 or Microsoft Defender XDR, admins can decide whether users can report malicious messages in Microsoft Teams. Admins can also get visibility into the Teams messages that users are reporting.
30
30
31
-
Users can report messages in Teams from **internal**chats, channels and meeting conversations. Users can only report messages as malicious.
31
+
Users can report messages in Teams from chats, standard channels and meeting conversations. Users can only report messages as malicious.
32
32
33
33
> [!NOTE]
34
34
> User reporting of messages in Teams is not supported in U.S. Government organizations (Microsoft 365 GCC, GCC High, and DoD).
@@ -48,7 +48,7 @@ User reporting of messages in Teams is made of two separate settings:
48
48
To view or configure this setting, you need to be a member of the **Global Administrator**<sup>\*</sup> or **Teams Administrator** roles. For more information about permissions in Teams, see [Use Microsoft Teams administrator roles to manage Teams](/microsoftteams/using-admin-roles).
49
49
50
50
> [!IMPORTANT]
51
-
> <sup>\*</sup> Microsoft recommends that you use roles with the fewest permissions. Using lower permissioned accounts helps improve security for your organization. Global Administrator is a highly privileged role that should be limited to emergency scenarios when you can't use an existing role.
51
+
> Microsoft recommends that you use roles with the fewest permissions. Using lower permissioned accounts helps improve security for your organization. Global Administrator is a highly privileged role that should be limited to emergency scenarios when you can't use an existing role.
52
52
53
53
1. In the Teams admin center at <https://admin.teams.microsoft.com>, go to **Messaging policies**. Or, to go directly to the **Messaging policies** page, use <https://admin.teams.microsoft.com/policies/messaging>.
Copy file name to clipboardExpand all lines: defender-xdr/pilot-deploy-defender-endpoint.md
+7-8Lines changed: 7 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,15 +18,14 @@ ms.collection:
18
18
- zerotrust-solution
19
19
- highpri
20
20
- tier1
21
-
ms.topic: conceptual
21
+
ms.topic: concept-article
22
+
appliesto:
23
+
- Microsoft Defender XDR
24
+
#customer intent: To learn how to pilot and deploy Microsoft Defender for Endpoint in your production Microsoft 365 tenant.
22
25
---
23
26
24
27
# Pilot and deploy Microsoft Defender for Endpoint
25
28
26
-
**Applies to:**
27
-
28
-
- Microsoft Defender XDR
29
-
30
29
This article provides a workflow for piloting and deploying Microsoft Defender for Endpoint in your organization. You can use these recommendations to onboard Microsoft Defender for Endpoint as an individual cybersecurity tool or as part of an end-to-end solution with Microsoft Defender XDR.
31
30
32
31
This article assumes you have a production Microsoft 365 tenant and are piloting and deploying Microsoft Defender for Endpoint in this environment. This practice will maintain any settings and customizations you configure during your pilot for your full deployment.
@@ -47,17 +46,17 @@ The articles in this series correspond to the following phases of end-to-end dep
47
46
| B. Pilot and deploy Microsoft Defender XDR components | - [Pilot and deploy Defender for Identity](pilot-deploy-defender-identity.md) <br><br> - [Pilot and deploy Defender for Office 365](pilot-deploy-defender-office-365.md) <br><br> - **Pilot and deploy Defender for Endpoint** (this article) <br><br> - [Pilot and deploy Microsoft Defender for Cloud Apps](pilot-deploy-defender-cloud-apps.md)|
48
47
|C. Investigate and respond to threats |[Practice incident investigation and response](pilot-deploy-investigate-respond.md)|
49
48
50
-
## Pilot and deploy workflow for Defender for Identity
49
+
## Pilot and deploy workflow for Defender for Endpoint
51
50
52
51
The following diagram illustrates a common process to deploy a product or service in an IT environment.
53
52
54
53
:::image type="content" source="./media/eval-defender-xdr/adoption-phases.svg" alt-text="Diagram of the pilot, evaluate, and full deployment adoption phases." lightbox="./media/eval-defender-xdr/adoption-phases.svg":::
55
54
56
55
You start by evaluating the product or service and how it will work within your organization. Then, you pilot the product or service with a suitably small subset of your production infrastructure for testing, learning, and customization. Then, gradually increase the scope of the deployment until your entire infrastructure or organization is covered.
57
56
58
-
Here is the workflow for piloting and deploying Defender for Identity in your production environment.
57
+
Here is the workflow for piloting and deploying Defender for Endpoint in your production environment.
59
58
60
-
:::image type="content" source="./media/eval-defender-xdr/defender-identity-pilot-deploy-steps.svg" alt-text="A diagram that shows the steps to pilot and deploy Microsoft Defender for Identity." lightbox="./media/eval-defender-xdr/defender-identity-pilot-deploy-steps.svg" border="false":::
59
+
:::image type="content" source="./media/eval-defender-xdr/defender-endpoint-pilot-deploy-steps.png" alt-text="A diagram that shows the steps to pilot and deploy Microsoft Defender for Endpoint." lightbox="./media/eval-defender-xdr/defender-endpoint-pilot-deploy-steps.png" border="false":::
Copy file name to clipboardExpand all lines: unified-secops-platform/criteria.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ ms.collection:
12
12
- m365-security
13
13
- tier2
14
14
ms.topic: conceptual
15
-
ms.date: 10/30/2024
15
+
ms.date: 03/13/2025
16
16
search.appverid: met150
17
17
---
18
18
@@ -219,4 +219,4 @@ Vulnerable software is an application or code that has security flaws or weaknes
219
219
220
220
### Vulnerable drivers
221
221
222
-
Despite strict requirements and reviews imposed on code running in kernel, device drivers remain susceptible to various types of vulnerabilities and bugs. Examples include memory corruption and arbitrary read and write bugs, which can be exploited by attackers to execute more significant malicious and destructive actions -– actions typically restricted in user mode. Terminating critical processes on a device is an example of such malicious action.
222
+
Despite strict requirements and reviews imposed on code running in kernel, device drivers remain susceptible to various types of vulnerabilities and bugs , including intentional design oversights that undermine the security promise of the operating system . Examples include memory corruption and arbitrary read and write bugs, which can be exploited by attackers to execute more significant malicious and destructive actions -– actions typically restricted in user mode. Terminating critical processes on a device is an example of such malicious action.
0 commit comments