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
+48-46Lines changed: 48 additions & 46 deletions
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: conceptual
16
16
ms.subservice: android
17
17
search.appverid: met150
18
-
ms.date: 04/30/2024
18
+
ms.date: 08/26/2024
19
19
---
20
20
21
21
# Configure Defender for Endpoint on Android features
@@ -59,62 +59,54 @@ It includes several admin controls to offer flexibility, such as the ability to
59
59
60
60
Network protection in Microsoft Defender for endpoint is disabled by default. Admins can use the following steps to **configure Network protection in Android devices.**
61
61
62
-
1.In the Microsoft Intune admin center, navigate to Apps > App configuration policies. Create a new App configuration policy.
62
+
In the Microsoft Intune admin center, navigate to Apps > App configuration policies. Create a new App configuration policy.
63
63
64
-
> [!div class="mx-imgBorder"]
65
64
1. Provide a name and description to uniquely identify the policy. Select **'Android Enterprise'** as the platform and **'Personally-owned work profile only'** as the profile type and **'Microsoft Defender'** as the Targeted app.
66
65
67
-
> [!div class="mx-imgBorder"]
68
-
> 
69
-
70
-
1. In Settings page, select **'Use configuration designer'** and add **'Enable Network Protection in Microsoft Defender'** as the key and value as **'1'** to enable Network Protection. (Network protection is disabled by default)
66
+
2. In Settings page, select **'Use configuration designer'** and add **'Enable Network Protection in Microsoft Defender'** as the key and value as **'0'** to disable Network Protection. (Network protection is enabled by default)
71
67
72
-
> [!div class="mx-imgBorder"]
73
-
> 
74
-
75
-
> [!div class="mx-imgBorder"]
76
-
> 
77
-
78
-
1. If your organization uses root CAs that are private, you must establish explicit trust between Intune (MDM solution) and user devices. Establishing trust helps prevent Defender from flagging root CAs as rogue certificates.
68
+
3. If your organization uses root CAs that are private, you must establish explicit trust between Intune (MDM solution) and user devices. Establishing trust helps prevent Defender from flagging root CAs as rogue certificates.
79
69
80
70
To establish trust for the root CAs, use **'Trusted CA certificate list for Network Protection'** as the key. In the value, add the **'comma separated list of certificate thumbprints (SHA 1)'**.
81
71
82
72
**Example of Thumbprint format to add**: `50 30 06 09 1d 97 d4 f5 ae 39 f7 cb e7 92 7d 7d 65 2d 34 31, 503006091d97d4f5ae39f7cbe7927d7d652d3431`
83
73
84
74
> [!IMPORTANT]
85
-
> Certificate SHA-1 Thumbprint characters should be with either white space separated, or non separated.
86
-
>
87
-
> This format is invalid: `50:30:06:09:1d:97:d4:f5:ae:39:f7:cb:e7:92:7d:7d:65:2d:34:31`
75
+
> Certificate SHA-1 Thumbprint characters should be with either white space separated, or non separated.
76
+
>
77
+
> This format is invalid: `50:30:06:09:1d:97:d4:f5:ae:39:f7:cb:e7:92:7d:7d:65:2d:34:31`
88
78
89
79
Any other separation characters are invalid.
90
80
91
-
1. For other configurations related to Network protection, add the following keys and appropriate corresponding value.
92
-
93
-
| Configuration Key| Description|
94
-
|---|---|
95
-
|Trusted CA certificate list for Network Protection|Security admins manage this setting to establish trust for root CA and self-signed certificates.|
96
-
|Enable Network protection in Microsoft Defender|1 - Enable, 0- Disable (default). This setting is used by the IT admin to enable or disable the network protection capabilities in the Defender app.|
97
-
|Enable Network Protection Privacy|1 - Enable (default), 0 - Disable. Security admins manage this setting to enable or disable privacy in network protection.|
98
-
|Enable Users to Trust Networks and Certificates|1 - Enable, 0 - Disable (default). Security admins manage this setting to enable or disable the end user's in-app experience to trust and untrust unsecure and suspicious networks and malicious certificates.|
99
-
|Automatic Remediation of Network Protection Alerts|1 - Enable (default), 0 - Disable. Security admins manage this setting to enable or disable the remediation alerts that are sent when a user performs remediation activities, such as switching to a safer Wi-Fi access point or deleting suspicious certificates detected by Defender.|
100
-
|Manage Network Protection detection for Open Networks|0 - Disable (default), 1- Audit Mode, 2 - Enable. Security admins manage this setting to disable, audit, or enable open network detection, respectively. In 'Audit' mode, alerts are sent only to the ATP portal with no end user experience. For user experience, set the config to 'Enable' mode.|
101
-
|Manage Network protection Detection for Certificates|0 - Disable, 1- Audit mode (default), 2 - Enable. When network protection is enabled, Audit mode for certificate detection is enabled by default. In Audit mode, notification alerts are sent to SOC admins, but no end-user notifications are displayed to the user when Defender detects a bad certificate. Admins can, however, disable this detection with 0 as the value and enable full feature functionality by setting 2 as the value. When the feature is enabled with the value of 2, end-user notifications are sent to the user when Defender detects a bad certificate, and alerts are also sent to the SOC Admin.|
102
-
103
-
6. Add the required groups to which the policy will have to be applied. Review and create the policy.
104
-
105
-
| Configuration Key| Description|
106
-
|---|---|
107
-
|Enable Network protection in Microsoft Defender|1: Enable <br/> 0: Disable (default) <br/><br/> This setting is used by the IT admin to enable or disable the network protection capabilities in the Defender app.|
108
-
|Enable Network Protection Privacy|1: Enable (default) <br/> 0: Disable <br/><br/> Security admins manage this setting to enable or disable privacy in network protection.|
109
-
|Enable Users to Trust Networks and Certificates|1 <br/> Enable <br/> 0:Disable (default) <br/><br/> This setting is used by IT admins to enable or disable the end user in-app experience to trust and untrust the unsecure and suspicious networks and malicious certificates.|
110
-
|Automatic Remediation of Network Protection Alerts|1: Enable (default) <br/> 0: Disable <br/><br/> This setting is used by IT admins to enable or disable the remediation alerts that are sent when a user does remediation activities. For example, the user switches to a safer Wi-Fi access point or deletes suspicious certificates that were detected by Defender.|
111
-
|Manage Network Protection detection for Open Networks|0: Disable (default)<br/> 1: Audit Mode <br/><br/> Security admins manage this setting to enable or disable open network detection.|
112
-
|Manage Network protection Detection for Certificates|0: Disable <br/> 1: Audit mode (default) <br/> 2: Enable <br/><br/> When network protection is enabled, Audit mode for certificate detection is enabled by default. In audit mode, notification alerts are sent to SOC admins, but no end user notifications are shown when Defender detects a bad certificate. Admins can disable this detection with the value 0 or enable full feature functionality by setting the value 2. When the value is 2, end user notifications are sent to users and alerts are sent to SOC admins when Defender detects a bad certificate.|
113
-
114
-
1. Add the required groups to which the policy has to be applied. Review and create the policy.
81
+
4. For other configurations related to Network protection, add the following keys and appropriate corresponding value.
82
+
83
+
| Configuration Key| Description|
84
+
|---|---|
85
+
|Trusted CA certificate list for Network Protection|Security admins manage this setting to establish trust for root CA and self-signed certificates.|
86
+
|Enable Network protection in Microsoft Defender|1 - Enable (default), 0- Disable. This setting is used by the IT admin to enable or disable the network protection capabilities in the Defender app.|
87
+
|Enable Network Protection Privacy|1 - Enable (default), 0 - Disable. Security admins manage this setting to enable or disable privacy in network protection.|
88
+
|Enable Users to Trust Networks and Certificates|1 - Enable, 0 - Disable (default). Security admins manage this setting to enable or disable the end user's in-app experience to trust and untrust unsecure and suspicious networks and malicious certificates.|
89
+
|Automatic Remediation of Network Protection Alerts|1 - Enable (default), 0 - Disable. Security admins manage this setting to enable or disable the remediation alerts that are sent when a user performs remediation activities, such as switching to a safer Wi-Fi access point or deleting suspicious certificates detected by Defender.|
90
+
|Manage Network Protection detection for Open Networks|2- Enable (default), 1- Audit mode, 0 - Disable. Security admins manage this setting to enable, audit, or disable open network detection, respectively. In 'Audit' mode, alerts are sent only to the ATP portal with no end user experience. For end user experience, the config should be set to 'Enable' mode.|
91
+
|Manage Network protection Detection for Certificates|2- Enable, 1- Audit mode, 0 - Disable (default). In Audit mode, notification alerts are sent to SOC admins, but no end-user notifications are displayed to the user when Defender detects a bad certificate. Admins can, however, enable full feature functionality by setting 2 as the value. When the feature is enabled with the value of 2, end-user notifications are sent to the user when Defender detects a bad certificate, and alerts are also sent to the SOC Admin.|
92
+
93
+
5. Add the required groups to which the policy will have to be applied. Review and create the policy.
94
+
95
+
| Configuration Key| Description|
96
+
|---|---|
97
+
|Enable Network protection in Microsoft Defender|1: Enable (default)<br/> 0: Disable<br/><br/> This setting is used by the IT admin to enable or disable the network protection capabilities in the Defender app.|
98
+
|Enable Network Protection Privacy|1: Enable (default) <br/> 0: Disable <br/><br/> Security admins manage this setting to enable or disable privacy in network protection.|
99
+
|Enable Users to Trust Networks and Certificates|1: Enable <br/>0: Disable (default) <br/><br/> This setting is used by IT admins to enable or disable the end user in-app experience to trust and untrust the unsecure and suspicious networks and malicious certificates.|
100
+
|Automatic Remediation of Network Protection Alerts|1: Enable (default) <br/> 0: Disable <br/><br/> This setting is used by IT admins to enable or disable the remediation alerts that are sent when a user does remediation activities. For example, the user switches to a safer Wi-Fi access point or deletes suspicious certificates that were detected by Defender.|
101
+
|Manage Network Protection detection for Open Networks| 2: Enable (default)<br/> 1: Audit Mode <br/> 0: Disable <br/> Security admins manage this setting to enable or disable open network detection.|
102
+
|Manage Network protection Detection for Certificates|2: Enable <br/> 1: Audit mode<br/> 0: Disable (default)<br/><br/>In audit mode, notification alerts are sent to SOC admins, but no end user notifications are shown when Defender detects a bad certificate. Admins can enable full feature functionality by setting the value 2. When the value is 2, end user notifications are sent to users and alerts are sent to SOC admins when Defender detects a bad certificate.|
103
+
104
+
6. Add the required groups to which the policy has to be applied. Review and create the policy.
115
105
116
106
> [!NOTE]
117
-
> Users need to enable location permission (which is an optional permission); this enables Defender for Endpoint to scan their networks and alert them when there are WIFI-related threats. If the location permission is denied by the user, Defender for Endpoint will only be able to provide limited protection against network threats and will only protect the users from rogue certificates.
107
+
> - The other config keys of Network Protection will only work if the parent key '**Enable Network Protection in Microsoft Defender'** is enabled.
108
+
> - Users need to enable location permission (which is an optional permission) and need to grant “Allow All the Time” permission to ensure protection against Wi-Fi threat, even when the app is not actively in use. If the location permission is denied by the user, Defender for Endpoint will only be able to provide limited protection against network threats and will only protect the users from rogue certificates.
109
+
118
110
## Privacy Controls
119
111
120
112
Following privacy controls are available for configuring the data that is sent by Defender for Endpoint from Android devices:
@@ -124,7 +116,7 @@ Following privacy controls are available for configuring the data that is sent b
124
116
|Malware report |Admins can set up privacy control for malware report. If privacy is enabled, then Defender for Endpoint won't send the malware app name and other app details as part of the malware alert report. |
125
117
|Phish report |Admins can set up privacy control for phishing reports. If privacy is enabled, then Defender for Endpoint won't send the domain name and details of the unsafe website as part of the phishing alert report. |
126
118
|Vulnerability assessment of apps |By default only information about apps installed in the work profile is sent for vulnerability assessment. Admins can disable privacy to include personal apps|
127
-
|Network Protection (preview)| Admins can enable or disable privacy in network protection. If enabled, then Defender won't send network details.|
119
+
|Network Protection | Admins can enable or disable privacy in network protection. If enabled, then Defender won't send network details.|
128
120
129
121
### Configure privacy alert report
130
122
@@ -140,7 +132,7 @@ Admin Privacy Controls (MDM) Use the following steps to enable privacy.
140
132
141
133
4. On the Settings page, select **Use configuration designer** and then select **Add**.
142
134
143
-
5. Select the required privacy setting -
135
+
5. Select the required privacy setting
144
136
- Hide URLs in report
145
137
- Hide URLs in report for personal profile
146
138
- Hide app details in report
@@ -206,8 +198,10 @@ Defender for Endpoint supports vulnerability assessment of apps in the work prof
206
198
2. Give the policy a name; **Platform \> Android Enterprise**; select the profile type.
207
199
3. Select **Microsoft Defender for Endpoint** as the target app.
208
200
4. In Settings page, select **Use configuration designer** and add **DefenderTVMPrivacyMode** as the key and value type as **Integer**
201
+
209
202
- To disable vulnerability of apps in the work profile, enter value as `1` and assign this policy to users. By default, this value is set to `0`.
210
203
- For users with key set as `0`, Defender for Endpoint sends the list of apps from the work profile to the backend service for vulnerability assessment.
204
+
211
205
5. Select **Next** and assign this profile to targeted devices/users.
212
206
213
207
Turning the above privacy controls on or off won't impact the device compliance check or conditional access.
@@ -246,7 +240,9 @@ Use the following steps to turn on privacy for targeted users in the work profil
246
240
2. Give the policy a name, **Platform > Android Enterprise**, select the profile type.
247
241
3. Select **Microsoft Defender for Endpoint** as the target app.
248
242
4. In Settings page, select **Use configuration designer** and add **DefenderExcludeURLInReport** as the key and value type as **Integer**.
249
-
- Enter **1 to enable privacy**. The default value is 0.
243
+
244
+
Enter **1 to enable privacy**. The default value is 0.
245
+
250
246
5. Select **Next** and assign this profile to targeted devices/users.
251
247
252
248
Turning the above privacy controls on or off won't impact the device compliance check or conditional access.
@@ -285,7 +281,9 @@ Use the following steps to turn on privacy for targeted users in the work profil
285
281
2. Give the policy a name, **Platform > Android Enterprise**, select the profile type.
286
282
3. Select **Microsoft Defender for Endpoint** as the target app.
287
283
4. In Settings page, select **Use configuration designer** and add **DefenderExcludeAppInReport** as the key and value type as **Integer**
288
-
- Enter **1 to enable privacy**. The default value is 0.
284
+
285
+
Enter **1 to enable privacy**. The default value is 0.
286
+
289
287
5. Select **Next** and assign this profile to targeted devices/users.
290
288
291
289
Using this privacy control won't impact the device compliance check or conditional access. For example, devices with a malicious app will always have a risk level of "Medium".
@@ -299,8 +297,10 @@ Use the following steps to configure Disable sign-out:
299
297
2. Give the policy a name, select **Platform > Android Enterprise**, and select the profile type.
300
298
3. Select **Microsoft Defender for Endpoint** as the target app.
301
299
4. In the Settings page, select **Use configuration designer** and add **Disable Sign Out** as the key and **Integer** as the value type.
300
+
302
301
- By default, Disable Sign Out = 1 for Android Enterprise personally owned work profiles, fully managed, company owned personally enabled profiles and 0 for device administrator mode.
303
302
- Admins need to make Disable Sign Out = 0 to enable the sign-out button in the app. Users will be able to see the sign-out button once the policy is pushed.
303
+
304
304
5. Select **Next** and assign this profile to targeted devices and users.
305
305
306
306
> [!IMPORTANT]
@@ -316,6 +316,7 @@ Use the following steps to configure the Device tags:
316
316
2. Give the policy a name, select **Platform > Android Enterprise**, and select the profile type.
317
317
3. Select **Microsoft Defender for Endpoint** as the target app.
318
318
4. In Settings page, select Use configuration designer and add **DefenderDeviceTag** as the key and value type as **String**.
319
+
319
320
- Admin can assign a new tag by adding the key **DefenderDeviceTag** and setting a value for device tag.
320
321
- Admin can edit an existing tag by modifying the value of the key **DefenderDeviceTag**.
321
322
- Admin can delete an existing tag by removing the key **DefenderDeviceTag**.
@@ -325,6 +326,7 @@ Use the following steps to configure the Device tags:
325
326
326
327
> [!NOTE]
327
328
> The Defender app needs to be opened for tags to be synced with Intune and passed to Security Portal. It may take up to 18 hours for tags to reflect in the portal.
329
+
328
330
## Related articles
329
331
330
332
-[Overview of Microsoft Defender for Endpoint on Android](microsoft-defender-endpoint-android.md)
0 commit comments