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/api/device-health-api-methods-properties.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
@@ -50,7 +50,7 @@ Data that is collected using either '_JSON response_ or _via files_' is the curr
50
50
> [!IMPORTANT]
51
51
> For Windows Server 2012 R2 and Windows Server 2016 to appear in device health reports, these devices must be onboarded using the modern unified solution package. For more information, see [New functionality in the modern unified solution for Windows Server 2012 R2 and 2016](../configure-server-endpoints.md#functionality-in-the-modern-unified-solution).
52
52
>
53
-
> For information about using the **Device health and antivirus compliance** reporting tool in the Microsoft 365 Security dashboard, see: [Device health and antivirus report in Microsoft Defender for Endpoint](../device-health-reports.md).
53
+
> For information about using the **Device health and antivirus compliance** reporting tool in the Microsoft Defender portal, see: [Device health and antivirus report in Microsoft Defender for Endpoint](../device-health-reports.md).
54
54
55
55
### 1.1 Export device antivirus health details API methods
Copy file name to clipboardExpand all lines: defender-endpoint/api/device-health-export-antivirus-health-report-api.md
+2-8Lines changed: 2 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ ms.service: defender-endpoint
5
5
ms.author: siosulli
6
6
author: siosulli
7
7
ms.localizationpriority: medium
8
-
ms.date: 11/03/2022
8
+
ms.date: 06/25/2024
9
9
manager: deniseb
10
10
audience: ITPro
11
11
ms.collection:
@@ -46,19 +46,13 @@ This API has two methods to retrieve Microsoft Defender Antivirus device antivir
46
46
47
47
Data that is collected using either '_JSON response_ or _via files_' is the current snapshot of the current state. It doesn't contain historic data. To collect historic data, customers must save the data in their own data storages. See [Export device health details API methods and properties](device-health-api-methods-properties.md).
48
48
49
-
> [!IMPORTANT]
50
-
>
51
-
> Currently, only the **Antivirus Health JSON Response** is generally available. **Antivirus Health API via files** is currently only available in public preview.
52
-
>
53
-
> **Advanced Hunting custom query** is currently only available in public preview, even if the queries are still visible.
54
-
55
49
> [!IMPORTANT]
56
50
>
57
51
> For Windows Server 2012 R2 and Windows Server 2016 to appear in device health reports, these devices must be onboarded using the modern unified solution package. For more information, see [New functionality in the modern unified solution for Windows Server 2012 R2 and 2016](../configure-server-endpoints.md#functionality-in-the-modern-unified-solution).
58
52
59
53
> [!NOTE]
60
54
>
61
-
> For information about using the **Device health and antivirus compliance** reporting tool in the Microsoft 365 Security dashboard, see: [Device health and antivirus compliance report in Microsoft Defender for Endpoint](../device-health-reports.md).
55
+
> For information about using the **Device health and antivirus compliance** reporting tool in the Microsoft Defender portal, see: [Device health and antivirus compliance report in Microsoft Defender for Endpoint](../device-health-reports.md).
Copy file name to clipboardExpand all lines: defender-endpoint/device-health-reports.md
+16-5Lines changed: 16 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ ms.service: defender-endpoint
6
6
ms.author: siosulli
7
7
author: siosulli
8
8
ms.localizationpriority: medium
9
-
ms.date: 09/06/2022
9
+
ms.date: 06/25/2024
10
10
manager: deniseb
11
11
audience: ITPro
12
12
ms.collection:
@@ -32,9 +32,9 @@ ms.reviewer: mkaminska
32
32
The Device Health report provides information about the devices in your organization. The report includes trending information showing the sensor health state, antivirus status, OS platforms, Windows 10 versions, and Microsoft Defender Antivirus update versions.
33
33
34
34
> [!IMPORTANT]
35
-
> For Windows Server 2012 R2 and Windows Server 2016 to appear in device health reports, these devices must be onboarded using the modern unified solution package. For more information, see [New functionality in the modern unified solution for Windows Server 2012 R2 and 2016](configure-server-endpoints.md#functionality-in-the-modern-unified-solution).
35
+
> For WindowsServer2012R2 and WindowsServer2016 to appear in device health reports, these devices must be onboarded using the modern unified solution package. For more information, see [New functionality in the modern unified solution for Windows Server 2012 R2 and 2016](configure-server-endpoints.md#functionality-in-the-modern-unified-solution).
36
36
37
-
In the Microsoft 365 Security dashboard navigation panel, select **Reports**, and then open **Device health and compliance**.
37
+
In the Microsoft Defender portal navigation panel, select **Reports**, and then open **Device health and compliance**.
38
38
The Device health and compliance dashboard is structured in two tabs:
39
39
40
40
- The [**Sensor health & OS** tab](device-health-sensor-health-os.md#sensor-health--os-tab) provides general operating system information, divided into three cards that display the following device attributes:
@@ -54,20 +54,30 @@ The Device health and compliance dashboard is structured in two tabs:
54
54
55
55
## Report access permissions
56
56
57
-
To access the Device health and antivirus compliance report in the Microsoft 365 Security dashboard, the following permissions are required:
57
+
To access the Device health and antivirus compliance report in the Microsoft Defender portal, the following permissions are required:
58
58
59
59
| Permission name | Permission type |
60
60
|:---|:---|
61
61
| View Data | Threat and vulnerability management (TVM) |
62
62
63
+
> [!IMPORTANT]
64
+
> Microsoft recommends that you use roles with the fewest permissions. This 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.
65
+
66
+
63
67
To Assign these permissions:
64
68
65
-
1. Sign in to <ahref="https://go.microsoft.com/fwlink/p/?linkid=2077139"target="_blank">Microsoft Defender XDR</a> using account with Security administrator or Global administrator role assigned.
69
+
1. Sign in to the <ahref="https://go.microsoft.com/fwlink/p/?linkid=2077139"target="_blank">Microsoft Defender portal</a> using account with Security administrator or Global administrator role assigned.
70
+
66
71
1. In the navigation pane, select **Settings**\>**Endpoints**\>**Roles** (under **Permissions**).
72
+
67
73
1. Select the role you'd like to edit.
74
+
68
75
1. Select **Edit**.
76
+
69
77
1. In **Edit role**, on the **General** tab, in **Role name**, type a name for the role.
78
+
70
79
1. In **Description** type a brief summary of the role.
80
+
71
81
1. In **Permissions**, select **View Data**, and under **View Data** select **Threat and vulnerability management** (TVM).
72
82
73
83
## See also
@@ -92,4 +102,5 @@ To Assign these permissions:
92
102
93
103
-[Create and manage roles for role-based access control](user-roles.md).
94
104
-[Export device antivirus health details API methods and properties](api/device-health-api-methods-properties.md)
105
+
95
106
[!INCLUDE [Microsoft Defender for Endpoint Tech Community](../includes/defender-mde-techcommunity.md)]
Copy file name to clipboardExpand all lines: defender-endpoint/device-health-sensor-health-os.md
+17-5Lines changed: 17 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,9 +32,9 @@ ms.reviewer: mkaminska
32
32
The Device Health report provides information about the devices in your organization. The report includes trending information showing the sensor health state, antivirus status, OS platforms, Windows 10 versions, and Microsoft Defender Antivirus update versions.
33
33
34
34
> [!IMPORTANT]
35
-
> For Windows Server 2012 R2 and Windows Server 2016 to appear in device health reports, these devices must be onboarded using the modern unified solution package. For more information, see [New functionality in the modern unified solution for Windows Server 2012 R2 and 2016](configure-server-endpoints.md#functionality-in-the-modern-unified-solution).
35
+
> For WindowsServer2012R2 and WindowsServer2016 to appear in device health reports, these devices must be onboarded using the modern unified solution package. For more information, see [New functionality in the modern unified solution for Windows Server 2012 R2 and 2016](configure-server-endpoints.md#functionality-in-the-modern-unified-solution).
36
36
37
-
In the Microsoft 365 Security dashboard navigation panel, select **Reports**, and then open **Device health and compliance**.
37
+
In the Microsoft Defender portalnel, select **Reports**, and then open **Device health and compliance**.
38
38
39
39
- The [**Sensor health & OS** tab](#sensor-health--os-tab) provides general operating system information, divided into three cards that display the following device attributes:
40
40
-[Sensor health card](#sensor-health-card)
@@ -43,20 +43,29 @@ In the Microsoft 365 Security dashboard navigation panel, select **Reports**, an
43
43
44
44
## Report access permissions
45
45
46
-
To access the Device health and antivirus compliance report in the Microsoft 365 Security dashboard, the following permissions are required:
46
+
To access the Device health and antivirus compliance report in the Microsoft Defender portal, the following permissions are required:
47
47
48
48
| Permission name | Permission type |
49
49
|:---|:---|
50
50
| View Data | Threat and vulnerability management (TVM) |
51
51
52
-
To Assign these permissions:
52
+
> [!IMPORTANT]
53
+
> Microsoft recommends that you use roles with the fewest permissions. This 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.
54
+
55
+
To assign these permissions:
56
+
57
+
1. Sign in to the <ahref="https://go.microsoft.com/fwlink/p/?linkid=2077139"target="_blank">Microsoft Defender portal</a> using account with Security administrator or Global administrator role assigned.
53
58
54
-
1. Sign in to <ahref="https://go.microsoft.com/fwlink/p/?linkid=2077139"target="_blank">Microsoft Defender XDR</a> using account with Security administrator or Global administrator role assigned.
55
59
1. In the navigation pane, select **Settings**\>**Endpoints**\>**Roles** (under **Permissions**).
60
+
56
61
1. Select the role you'd like to edit.
62
+
57
63
1. Select **Edit**.
64
+
58
65
1. In **Edit role**, on the **General** tab, in **Role name**, type a name for the role.
66
+
59
67
1. In **Description** type a brief summary of the role.
68
+
60
69
1. In **Permissions**, select **View Data**, and under **View Data** select **Threat and vulnerability management** (TVM).
61
70
62
71
For more information about user role management, see [Create and manage roles for role-based access control](user-roles.md).
@@ -89,7 +98,9 @@ Use the provided filters to include or exclude devices with certain attributes.
89
98
For example, to show data about Windows 10 devices with Active sensor health state:
90
99
91
100
1. Under **Filters** > **Sensor health state** > **Active**.
101
+
92
102
2. Then select **OS platforms** > **Windows 10**.
103
+
93
104
3. Select **Apply**.
94
105
95
106
### Sensor health card
@@ -144,4 +155,5 @@ The Windows version trend graph can help you quickly determine whether your orga
Copy file name to clipboardExpand all lines: defender-endpoint/manage-security-policies.md
+12-21Lines changed: 12 additions & 21 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
- tier2
13
13
ms.topic: how-to
14
14
search.appverid: met150
15
-
ms.date: 05/06/2024
15
+
ms.date: 06/25/2024
16
16
---
17
17
18
18
# Manage endpoint security policies in Microsoft Defender for Endpoint
@@ -26,12 +26,15 @@ ms.date: 05/06/2024
26
26
-[Microsoft Defender XDR](/defender-xdr)
27
27
28
28
29
-
Use security policies to manage security settings on devices. As a security administrator, you can configure security policy settings in Microsoft Defender XDR.
29
+
Use security policies to manage security settings on devices. As a Security Administrator, you can configure security policy settings in the Microsoft Defender portal.
> Microsoft recommends that you use roles with the fewest permissions. This 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.
> The **Endpoint Security Policies** page in Microsoft Defender XDR is available only for [users with the security administrator role in Microsoft Defender XDR](assign-portal-access.md). Any other user role, such as Security Reader, cannot access the portal. When a user has the required permissions to view policies in the Microsoft Defender portal, the data is presented based on Intune permissions. If the user is in scope for Intune role-based access control, it applies to the list of policies presented in the Microsoft Defender portal. We recommend granting security administrators with the [Intune built-in role, "Endpoint Security Manager"](/mem/intune/fundamentals/role-based-access-control#built-in-roles) to effectively align the level of permissions between Intune and Microsoft Defender XDR.
37
+
> The **Endpoint Security Policies** page in the Microsoft Defender portal is available only for [users with the Security Administrator role assigned](assign-portal-access.md). Any other user role, such as Security Reader, cannot access the portal. When a user has the required permissions to view policies in the Microsoft Defender portal, the data is presented based on Intune permissions. If the user is in scope for Intune role-based access control, it applies to the list of policies presented in the Microsoft Defender portal. We recommend granting security administrators with the [Intune built-in role, "Endpoint Security Manager"](/mem/intune/fundamentals/role-based-access-control#built-in-roles) to effectively align the level of permissions between Intune and the Microsoft Defender portal.
35
38
36
39
:::image type="content" source="./media/endpoint-security-policies.png" alt-text="Managing Endpoint security policies in the Microsoft Defender portal":::
37
40
@@ -50,14 +53,10 @@ The following list provides a brief description of each endpoint security policy
50
53
51
54
## Create an endpoint security policy
52
55
53
-
>[!NOTE]
54
-
>Currently, only antivirus policies are supported.
55
-
56
-
1. Sign in to <ahref="https://go.microsoft.com/fwlink/p/?linkid=2077139"target="_blank">Microsoft Defender XDR</a> using at least a security admin role.
56
+
1. Sign in to the <ahref="https://go.microsoft.com/fwlink/p/?linkid=2077139"target="_blank">Microsoft Defender portal</a> using at least a Security Administrator role.
57
57
58
58
2. Select **Endpoints > Configuration management > Endpoint security policies** and then select **Create new Policy**.
59
59
60
-
61
60
3. Select a platform from the dropdown list.
62
61
63
62
4. Select a template, then select **Create policy**.
@@ -75,10 +74,8 @@ The following list provides a brief description of each endpoint security policy
75
74
76
75
8. On the **Review + create** page, when you're done, select **Save**. The new profile is displayed in the list when you select the policy type for the profile you created.
77
76
78
-
79
-
>[!NOTE]
80
-
>To edit the scope tags, you'll need to go to the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
81
-
77
+
> [!NOTE]
78
+
> To edit the scope tags, you'll need to go to the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
82
79
83
80
## To edit an endpoint security policy
84
81
@@ -93,25 +90,19 @@ The following list provides a brief description of each endpoint security policy
93
90
94
91
4. After you've made changes, select **Save** to save your edits. Edits to one category must be saved before you can introduce edits to additional categories.
95
92
96
-
97
-
98
-
99
93
## Verify endpoint security policies
100
94
101
95
To verify that you have successfully created a policy, select a policy name from the list of endpoint security policies.
102
96
103
-
>[!NOTE]
104
-
>It can take up to 90 minutes for a policy to reach a device. To expedite the process, for devices Managed by Defender for Endpoint, you can select **Policy sync** from the actions menu so that it is applied in approximately 10 minutes.
97
+
>[!NOTE]
98
+
>It can take up to 90 minutes for a policy to reach a device. To expedite the process, for devices Managed by Defender for Endpoint, you can select **Policy sync** from the actions menu so that it is applied in approximately 10 minutes.
The policy page displays details that summarize the status of the policy. You can view a policy's status, which devices it has been applied to, and assigned groups.
108
102
109
103
During an investigation, you can also view the **Security policies** tab in the device page to view the list of policies that are being applied to a particular device. For more information, see [Investigating devices](investigate-machines.md#security-policies).
110
104
111
-
112
105
:::image type="content" source="./media/security-policies-list.png" alt-text="Security policies tab with list of policies":::
113
106
114
107
115
-
116
-
117
108
[!INCLUDE [Microsoft Defender for Endpoint Tech Community](../includes/defender-mde-techcommunity.md)]
0 commit comments