Skip to content

Commit 56e299a

Browse files
committed
Add new account protection profile
1 parent 57e4dbf commit 56e299a

3 files changed

Lines changed: 73 additions & 12 deletions

File tree

memdocs/intune/protect/endpoint-security-account-protection-policy.md

Lines changed: 73 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,13 @@
11
---
22
# required metadata
33

4-
title: Manage attack account protection settings with endpoint security policies in Microsoft Intune | Microsoft Docs
5-
description: Configure and deploy policies for devices you manage with endpoint security account protection policy settings in Microsoft Endpoint Manager.
4+
title: Manage account protection settings with endpoint security policies in Microsoft Intune | Microsoft Docs
5+
description: Deploy policies for endpoint security account protection policies to devices you manage with in Microsoft Endpoint Manager.
66
keywords:
77
author: brenduns
88
ms.author: brenduns
99
manager: dougeby
10-
ms.date: 05/15/2020
10+
ms.date: 01/26/2022
1111
ms.topic: reference
1212
ms.service: microsoft-intune
1313
ms.subservice: protect
@@ -30,28 +30,89 @@ ms.reviewer: mattcall
3030

3131
# Account protection policy for endpoint security in Intune
3232

33-
Use Intune endpoint security policies for account protection to protect the identity and accounts of your users. The account protection policy is focused on settings for Windows Hello and Credential Guard, which is part of Windows identity and access management.
34-
35-
- *Windows Hello for Business* replaces passwords with strong two-factor authentication on PCs and mobile devices.
36-
- *Credential Guard* helps protect credentials and secrets that you use with your devices.
37-
38-
To learn more, see [Identity and access management](/windows/security/identity-protection/) in the Windows identity and access management documentation.
33+
Use Intune endpoint security policies for account protection to protect the identity and accounts of your users and manage the built-in group memberships on devices.
3934

4035
Find the endpoint security policies for Account protection under *Manage* in the **Endpoint security** node of the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
4136

4237
View [settings for account protection profiles](../protect/endpoint-security-asr-profile-settings.md).
4338

4439
## Prerequisites for Account protection profiles
4540

46-
- Windows 10 or Windows 11
41+
Devices must run Windows 10 or Windows 11.
4742

4843
## Account protection profiles
4944

5045
*Account protection profiles are in Preview*.
5146

52-
**Windows 10 profiles**:
47+
**Windows 10/11 profiles**:
48+
49+
- **Account protection** **(Preview)** – Settings for account protection policies help you protect user credentials.
50+
51+
The account protection policy is focused on settings for Windows Hello and Credential Guard, which is part of Windows identity and access management.
52+
53+
- *Windows Hello for Business* replaces passwords with strong two-factor authentication on PCs and mobile devices.
54+
- *Credential Guard* helps protect credentials and secrets that you use with your devices.
55+
56+
To learn more, see [Identity and access management](/windows/security/identity-protection/) in the Windows identity and access management documentation.
57+
58+
- **Local user group membership (preview)** – Use this profile to add, remove, or replace members of the built-in local groups on Windows devices. For example, the Administrators local group has broad rights. You can use this policy to edit the Admin group's membership to lock it down to a set of exclusively defined members.
59+
60+
Use of this profile is detailed in the following section, [Manage local groups on Windows devices](#manage-local-groups-on-windows-devices).
61+
62+
## Manage local groups on Windows devices
63+
64+
Use the Local user group membership (preview) profile to manage the users that are members of the built-in local groups on Windows 10/11 devices that receive this policy.
65+
66+
### Additional prerequisites for *local user group membership* profiles
67+
68+
- Devices must be Azure Active Directory (Azure AD) Joined, and managed by Intune
69+
- Users must be in your Azure AD
70+
71+
### Configure the profile
72+
73+
This profile manages the local group membership on devices through [Policy CSP - LocalUsersAndGroups](/windows/client-management/mdm/policy-csp-localusersandgroups?WT.mc_id=Portal-fx).
74+
75+
When configuring this profile, on the *Configuration settings* page you can create multiple rules to manage which built-in local groups you want to change, the group action to take, and the method to select the users.
76+
77+
:::image type="content" source="./media/endpoint-security-account-protection-policy/create-profile.png" alt-text="Screen shot of the Configuration settings page for configuring the profile.":::
78+
79+
The following are the configurations you can make:
80+
81+
- **Local group**: Select one or more groups from the drop-down. These groups will all apply the same Group and user action to the users you assign. You can create more than one grouping of local groups in a single profile and assign different actions and groups of users to each grouping of local groups.
82+
83+
- **Group and user action**: Configure the action to apply to the selected groups. This action will apply to the users you select for this same action and grouping of local accounts. Actions you can choose include:
84+
- **Add (Update)**: Adds members to the selected groups. The group membership for users that aren’t specified by the policy are not changed.
85+
- **Remove (Update)**: Remove members from the selected groups. The group membership for users that aren’t specified by the policy are not changed.
86+
- **Add (Replace)**: Replace the members of the selected groups with the new members you specify for this action. This option works in the same way as a Restricted Group and any group members that are not specified in the policy are removed.
87+
88+
> [!CAUTION]
89+
> If the same group is configured with both a Replace and Update action, the Replace action wins. This is not considered a conflict.
90+
91+
- **User selection type**: Choose how to select users. Options include:
92+
93+
- **Users**: Select the users and user groups from your Azure Active Directory (Azure AD).
94+
- **Manual**: Specify Azure AD users and groups manually, by username, domain/username, or their security identifier (SID).
95+
96+
- **Selected user(s)**: Depending on your selection for *User selection type*, you’ll use one of the following options:
97+
98+
- **Select user(s)**: Select the users and user groups from your Azure Active Directory (Azure AD).
99+
- **Add users(s)**: This opens the **Add users** pane where you can then specify one or more user identifiers as they appear on a device. You can specify the user by *Username, Domain/username*, or by *security identifier (SID)*.
100+
101+
:::image type="content" source="./media/endpoint-security-account-protection-policy/add-user.png" alt-text="Screen shot of the Add users page.":::
102+
103+
### Conflicts
104+
105+
If policies create a conflict for a group membership, the conflicting settings from each policy are not sent to the device. Instead, the conflict is reported for those policies in the Microsoft Endpoint Manager admin center. To resolve the conflict, reconfigure one or more policies.
106+
107+
### Reporting
108+
109+
As devices check in and apply the policy, the admin center displays the status of the devices and users as successful or in error.
110+
111+
Because the policy can contain multiple rules, consider the following:
53112

54-
- **Account protection** *(Preview)* – Settings for account protection policies help you protect user credentials.
113+
- When processing the policy for devices, the per-setting status view displays a status for the group of rules as if it’s a single setting.
114+
- Each rule in the policy that results in an error is skipped, and not sent to devices.
115+
- Each rule that is successful is sent to devices to be applied.
55116

56117
## Next steps
57118

61.5 KB
Loading
111 KB
Loading

0 commit comments

Comments
 (0)