rbac and machine groups

This commit is contained in:
jcaparas
2018-03-14 21:45:28 -07:00
parent f22883234b
commit d0482f5cc3
2 changed files with 20 additions and 4 deletions

View File

@ -26,7 +26,23 @@ ms.date: 04/16/2018
[!include[Prerelease information](prerelease.md)]
Create machine groups and set automated remediation levels on them, configure the rules to apply on the group, and assign the group to an Azure AD group and role. After configuring the groups and assignments, rank the group so that the corresponding rule is applied.
In a typical enterprise scenario, security operation teams are assigned a set of machines groups. These machines are grouped together based on a set of attributes such as domain, name, or tag.
In Windows Defender ATP, you can create machine groups based on conditions and apply the following rules on them:
- Remediation level for automated investigations
- Azure Active Directory (Azure AD) user group access
When you create a machine group, you'll need to set the automated remediation level for that group. You'll also need to configure the conditions for when a machine is considered to be part of that group. You can set the conditions based on name, domain, tag, or OS.
After setting the automated remediation level and conditions, you'll need to assign a Azure AD user group who will have access to that group of machines. The assignment you set here determines what the group can see in the portal. For example, if you assign a user group to only see machines with a specific tag then their view of the Machines list will be limited based on the tags you set in the rule.
Finally, you'll need to rank the machine groups so that the appropriate rul is applied on them.
### Add machine group
@ -54,7 +70,7 @@ Create machine groups and set automated remediation levels on them, configure th
4. Review the result of the preview of matched machines. If you are satisfied with the rules, click the **Access** tab.
5. Assign the user groups that can access the machine group you created. The assignment you set here determines what the group can see in the portal. For example, if you assign a user group to only see machines with a specific tag then their view of the Machines list will be limited based on the tags you set in the rule.
5. Assign the user groups that can access the machine group you created.
6. Click **Close**.
@ -62,7 +78,7 @@ Create machine groups and set automated remediation levels on them, configure th
## Rank rules on machine groups
After creating groups, setting the remediation levels on them, and assigning user groups that can access the machine group, you<6F>ll need to rank the rules that are applied on the groups.
After creating groups based on conditions, setting the remediation levels on them, and assigning user groups that can access the machine group, you<6F>ll need to rank the rules that are applied on the groups.
You can promote or demote the rank of a group so that the rules applied is of higher or lower level. The evaluation order is applied from higher rank to lower rank. The higher rank should apply to the most machines.

View File

@ -39,7 +39,7 @@ Tier 1 | **Local security operations team / IT team** <br> This team usually tri
Tier 2 | **Regional security operations team** <br> This team can see all the machines for their region and perform remediation actions.
Tier 3 | **Global security operations team** <br> This team consists of security experts and are authorized to see and perform all actions from the portal.
Windows Defender ATP RBAC is designed to support your tier or role model of choice and allows you to have granular control over what roles can see, machines they can access, and actions they can take.
Windows Defender ATP RBAC is designed to support your tier or role model of choice and gives you granular control over what roles can see, machines they can access, and actions they can take.
The implementation of role-based access control in Windows Defender ATP is based on Azure Active Directory (Azure AD) user groups.