mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-18 16:27:22 +00:00
Merged PR 8131: 5/10 PM Publish
This commit is contained in:
Alma Jenks
commit
acac4e7956
@ -10,7 +10,7 @@ ms.pagetype: security
|
||||
ms.author: macapara
|
||||
author: mjcaparas
|
||||
ms.localizationpriority: high
|
||||
ms.date: 04/24/2018
|
||||
ms.date: 05/08/2018
|
||||
---
|
||||
|
||||
# Configure advanced features in Windows Defender ATP
|
||||
@ -87,6 +87,11 @@ When you enable this feature, you'll be able to share Windows Defender ATP devic
|
||||
>You'll need to enable the integration on both Intune and Windows Defender ATP to use this feature.
|
||||
|
||||
|
||||
## Preview features
|
||||
Learn about new features in the Windows Defender ATP preview release and be among the first to try upcoming features by turning on the preview experience.
|
||||
|
||||
You'll have access to upcoming features which you can provide feedback on to help improve the overall experience before features are generally available.
|
||||
|
||||
## Enable advanced features
|
||||
1. In the navigation pane, select **Preferences setup** > **Advanced features**.
|
||||
2. Select the advanced feature you want to configure and toggle the setting between **On** and **Off**.
|
||||
|
||||
@ -10,7 +10,7 @@ ms.pagetype: security
|
||||
ms.author: macapara
|
||||
author: mjcaparas
|
||||
ms.localizationpriority: high
|
||||
ms.date: 05/03/2018
|
||||
ms.date: 05/08/2018
|
||||
---
|
||||
|
||||
# Use Automated investigations to investigate and remediate threats
|
||||
@ -65,15 +65,24 @@ While an investigation is running, any other alert generated from the machine wi
|
||||
If an incriminated entity is seen in another machine, the Automated investigation will expand the investigation to include that machine and a generic machine playbook will start on that machine. If 10 or more machines are found during this expansion process from the same entity, then that expansion action will require an approval and will be seen in the **Pending actions** view.
|
||||
|
||||
### How threats are remediated
|
||||
Depending on how you set up the machine groups and their level of automation, the Automated investigation will either automatically remediate threats or require user approval (this is the default). For more information, see [Create and manage machine groups](machine-groups-windows-defender-advanced-threat-protection.md).
|
||||
Depending on how you set up the machine groups and their level of automation, the Automated investigation will either require user approval (default) or automatically remediate threats.
|
||||
|
||||
You can configure the following levels of automation:
|
||||
|
||||
Automation level | Description
|
||||
:---|:---
|
||||
Semi - require approval for any remediation | This is the default automation level.<br><br> An approval is needed for any remediation action.
|
||||
Semi - require approval for non-temp folders remediation | An approval is required on files or executables that are not in temporary folders. <br><br> Files or executables in temporary folders, such as the user's download folder or the user's temp folder, will automatically be remediated if needed.
|
||||
Semi - require approval for non-temp folders remediation | An approval is required on files or executables that are in the operating system directories such as Windows folder and Program files folder. <br><br> Files or executables in all other folders will automatically be remediated if needed.
|
||||
Semi - require approval for core folders remediation | An approval is required on files or executables that are in the operating system directories such as Windows folder and Program files folder. <br><br> Files or executables in all other folders will automatically be remediated if needed.
|
||||
Full - remediate threats automatically | All remediation actions will be performed automatically.
|
||||
|
||||
For more information on how to configure these automation levels, see [Create and manage machine groups](machine-groups-windows-defender-advanced-threat-protection.md).
|
||||
|
||||
The default machine group is configured for semi-automatic remediation. This means that any malicious entity that needs to be remediated requires an approval and the investigation is added to the **Pending actions** section, this can be changed to fully automatic so that no user approval is needed.
|
||||
|
||||
When a pending action is approved, the entity is then remediated and this new state is reflected in the **Entities** tab of the investigation.
|
||||
|
||||
### How an Automated investigation is completed
|
||||
When the Automated investigation completes its analysis, and all pending actions are resolved, an investigation is considered complete. It's important to understand that an investigation is only considered complete if there are no pending actions on it.
|
||||
|
||||
|
||||
## Manage Automated investigations
|
||||
By default, the Automated investigations list displays investigations initiated in the last week. You can also choose to select other time ranges from the drop-down menu or specify a custom range.
|
||||
@ -103,19 +112,15 @@ Status | Description
|
||||
| No threats found | No malicious entities found during the investigation.
|
||||
| Failed | A problem has interrupted the investigation, preventing it from completing. |
|
||||
| Partially remediated | A problem prevented the remediation of some malicious entities. |
|
||||
| Action required | Remediation actions require review and approval. |
|
||||
| Pending | Remediation actions require review and approval. |
|
||||
| Waiting for machine | Investigation paused. The investigation will resume as soon as the machine is available. |
|
||||
| Queued | Investigation has been queued and will resume as soon as other remediation activities are completed. |
|
||||
| Running | Investigation ongoing. Malicious entities found will be remediated. |
|
||||
| Remediated | Malicious entities found were successfully remediated. |
|
||||
| Terminated by system | Investigation was stopped due to <reason>. |
|
||||
| Terminated by user | A user stopped the investigation before it could complete. |
|
||||
| Not applicable | Automated investigations do not apply to this alert type. |
|
||||
| Terminated by user | A user stopped the investigation before it could complete.
|
||||
| Partially investigated | Entities directly related to the alert have been investigated. However, a problem stopped the investigation of collateral entities. |
|
||||
| Automated investigation not applicable to alert type | Automated investigation does not apply to this alert type. |
|
||||
| Automated investigation does not support OS | Machine is running an OS that is not supported by Automated investigation. |
|
||||
| Automated investigation unavailable for preexisting alert | Automated investigation does not apply to alerts that were generated before it was deployed. |
|
||||
| Automated investigation unavailable for suppressed alert | Automated investigation does not apply to suppressed alerts. |
|
||||
|
||||
|
||||
|
||||
**Detection source**</br>
|
||||
|
||||
@ -102,7 +102,7 @@ Take the following steps to enable conditional access:
|
||||
|
||||
|
||||
### Step 1: Turn on the Microsoft Intune connection
|
||||
1. In the navigation pane, select **Settings** > **General** > **Advanced features** > **Microsoft Intune connection**.
|
||||
1. In the navigation pane, select **Settings** > **Advanced features** > **Microsoft Intune connection**.
|
||||
2. Toggle the Microsoft Intune setting to **On**.
|
||||
3. Click **Save preferences**.
|
||||
|
||||
|
||||
@ -30,26 +30,29 @@ ms.date: 05/01/2018
|
||||
You can configure Windows Defender ATP to send email notifications to specified recipients for new alerts. This feature enables you to identify a group of individuals who will immediately be informed and can act on alerts based on their severity.
|
||||
|
||||
> [!NOTE]
|
||||
> Only users with full access can configure email notifications.
|
||||
> Only users with 'Manage security settings' permissions can configure email notifications. If you've chosen to use basic permissions management, users with Security Administrator or Global Administrator roles can configure email notifications.
|
||||
|
||||
You can set the alert severity levels that trigger notifications. When you turn enable the email notifications feature, it’s set to high and medium alerts by default.
|
||||
You can set the alert severity levels that trigger notifications. You can also add or remove recipients of the email notification. New recipients get notified about alerts encountered after they are added. For more information about alerts, see [View and organize the Alerts queue](alerts-queue-windows-defender-advanced-threat-protection.md).
|
||||
|
||||
You can also add or remove recipients of the email notification. New recipients get notified about alerts encountered after they are added. For more information about alerts, see [View and organize the Alerts queue](alerts-queue-windows-defender-advanced-threat-protection.md).
|
||||
If you're using role-based access control (RBAC), recipients will only receive notifications based on the machine groups that were configured in the notification rule.
|
||||
Users with the proper permission can only create, edit, or delete notifications that are limited to their machine group management scope.
|
||||
Only users assigned to the Global administrator role can manage notification rules that are configured for all machine groups.
|
||||
|
||||
The email notification includes basic information about the alert and a link to the portal where you can do further investigation.
|
||||
|
||||
|
||||
## Set up email notifications for alerts
|
||||
The email notifications feature is turned off by default. Turn it on to start receiving email notifications.
|
||||
|
||||
1. On the navigation pane, select **Settings** > **Alert notifications**.
|
||||
2. Toggle the setting between **On** and **Off**.
|
||||
3. Select the alert severity level that you’d like your recipients to receive:
|
||||
- **High** – Select this level to send notifications for high-severity alerts.
|
||||
- **Medium** – Select this level to send notifications for medium-severity alerts.
|
||||
3. Select the alert severity level that you’d like your recipients to receive:
|
||||
- **High** – Select this level to send notifications for high-severity alerts.
|
||||
- **Medium** – Select this level to send notifications for medium-severity alerts.
|
||||
- **Low** - Select this level to send notifications for low-severity alerts.
|
||||
- **Informational** - Select this level to send notification for alerts that might not be considered harmful but good to keep track of.
|
||||
4. In **Email recipients to notify on new alerts**, type the email address then select the + sign.
|
||||
5. Click **Save preferences** when you’ve completed adding all the recipients.
|
||||
5. Click **Save preferences** when you’ve completed adding all the recipients.
|
||||
|
||||
Check that email recipients are able to receive the email notifications by selecting **Send test email**. All recipients in the list will receive the test email.
|
||||
|
||||
@ -59,10 +62,9 @@ Here's an example email notification:
|
||||
|
||||
## Remove email recipients
|
||||
|
||||
1. Select the trash bin icon beside the email address you’d like to remove.
|
||||
1. Select the trash bin icon beside the email address you’d like to remove.
|
||||
2. Click **Save preferences**.
|
||||
|
||||
|
||||
## Troubleshoot email notifications for alerts
|
||||
This section lists various issues that you may encounter when using email notifications for alerts.
|
||||
|
||||
|
||||
@ -36,7 +36,7 @@ ms.date: 04/24/2018
|
||||
## Onboard machines using Group Policy
|
||||
1. Open the GP configuration package .zip file (*WindowsDefenderATPOnboardingPackage.zip*) that you downloaded from the service onboarding wizard. You can also get the package from the [Windows Defender ATP portal](https://securitycenter.windows.com/):
|
||||
|
||||
a. In the navigation pane, select **Settings** > **Machine management** > **Onboarding**.
|
||||
a. In the navigation pane, select **Settings** > **Onboarding**.
|
||||
|
||||
b. Select Windows 10 as the operating system.
|
||||
|
||||
@ -122,7 +122,7 @@ For security reasons, the package used to Offboard machines will expire 30 days
|
||||
|
||||
1. Get the offboarding package from the [Windows Defender ATP portal](https://securitycenter.windows.com/):
|
||||
|
||||
a. In the navigation pane, select **Settings** > **Machine management** > **Offboarding**.
|
||||
a. In the navigation pane, select **Settings** > **Offboarding**.
|
||||
|
||||
b. Select Windows 10 as the operating system.
|
||||
|
||||
|
||||
@ -106,7 +106,7 @@ For more information on using Windows Defender ATP CSP see, [WindowsAdvancedThre
|
||||
|
||||
1. Open the Microsoft Intune configuration package .zip file (*WindowsDefenderATPOnboardingPackage.zip*) that you downloaded from the service onboarding wizard. You can also get the package from the [Windows Defender ATP portal](https://securitycenter.windows.com/):
|
||||
|
||||
a. In the navigation pane, select **Settings** > **Machine management** > **Onboarding**.
|
||||
a. In the navigation pane, select **Settings** > **Onboarding**.
|
||||
|
||||
b. Select Windows 10 as the operating system.
|
||||
|
||||
@ -189,7 +189,7 @@ For security reasons, the package used to Offboard machines will expire 30 days
|
||||
|
||||
1. Get the offboarding package from the [Windows Defender ATP portal](https://securitycenter.windows.com/):
|
||||
|
||||
a. In the navigation pane, select **Settings** > **Machine management** > **Offboarding**.
|
||||
a. In the navigation pane, select **Settings** > **Offboarding**.
|
||||
|
||||
b. Select Windows 10 as the operating system.
|
||||
|
||||
|
||||
@ -34,7 +34,7 @@ You'll need to take the following steps to onboard non-Windows machines:
|
||||
|
||||
### Turn on third-party integration
|
||||
|
||||
1. In the navigation pane, select **Settings** > **Machine management** > **Onboarding**. Make sure the third-party solution is listed.
|
||||
1. In the navigation pane, select **Settings** > **Onboarding**. Make sure the third-party solution is listed.
|
||||
|
||||
2. Select Mac and Linux as the operating system.
|
||||
|
||||
@ -59,7 +59,7 @@ To effectively offboard the machine from the service, you'll need to disable the
|
||||
|
||||
1. Follow the third-party documentation to opt-out on the third-party service side.
|
||||
|
||||
2. In the navigation pane, select **Settings** > **Machine management** > **Onboarding**.
|
||||
2. In the navigation pane, select **Settings** > **Onboarding**.
|
||||
|
||||
3. Turn off the third-party solution integration.
|
||||
|
||||
|
||||
@ -49,7 +49,7 @@ You can use existing System Center Configuration Manager functionality to create
|
||||
|
||||
1. Open the SCCM configuration package .zip file (*WindowsDefenderATPOnboardingPackage.zip*) that you downloaded from the service onboarding wizard. You can also get the package from the [Windows Defender ATP portal](https://securitycenter.windows.com/):
|
||||
|
||||
a. In the navigation pane, select **Settings** > **Machine management** > **Onboarding**.
|
||||
a. In the navigation pane, select **Settings** > **Onboarding**.
|
||||
|
||||
b. Select Windows 10 as the operating system.
|
||||
|
||||
@ -127,7 +127,7 @@ For security reasons, the package used to Offboard machines will expire 30 days
|
||||
|
||||
1. Get the offboarding package from the [Windows Defender ATP portal](https://securitycenter.windows.com/):
|
||||
|
||||
a. In the navigation pane, select **Settings** > **Machine management** > **Offboarding**.
|
||||
a. In the navigation pane, select **Settings** > **Offboarding**.
|
||||
|
||||
b. Select Windows 10 as the operating system.
|
||||
|
||||
|
||||
@ -36,7 +36,7 @@ You can also manually onboard individual machines to Windows Defender ATP. You m
|
||||
## Onboard machines
|
||||
1. Open the GP configuration package .zip file (*WindowsDefenderATPOnboardingPackage.zip*) that you downloaded from the service onboarding wizard. You can also get the package from the [Windows Defender ATP portal](https://securitycenter.windows.com/):
|
||||
|
||||
a. In the navigation pane, select **Settings** > **Machine management** > **Onboarding**.
|
||||
a. In the navigation pane, select **Settings** > **Onboarding**.
|
||||
|
||||
b. Select Windows 10 as the operating system.
|
||||
|
||||
@ -94,7 +94,7 @@ For security reasons, the package used to Offboard machines will expire 30 days
|
||||
|
||||
1. Get the offboarding package from the [Windows Defender ATP portal](https://securitycenter.windows.com/):
|
||||
|
||||
a. In the navigation pane, select **Settings** > **Machine management** > **Offboarding**.
|
||||
a. In the navigation pane, select **Settings** > **Offboarding**.
|
||||
|
||||
b. Select Windows 10 as the operating system.
|
||||
|
||||
|
||||
@ -40,7 +40,7 @@ You can onboard VDI machines using a single entry or multiple entries for each m
|
||||
|
||||
1. Open the VDI configuration package .zip file (*WindowsDefenderATPOnboardingPackage.zip*) that you downloaded from the service onboarding wizard. You can also get the package from the [Windows Defender ATP portal](https://securitycenter.windows.com/):
|
||||
|
||||
a. In the navigation pane, select **Settings** > **Machine management** > **Onboarding**.
|
||||
a. In the navigation pane, select **Settings** > **Onboarding**.
|
||||
|
||||
b. Select Windows 10 as the operating system.
|
||||
|
||||
|
||||
@ -115,7 +115,9 @@ You’ll be able to onboard in the same method available for Windows 10 client m
|
||||
If the result is ‘The specified service does not exist as an installed service’, then you'll need to install Windows Defender AV. For more information, see [Windows Defender Antivirus in Windows 10](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-antivirus/windows-defender-antivirus-in-windows-10).
|
||||
|
||||
## Offboard servers
|
||||
You have two options to offboard servers from the service:
|
||||
You can offboard Windows Server, version 1803 in the same method available for Windows 10 client machines.
|
||||
|
||||
For other server versions, you have two options to offboard servers from the service:
|
||||
- Uninstall the MMA agent
|
||||
- Remove the Windows Defender ATP workspace configuration
|
||||
|
||||
@ -143,7 +145,7 @@ To offboard the server, you can use either of the following methods:
|
||||
#### Run a PowerShell command to remove the configuration
|
||||
|
||||
1. Get your Workspace ID:
|
||||
a. In the navigation pane, select **Settings** > **Machine management** > **Onboarding**.
|
||||
a. In the navigation pane, select **Settings** > **Onboarding**.
|
||||
|
||||
b. Select **Windows server 2012, 2012R2 and 2016** as the operating system and get your Workspace ID:
|
||||
|
||||
|
||||
@ -28,7 +28,7 @@ ms.date: 04/24/2018
|
||||
|
||||
During the onboarding process, a wizard takes you through the general settings of Windows Defender ATP. After onboarding, you might want to update the data retention settings.
|
||||
|
||||
1. In the navigation pane, select **Settings** > **General** > **Data rention**.
|
||||
1. In the navigation pane, select **Settings** > **Data rention**.
|
||||
|
||||
2. Select the data retention duration from the drop-down list.
|
||||
|
||||
|
||||
@ -29,7 +29,7 @@ ms.date: 04/24/2018
|
||||
|
||||
Before you can create custom threat intelligence (TI) using REST API, you'll need to set up the custom threat intelligence application through the Windows Defender ATP portal.
|
||||
|
||||
1. In the navigation pane, select **Settings** > **APIs** > **Threat intel**.
|
||||
1. In the navigation pane, select **Settings** > **Threat intel**.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -30,7 +30,7 @@ Set the baselines for calculating the score of Windows Defender security control
|
||||
>[!NOTE]
|
||||
>Changes might take up to a few hours to reflect on the dashboard.
|
||||
|
||||
1. In the navigation pane, select **Settings** > **General** > **Secure Score**.
|
||||
1. In the navigation pane, select **Settings** > **Secure Score**.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -29,7 +29,7 @@ ms.date: 04/24/2018
|
||||
|
||||
Enable security information and event management (SIEM) integration so you can pull alerts from the Windows Defender ATP portal using your SIEM solution or by connecting directly to the alerts REST API.
|
||||
|
||||
1. In the navigation pane, select **Settings** > **APIs** > **SIEM**.
|
||||
1. In the navigation pane, select **Settings** > **SIEM**.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -10,7 +10,7 @@ ms.pagetype: security
|
||||
ms.author: macapara
|
||||
author: mjcaparas
|
||||
ms.localizationpriority: high
|
||||
ms.date: 04/24/2018
|
||||
ms.date: 05/08/2018
|
||||
---
|
||||
|
||||
# Create and manage machine groups in Windows Defender ATP
|
||||
@ -33,61 +33,61 @@ In Windows Defender ATP, you can create machine groups and use them to:
|
||||
- Configure different auto-remediation settings for different sets of machines
|
||||
|
||||
As part of the process of creating a machine group, you'll:
|
||||
- Set the automated remediation level for that group
|
||||
- Define a matching rule based on the machine name, domain, tags, and OS platform to determine which machines belong to the group. If a machine is also matched to other groups, it is added only to the highest ranked machine group.
|
||||
- Determine access to machine group
|
||||
- Rank the machine group relative to other groups after it is created
|
||||
- Set the automated remediation level for that group. For more information on remediation levels, see [Use Automated investigation to investigate and remediate threats](automated-investigations-windows-defender-advanced-threat-protection.md).
|
||||
- Specify the matching rule that determines which machine group belongs to the group based on the machine name, domain, tags, and OS platform. If a machine is also matched to other groups, it is added only to the highest ranked machine group.
|
||||
- Select the Azure AD user group that should have access to the machine group.
|
||||
- Rank the machine group relative to other groups after it is created.
|
||||
|
||||
>[!NOTE]
|
||||
>All machine groups are accessible to all users if you don’t assign any Azure AD groups to them.
|
||||
>A machine group is accessible to all users if you don’t assign any Azure AD groups to it.
|
||||
|
||||
|
||||
## Add a machine group
|
||||
|
||||
1. In the navigation pane, select **Settings > Permissions > Machine groups**.
|
||||
1. In the navigation pane, select **Settings** > **Machine groups**.
|
||||
|
||||
2. Click **Add machine group**.
|
||||
|
||||
3. Set the machine group details, configure an association rule, preview the results, then assign the group to an Azure user group:
|
||||
3. Enter the group name and automation settings and specify the matching rule that determines which machines belong to the group.
|
||||
|
||||
- **Name**
|
||||
|
||||
- **Remediation level for automated investigations**
|
||||
- **No remediation**
|
||||
- **Require approval (all folders)**
|
||||
- **Require approval (non-temp folders)**
|
||||
- **Require approval (core folders)**
|
||||
- **Fully automated**
|
||||
- **Machine group name**
|
||||
- **Automation level**
|
||||
- **Semi - require approval for any remediation**
|
||||
- **Semi - require approval for non-temp folders remediation**
|
||||
- **Semi - require approval for core folders remediation**
|
||||
- **Full - remediate threats automatically**
|
||||
|
||||
>[!NOTE]
|
||||
> For more information on automation levels, see [Understand the Automated investigation flow](automated-investigations-windows-defender-advanced-threat-protection.md#understand-the-automated-investigation-flow).
|
||||
|
||||
- **Description**
|
||||
- **Members**
|
||||
|
||||
- **Matching rule** – you can apply the rule based on machine name, domain, tag, or OS version.
|
||||
>[!TIP]
|
||||
>If you want to group machines by organizational unit, you can configure the registry key for the group affiliation. For more information on device tagging, see [Manage machine group and tags](https://docs.microsoft.com/en-us/windows/security/threat-protection/windows-defender-atp/investigate-machines-windows-defender-advanced-threat-protection#manage-machine-group-and-tags).
|
||||
|
||||
>[!TIP]
|
||||
>If you want to group machines by organizational unit, you can configure the registry key for the group affiliation. For more information on device tagging, see [Manage machine group and tags](https://docs.microsoft.com/en-us/windows/security/threat-protection/windows-defender-atp/investigate-machines-windows-defender-advanced-threat-protection#manage-machine-group-and-tags).
|
||||
|
||||
4. Review the result of the preview of matched machines. If you are satisfied with the rules, click the **Access** tab.
|
||||
4. Preview several machines that will be matched by this rule. If you are satisfied with the rule, click the **Access** tab.
|
||||
|
||||
5. Assign the user groups that can access the machine group you created.
|
||||
|
||||
>[!NOTE]
|
||||
>You can only grant access to Azure AD user groups that have been assigned to RBAC roles.
|
||||
|
||||
6. Click **Close**.
|
||||
6. Click **Close**. The configuration changes are applied.
|
||||
|
||||
7. Apply the configuration settings.
|
||||
|
||||
## Understand matching and manage groups
|
||||
You can promote the rank of a machine group so that it is given higher priority during matching. When a machine is matched to more than one group, it is added only to the highest ranked group. You can also edit and delete groups.
|
||||
## Manage machine groups
|
||||
You can promote or demote the rank of a machine group so that it is given higher or lower priority during matching. When a machine is matched to more than one group, it is added only to the highest ranked group. You can also edit and delete groups.
|
||||
|
||||
>[!WARNING]
|
||||
>Deleting a machine group may affect email notification rules. If a machine group is configured under an email notification rule, it will be removed from that rule. If the machine group is the only group configured for an email notification, that email notification rule will be deleted along with the machine group.
|
||||
|
||||
By default, machine groups are accessible to all users with portal access. You can change the default behavior by assigning Azure AD user groups to the machine group.
|
||||
|
||||
Machines that are not matched to any groups are added to Ungrouped machines (default) group. You cannot change the rank of this group or delete it. However, you can change the remediation level of this group, and define the Azure AD user groups that can access this group.
|
||||
|
||||
>[!NOTE]
|
||||
>Applying changes to machine group configuration may take up to several minutes.
|
||||
|
||||
|
||||
> - Applying changes to machine group configuration may take up to several minutes.
|
||||
|
||||
|
||||
## Related topic
|
||||
|
||||
@ -110,7 +110,7 @@ Create custom rules to control when alerts are suppressed, or resolved. You can
|
||||
|
||||
### View the list of suppression rules
|
||||
|
||||
1. In the navigation pane, select **Settings** > **Rules** > **Alert suppression**.
|
||||
1. In the navigation pane, select **Settings** > **Alert suppression**.
|
||||
|
||||
2. The list of suppression rules shows all the rules that users in your organization have created.
|
||||
|
||||
|
||||
@ -36,7 +36,7 @@ Entities added to the blocked list are considered malicious and will be remediat
|
||||
You can define the conditions for when entities are identified as malicious or safe based on certain attributes such as hash values or certificates.
|
||||
|
||||
## Create an allowed or blocked list
|
||||
1. In the navigation pane, select **Settings** > **Rules** > **Automation allowed/blocked list**.
|
||||
1. In the navigation pane, select **Settings** > **Automation allowed/blocked list**.
|
||||
|
||||
2. Select the type of entity you'd like to create an exclusion for. You can choose any of the following entities:
|
||||
- File hash
|
||||
@ -52,14 +52,14 @@ You can define the conditions for when entities are identified as malicious or s
|
||||
5. Click **Update rule**.
|
||||
|
||||
## Edit a list
|
||||
1. In the navigation pane, select **Settings** > **Rules** > **Automation allowed/blocked list**.
|
||||
1. In the navigation pane, select **Settings** > **Automation allowed/blocked list**.
|
||||
|
||||
2. Select the type of entity you'd like to edit the list from.
|
||||
|
||||
3. Update the details of the rule and click **Update rule**.
|
||||
|
||||
## Delete a list
|
||||
1. In the navigation pane, select **Settings** > **Rules** > **Automation allowed/blocked list**.
|
||||
1. In the navigation pane, select **Settings** > **Automation allowed/blocked list**.
|
||||
|
||||
2. Select the type of entity you'd like to delete the list from.
|
||||
|
||||
|
||||
@ -35,7 +35,7 @@ For example, if you add *exe* and *bat* as file or attachment extension names, t
|
||||
|
||||
## Add file extension names and attachment extension names.
|
||||
|
||||
1. In the navigation pane, select **Settings** > **Rules** > **Automation file uploads**.
|
||||
1. In the navigation pane, select **Settings** > **Automation file uploads**.
|
||||
|
||||
2. Toggle the content analysis setting between **On** and **Off**.
|
||||
|
||||
|
||||
@ -47,7 +47,7 @@ You can specify the file names that you want to be excluded in a specific direct
|
||||
|
||||
|
||||
## Add an automation folder exclusion
|
||||
1. In the navigation pane, select **Settings** > **Rules** > **Automation folder exclusions**.
|
||||
1. In the navigation pane, select **Settings** > **Automation folder exclusions**.
|
||||
|
||||
2. Click **New folder exclusion**.
|
||||
|
||||
@ -62,14 +62,14 @@ You can specify the file names that you want to be excluded in a specific direct
|
||||
4. Click **Save**.
|
||||
|
||||
## Edit an automation folder exclusion
|
||||
1. In the navigation pane, select **Settings** > **Rules** > **Automation folder exclusions**.
|
||||
1. In the navigation pane, select **Settings** > **Automation folder exclusions**.
|
||||
|
||||
2. Click **Edit** on the folder exclusion.
|
||||
|
||||
3. Update the details of the rule and click **Save**.
|
||||
|
||||
## Remove an automation folder exclusion
|
||||
1. In the navigation pane, select **Settings** > **Rules** > **Automation folder exclusions**.
|
||||
1. In the navigation pane, select **Settings** > **Automation folder exclusions**.
|
||||
2. Click **Remove exclusion**.
|
||||
|
||||
|
||||
|
||||
@ -32,7 +32,7 @@ There might be scenarios where you need to suppress alerts from appearing in the
|
||||
You can view a list of all the suppression rules and manage them in one place. You can also turn an alert suppression rule on or off.
|
||||
|
||||
## Turn a suppression rule on or off
|
||||
1. In the navigation pane, select **Settings** > **Rules** > **Alert suppression**. The list of suppression rules that users in your organization have created is displayed.
|
||||
1. In the navigation pane, select **Settings** > **Alert suppression**. The list of suppression rules that users in your organization have created is displayed.
|
||||
|
||||
2. Select a rule by clicking on the check-box beside the rule name.
|
||||
|
||||
@ -40,7 +40,7 @@ You can view a list of all the suppression rules and manage them in one place. Y
|
||||
|
||||
## View details of a suppression rule
|
||||
|
||||
1. In the navigation pane, select **Settings** > **Rules** > **Alert suppression**. The list of suppression rules that users in your organization have created is displayed.
|
||||
1. In the navigation pane, select **Settings** > **Alert suppression**. The list of suppression rules that users in your organization have created is displayed.
|
||||
|
||||
2. Click on a rule name. Details of the rule is displayed. You'll see the rule details such as status, scope, action, number of matching alerts, created by, and date when the rule was created. You can also view associated alerts and the rule conditions.
|
||||
|
||||
|
||||
@ -40,7 +40,7 @@ You can access these options from the Windows Defender ATP portal. Both the Powe
|
||||
## Create a Windows Defender ATP dashboard on Power BI service
|
||||
Windows Defender ATP makes it easy to create a Power BI dashboard by providing an option straight from the portal.
|
||||
|
||||
1. In the navigation pane, select **Settings** > **General** > **Power BI reports**.
|
||||
1. In the navigation pane, select **Settings** > **Power BI reports**.
|
||||
|
||||
2. Click **Create dashboard**.
|
||||
|
||||
@ -127,7 +127,7 @@ You can create a custom dashboard in Power BI Desktop to create visualizations t
|
||||
### Before you begin
|
||||
1. Make sure you use Power BI Desktop June 2017 and above. [Download the latest version](https://powerbi.microsoft.com/en-us/desktop/).
|
||||
|
||||
2. In the navigation pane, select **Settings** > **General** > **Power BI reports**.
|
||||
2. In the navigation pane, select **Settings** > **Power BI reports**.
|
||||
|
||||
3. Click **Download connector** to download the WDATPPowerBI.zip file and extract it.
|
||||
|
||||
|
||||
@ -28,7 +28,7 @@ ms.date: 04/24/2018
|
||||
|
||||
Turn on the preview experience setting to be among the first to try upcoming features.
|
||||
|
||||
1. In the navigation pane, select **Settings** > **Preview experience**.
|
||||
1. In the navigation pane, select **Settings** > **Advanced features**.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -36,7 +36,7 @@ You'll have access to upcoming features which you can provide feedback on to hel
|
||||
|
||||
Turn on the preview experience setting to be among the first to try upcoming features.
|
||||
|
||||
1. In the navigation pane, select **Settings** > **General** > **Advanced features** > **Preview features**.
|
||||
1. In the navigation pane, select **Settings** > **Advanced features** > **Preview features**.
|
||||
|
||||
2. Toggle the setting between **On** and **Off** and select **Save preferences**.
|
||||
|
||||
|
||||
@ -10,7 +10,7 @@ ms.pagetype: security
|
||||
ms.author: macapara
|
||||
author: mjcaparas
|
||||
ms.localizationpriority: high
|
||||
ms.date: 04/24/2018
|
||||
ms.date: 05/08/2018
|
||||
---
|
||||
|
||||
# Manage portal access using role-based access control
|
||||
@ -76,17 +76,18 @@ Someone with a Windows Defender ATP Global administrator role has unrestricted a
|
||||
|
||||
2. Click **Add role**.
|
||||
|
||||
3. Enter the role name, description, and active permissions you’d like to assign to the role.
|
||||
3. Enter the role name, description, and permissions you’d like to assign to the role.
|
||||
|
||||
- **Role name**
|
||||
|
||||
- **Description**
|
||||
|
||||
- **Active permissions**
|
||||
- **Permissions**
|
||||
- **View data** - Users can view information in the portal.
|
||||
- **Investigate alerts** - Users can manage alerts, initiate automated investigations, collect investigation packages, manage machine tags, and export machine timeline.
|
||||
- **Approve or take action** - Users can take response actions and approve or dismiss pending remediation actions.
|
||||
- **Manage system settings** - Users can configure settings, SIEM and threat intel API settings, advanced settings, preview features, and automated file uploads.
|
||||
- **Manage security settings** - Users can configure alert suppression settings, manage allowed/blocked lists for automation, manage folder exclusions for automation, onboard and offboard machines, and manage email notifications.
|
||||
|
||||
4. Click **Next** to assign the role to an Azure AD group.
|
||||
|
||||
@ -102,13 +103,13 @@ Someone with a Windows Defender ATP Global administrator role has unrestricted a
|
||||
|
||||
2. Click **Edit**.
|
||||
|
||||
3. Modify the details or the groups that the role is a part of.
|
||||
3. Modify the details or the groups that are assigned to the role.
|
||||
|
||||
4. Click **Save and close**.
|
||||
|
||||
## Delete roles
|
||||
|
||||
1. Select the role row you'd like to delete.
|
||||
1. Select the role you'd like to delete.
|
||||
|
||||
2. Click the drop-down button and select **Delete role**.
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user