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/monitored-activities.md
+12-10Lines changed: 12 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,18 +14,20 @@ In the case of a valid threat, or **true positive**, Defender for Identity enabl
14
14
The information monitored by Defender for Identity is presented in the form of activities. Defender for Identity currently supports monitoring of the following activity types:
15
15
16
16
> [!NOTE]
17
-
>
18
17
> - This article is relevant for all Defender for Identity sensor types.
19
18
> - Defender for Identity monitored activities appear on both the user and machine profile page.
20
-
> - Defender for Identity monitored activities are also available in Microsoft Defender XDR's [Advanced Hunting](https://security.microsoft.com/advanced-hunting) page.
19
+
> - Defender for Identity monitored activities are also available in [Microsoft Defender XDR's Advanced Hunting](/defender-xdr/advanced-hunting-overview) page.
20
+
21
+
> [!TIP]
22
+
> For detailed information on all supported event types (`ActionType` values) in Advanced Hunting Identity-related tables, use the built-in schema reference available in Microsoft Defender XDR.
21
23
22
24
## Monitored user activities: User account AD attribute changes
23
25
24
26
|Monitored activity|Description|
25
27
|---------------------|------------------|
26
28
|Account Constrained Delegation State Changed|The account state is now enabled or disabled for delegation.|
27
29
|Account Constrained Delegation SPNs Changed|Constrained delegation restricts the services to which the specified server can act on behalf of the user.|
28
-
|Account Delegation Changed | Changes to the account delegation settings |
30
+
|Account Delegation Changed | Changes to the account delegation settings.|
29
31
|Account Disabled Changed|Indicates whether an account is disabled or enabled.|
30
32
|Account Expired|Date when the account expires.|
31
33
|Account Expiry Time Changed|Change to the date when the account expires.|
@@ -35,9 +37,9 @@ The information monitored by Defender for Identity is presented in the form of a
35
37
|Account Password Never Expires Changed|User's password changed to never expire.|
36
38
|Account Password Not Required Changed|User account was changed to allow logging in with a blank password.|
37
39
|Account Smartcard Required Changed|Account changes to require users to log on to a device using a smart card.|
Copy file name to clipboardExpand all lines: defender-endpoint/android-configure.md
+16-16Lines changed: 16 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,7 +49,7 @@ Defender for Endpoint on Android allows IT Administrators the ability to configu
49
49
[Web protection](web-protection-overview.md) helps to secure devices against web threats and protect users from phishing attacks. Anti-phishing and custom indicators (URL and IP addresses) are supported as part of web protection. Web content filtering is currently not supported on mobile platforms.
50
50
51
51
> [!NOTE]
52
-
> Defender for Endpoint on Android would use a VPN in order to provide the Web Protection feature. This VPN is not a regular VPN. Instead, it's a local/self-looping VPN that does not take traffic outside the device.
52
+
> Defender for Endpoint on Android would use a VPN in order to provide the Web Protection feature. This VPN isn't a regular VPN. Instead, it's a local/self-looping VPN that doesn't take traffic outside the device.
53
53
>
54
54
> For more information, see [Configure web protection on devices that run Android](/mem/intune/protect/advanced-threat-protection-manage-android).
55
55
@@ -92,7 +92,7 @@ In the Microsoft Intune admin center, navigate to Apps > App configuration polic
92
92
|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.|
93
93
|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. |
94
94
95
-
5. Add the required groups to which the policy will have to be applied. Review and create the policy.
95
+
5. Add the required groups to which the policy has to be applied. Review and create the policy.
96
96
97
97
| Configuration Key| Description|
98
98
|---|---|
@@ -106,9 +106,9 @@ In the Microsoft Intune admin center, navigate to Apps > App configuration polic
106
106
6. Add the required groups to which the policy has to be applied. Review and create the policy.
107
107
108
108
> [!NOTE]
109
-
>
110
109
> - The other config keys of Network Protection will only work if the parent key '**Enable Network Protection in Microsoft Defender'** is enabled.
111
-
> - 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.
110
+
> - 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.
111
+
**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
112
113
113
## Privacy Controls
114
114
@@ -156,7 +156,7 @@ These controls help the end user to configure the information shared to their or
156
156
157
157
These toggles will only be visible if enabled by the admin. Users can decide if they want to send the information to their organization or not.
158
158
159
-
Enabling/disabling the above privacy controls won't impact the device compliance check or conditional access.
159
+
Enabling/disabling the above privacy controls won't affect the device compliance check or conditional access.
160
160
161
161
## Configure vulnerability assessment of apps for BYOD devices
162
162
@@ -207,7 +207,7 @@ Defender for Endpoint supports vulnerability assessment of apps in the work prof
207
207
208
208
5. Select **Next** and assign this profile to targeted devices/users.
209
209
210
-
Turning the above privacy controls on or off won't impact the device compliance check or conditional access.
210
+
Turning the above privacy controls on or off won't affect the device compliance check or conditional access.
211
211
212
212
## Configure privacy for phishing alert report
213
213
@@ -233,7 +233,7 @@ Use the following steps to turn it on for targeted users:
233
233
234
234
4. Select **Next** and assign this profile to targeted devices/users.
235
235
236
-
Using this privacy control won't impact the device compliance check or conditional access.
236
+
Using this privacy control won't affect the device compliance check or conditional access.
237
237
238
238
### Configure privacy for phishing alert report on Android Enterprise work profile
239
239
@@ -248,7 +248,7 @@ Use the following steps to turn on privacy for targeted users in the work profil
248
248
249
249
5. Select **Next** and assign this profile to targeted devices/users.
250
250
251
-
Turning the above privacy controls on or off won't impact the device compliance check or conditional access.
251
+
Turning the above privacy controls on or off won't affect the device compliance check or conditional access.
252
252
253
253
## Configure privacy for malware threat report
254
254
@@ -274,7 +274,7 @@ Use the following steps to turn it on for targeted users:
274
274
275
275
4. Select **Next** and assign this profile to targeted devices/users.
276
276
277
-
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".
277
+
Using this privacy control won't affect the device compliance check or conditional access. For example, devices with a malicious app will always have a risk level of "Medium".
278
278
279
279
### Configure privacy for malware alert report on Android Enterprise work profile
280
280
@@ -289,20 +289,20 @@ Use the following steps to turn on privacy for targeted users in the work profil
289
289
290
290
5. Select **Next** and assign this profile to targeted devices/users.
291
291
292
-
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".
292
+
Using this privacy control won't affect the device compliance check or conditional access. For example, devices with a malicious app will always have a risk level of "Medium".
293
293
294
-
## Disable sign-out
294
+
## Disable signout
295
295
296
-
Defender for Endpoint supports deployment without the sign-out button in the app to prevent users from signing out of the Defender app. This is important to prevent users from tampering with the device.
297
-
Use the following steps to configure Disable sign-out:
296
+
Defender for Endpoint supports deployment without the signout button in the app to prevent users from signing out of the Defender app. This is important to prevent users from tampering with the device.
297
+
Use the following steps to configure Disable out sign:
298
298
299
299
1. In [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431), go to **Apps** > **App configuration policies** > **Add** > **Managed devices**.
300
300
2. Give the policy a name, select **Platform > Android Enterprise**, and select the profile type.
301
301
3. Select **Microsoft Defender for Endpoint** as the target app.
302
302
4. In the Settings page, select **Use configuration designer** and add **Disable Sign Out** as the key and **Integer** as the value type.
303
303
304
304
- 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.
305
-
- 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.
305
+
- Admins need to make Disable Sign Out = 0 to enable the signout button in the app. Users are able to see the signout button once the policy is pushed.
306
306
307
307
5. Select **Next** and assign this profile to targeted devices and users.
308
308
@@ -321,11 +321,11 @@ Use the following steps to configure the Device tags:
321
321
- Admin can edit an existing tag by modifying the value of the key **DefenderDeviceTag**.
322
322
- Admin can delete an existing tag by removing the key **DefenderDeviceTag**.
323
323
324
-
5.Click Next and assign this policy to targeted devices and users.
324
+
5.Select Next and assign this policy to targeted devices and users.
325
325
326
326
327
327
> [!NOTE]
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.
328
+
> The Defender app needs to be opened for tags to be synced with Intune and passed to Security Portal. It might take up to 18 hours for tags to reflect in the portal.
0 commit comments