mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 21:37:22 +00:00
Merge branch 'master' into insider-risk
This commit is contained in:
Joey Caparas
commit
2fd0b3d7ce
@ -65,22 +65,6 @@
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "mdop",
|
||||
"build_source_folder": "mdop",
|
||||
"build_output_subfolder": "mdop",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
"ManagedReference": "Content",
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "microsoft-edge",
|
||||
"build_source_folder": "browsers/edge",
|
||||
@ -145,38 +129,6 @@
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "surface",
|
||||
"build_source_folder": "devices/surface",
|
||||
"build_output_subfolder": "surface",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
"ManagedReference": "Content",
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "surface-hub",
|
||||
"build_source_folder": "devices/surface-hub",
|
||||
"build_output_subfolder": "surface-hub",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
"ManagedReference": "Content",
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "win-access-protection",
|
||||
"build_source_folder": "windows/access-protection",
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
description: You can customize your organization’s browser settings in Microsoft Edge with Group Policy or Microsoft Intune, or other MDM service. When you do this, you set the policy once and then copy it onto many computers—that is, touch once, configure many.
|
||||
description: You can customize your organization's browser settings in Microsoft Edge with Group Policy or Microsoft Intune, or other MDM service. When you do this, you set the policy once and then copy it onto many computers—that is, touch once, configure many.
|
||||
ms.assetid: 2e849894-255d-4f68-ae88-c2e4e31fa165
|
||||
ms.reviewer:
|
||||
author: dansimp
|
||||
@ -18,7 +18,10 @@ ms.localizationpriority: medium
|
||||
|
||||
> Applies to: Microsoft Edge on Windows 10 and Windows 10 Mobile
|
||||
|
||||
You can customize your organization’s browser settings in Microsoft Edge with Group Policy or Microsoft Intune, or other MDM service. When you do this, you set the policy once and then copy it onto many computers—that is, touch once, configure many. For example, you can set up multiple security settings in a Group Policy Object (GPO) linked to a domain, and then apply those settings to every computer in the domain.
|
||||
> [!NOTE]
|
||||
> You've reached the documentation for Microsoft Edge version 45 and earlier. To see the documentation for Microsoft Edge version 77 or later, go to the [Microsoft Edge documentation landing page](https://docs.microsoft.com/DeployEdge/).
|
||||
|
||||
You can customize your organization's browser settings in Microsoft Edge with Group Policy or Microsoft Intune, or other MDM service. When you do this, you set the policy once and then copy it onto many computers—that is, touch once, configure many. For example, you can set up multiple security settings in a Group Policy Object (GPO) linked to a domain, and then apply those settings to every computer in the domain.
|
||||
|
||||
Other policy settings in Microsoft Edge include allowing Adobe Flash content to play automatically, provision a favorites list, set default search engine, and more. You configure a Group Policy setting in the Administrative Templates folders, which are registry-based policy settings that Group Policy enforces. Group Policy stores these settings in a specific registry location, which users cannot change. Also, Group Policy-aware Windows features and applications look for these settings in the registry, and if found the policy setting gets used instead of the regular settings.
|
||||
|
||||
|
||||
@ -38,10 +38,10 @@ The [Windows Assessment and Deployment Kit (ADK) for Windows 10](https://develop
|
||||
- The tool for creating provisioning packages is renamed Windows Configuration Designer, replacing the Windows Imaging and Configuration Designer (ICD) tool. The components for creating images have been removed from Windows Configuration Designer, which now provides access to runtime settings only.
|
||||
- Windows Configuration Designer can still be installed from the Windows ADK. You can also install it from the Microsoft Store.
|
||||
- Windows Configuration Designer adds more wizards to make it easier to create provisioning packages for specific scenarios. See [What you can configure](#configuration-designer-wizards) for wizard descriptions.
|
||||
- The wizard **Provision desktop devices** (previously called **Simple provisioning**) now enables joining Azure Active Directory (Azure AD) domains and also allows you to remove non-Microsoft software from Windows desktop devices during provisioning.
|
||||
- The Provision desktop devices wizard (previously called Simple provisioning) now enables joining Azure Active Directory (Azure AD) domains and also allows you to remove non-Microsoft software from Windows desktop devices during provisioning.
|
||||
- When provisioning packages are applied to a device, a status screen indicates successful or failed provisioning.
|
||||
- Windows 10 includes PowerShell cmdlets that simplify scripted provisioning. Using these cmdlets, you can add provisioning packages, remove provisioning packages and generate log files to investigate provisioning errors.
|
||||
- The **Provision school devices** wizard is removed from Windows Configuration Designer. Instead, use the [Setup School PCs app](https://www.microsoft.com/store/p/set-up-school-pcs/9nblggh4ls40) from the Microsoft Store.
|
||||
- The Provision school devices wizard is removed from Windows Configuration Designer. Instead, use the [Setup School PCs app](https://www.microsoft.com/store/p/set-up-school-pcs/9nblggh4ls40) from the Microsoft Store.
|
||||
<!-- Provisioning packages can be made available [using NFC and barcodes](provisioning-nfc.md).-->
|
||||
|
||||
|
||||
@ -119,8 +119,8 @@ For details about the settings you can customize in provisioning packages, see [
|
||||
|
||||
## Changes to provisioning in Windows 10, version 1607
|
||||
|
||||
>[!NOTE]
|
||||
>This section is retained for customers using Windows 10, version 1607, on the Current Branch for Business. Some of this information is not applicable in Windows 10, version 1703.
|
||||
> [!NOTE]
|
||||
> This section is retained for customers using Windows 10, version 1607, on the Current Branch for Business. Some of this information is not applicable in Windows 10, version 1703.
|
||||
|
||||
Windows ICD for Windows 10, version 1607, simplified common provisioning scenarios.
|
||||
|
||||
@ -130,7 +130,7 @@ Windows ICD in Windows 10, version 1607, supported the following scenarios for I
|
||||
|
||||
* **Simple provisioning** – Enables IT administrators to define a desired configuration in Windows ICD and then apply that configuration on target devices. The simple provisioning wizard makes the entire process quick and easy by guiding an IT administrator through common configuration settings in a step-by-step manner.
|
||||
|
||||
> [Learn how to use simple provisioning to configure Windows 10 computers.](provision-pcs-for-initial-deployment.md)
|
||||
[Learn how to use simple provisioning to configure Windows 10 computers.](provision-pcs-for-initial-deployment.md)
|
||||
|
||||
* **Advanced provisioning (deployment of classic (Win32) and Universal Windows Platform (UWP) apps, and certificates)** – Allows an IT administrator to use Windows ICD to open provisioning packages in the advanced settings editor and include apps for deployment on end-user devices.
|
||||
|
||||
@ -146,9 +146,11 @@ Windows ICD in Windows 10, version 1607, supported the following scenarios for I
|
||||
|
||||
## Learn more
|
||||
|
||||
- Watch the video: [Provisioning Windows 10 Devices with New Tools](https://go.microsoft.com/fwlink/p/?LinkId=615921)
|
||||
For more information about provisioning, watch the following videos:
|
||||
|
||||
- Watch the video: [Windows 10 for Mobile Devices: Provisioning Is Not Imaging](https://go.microsoft.com/fwlink/p/?LinkId=615922)
|
||||
- [Provisioning Windows 10 devices with new tools](https://go.microsoft.com/fwlink/p/?LinkId=615921)
|
||||
|
||||
- [Windows 10 for Mobile Devices: Provisioning Is Not Imaging](https://go.microsoft.com/fwlink/p/?LinkId=615922)
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
@ -85,6 +85,8 @@ landingContent:
|
||||
url: https://docs.microsoft.com/microsoft-365/solutions/empower-people-to-work-remotely
|
||||
- text: Top 12 tasks for security teams to support working from home
|
||||
url: https://docs.microsoft.com/microsoft-365/security/top-security-tasks-for-remote-work
|
||||
- text: Support your remote workforce
|
||||
url: https://docs.microsoft.com/microsoftteams/faq-support-remote-workforce
|
||||
|
||||
# Card (optional)
|
||||
- title: Microsoft Learn
|
||||
|
||||
@ -57,9 +57,9 @@ If these scenarios cannot be completed, Windows Autopilot for white glove deploy
|
||||
|
||||
To enable white glove deployment, an additional Autopilot profile setting must be configured by the customer or IT Admin via their Intune account, prior to beginning the white glove process in the provisioning service facility:
|
||||
|
||||
|
||||
|
||||
|
||||
The Windows Autopilot for white glove deployment pre-provisioning process will apply all device-targeted policies from Intune. That includes certificates, security templates, settings, apps, and more – anything targeting the device. Additionally, any apps (Win32 or LOB) that are configured to install in the device context and targeted to the user that has been pre-assigned to the Autopilot device will also be installed. Please make sure not to target both win32 and LOB apps to the same device.
|
||||
The Windows Autopilot for white glove deployment pre-provisioning process will apply all device-targeted policies from Intune. That includes certificates, security templates, settings, apps, and more – anything targeting the device. Additionally, any apps (Win32 or LOB) that are configured to install in the device context and targeted to the user that has been pre-assigned to the Autopilot device will also be installed. Please make sure not to target both win32 and LOB apps to the same device, as this can make troubleshooting difficult if there are app installation failures. For more information, see [Add a Windows line-of-business app to Microsoft Intune](https://docs.microsoft.com/mem/intune/apps/lob-apps-windows).
|
||||
|
||||
> [!NOTE]
|
||||
> The white glove technician phase will install all device-targeted apps as well as any user-targeted, device-context apps that are targeted to the assigned user. If there is no assigned user, then it will only install the device-targeted apps. Other user-targeted policies will not apply until the user signs into the device. To verify these behaviors, be sure to create appropriate apps and policies targeted to devices and users.
|
||||
|
||||
@ -99,7 +99,9 @@ Windows Hello for Business with a key does not support RDP. RDP does not support
|
||||
|
||||
## Learn more
|
||||
|
||||
[Implementing Windows Hello for Business at Microsoft](https://www.microsoft.com/itshowcase/implementing-windows-hello-for-business-at-microsoft)
|
||||
[Implementing strong user authentication with Windows Hello for Business](https://www.microsoft.com/en-us/itshowcase/implementing-strong-user-authentication-with-windows-hello-for-business)
|
||||
|
||||
[Implementing Windows Hello for Business at Microsoft](https://www.microsoft.com/en-us/itshowcase/implementing-windows-hello-for-business-at-microsoft)
|
||||
|
||||
[Introduction to Windows Hello](https://go.microsoft.com/fwlink/p/?LinkId=786649), video presentation on Microsoft Virtual Academy
|
||||
|
||||
|
||||
@ -49,9 +49,9 @@ lastEventTime | Nullable DateTimeOffset | The last occurrence of the event that
|
||||
firstEventTime | Nullable DateTimeOffset | The first occurrence of the event that triggered the alert on that device.
|
||||
lastUpdateTime | Nullable DateTimeOffset | The date and time (in UTC) the alert was last updated.
|
||||
resolvedTime | Nullable DateTimeOffset | The date and time in which the status of the alert was changed to 'Resolved'.
|
||||
incidentId | Nullable Long | The [Incident](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/view-incidents-queue) ID of the Alert.
|
||||
investigationId | Nullable Long | The [Investigation](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/automated-investigations) ID related to the Alert.
|
||||
investigationState | Nullable Enum | The current state of the [Investigation](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/automated-investigations). Possible values are: 'Unknown', 'Terminated', 'SuccessfullyRemediated', 'Benign', 'Failed', 'PartiallyRemediated', 'Running', 'PendingApproval', 'PendingResource', 'PartiallyInvestigated', 'TerminatedByUser', 'TerminatedBySystem', 'Queued', 'InnerFailure', 'PreexistingAlert', 'UnsupportedOs', 'UnsupportedAlertType', 'SuppressedAlert'.
|
||||
incidentId | Nullable Long | The [Incident](view-incidents-queue.md) ID of the Alert.
|
||||
investigationId | Nullable Long | The [Investigation](automated-investigations.md) ID related to the Alert.
|
||||
investigationState | Nullable Enum | The current state of the [Investigation](automated-investigations.md). Possible values are: 'Unknown', 'Terminated', 'SuccessfullyRemediated', 'Benign', 'Failed', 'PartiallyRemediated', 'Running', 'PendingApproval', 'PendingResource', 'PartiallyInvestigated', 'TerminatedByUser', 'TerminatedBySystem', 'Queued', 'InnerFailure', 'PreexistingAlert', 'UnsupportedOs', 'UnsupportedAlertType', 'SuppressedAlert'.
|
||||
assignedTo | String | Owner of the alert.
|
||||
severity | Enum | Severity of the alert. Possible values are: 'UnSpecified', 'Informational', 'Low', 'Medium' and 'High'.
|
||||
status | Enum | Specifies the current status of the alert. Possible values are: 'Unknown', 'New', 'InProgress' and 'Resolved'.
|
||||
@ -61,6 +61,8 @@ category| String | Category of the alert.
|
||||
detectionSource | String | Detection source.
|
||||
threatFamilyName | String | Threat family.
|
||||
machineId | String | ID of a [machine](machine.md) entity that is associated with the alert.
|
||||
computerDnsName | String | [machine](machine.md) fully qualified name.
|
||||
aadTenantId | String | The Azure Active Directory ID.
|
||||
comments | List of Alert comments | Alert Comment is an object that contains: comment string, createdBy string and createTime date time.
|
||||
|
||||
### Response example for getting single alert:
|
||||
|
||||
@ -33,7 +33,7 @@ ms.date: 04/16/2020
|
||||
Microsoft Defender ATP supports non-persistent VDI session onboarding.
|
||||
|
||||
>[!Note]
|
||||
>To onboard non-persistent VDI sessions, VDI machines must be on Windows 10.
|
||||
>To onboard non-persistent VDI sessions, VDI devices must be on Windows 10.
|
||||
>
|
||||
>While other Windows versions might work, only Windows 10 is supported.
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Onboard servers to the Microsoft Defender ATP service
|
||||
description: Onboard servers so that they can send sensor data to the Microsoft Defender ATP sensor.
|
||||
title: Onboard Windows servers to the Microsoft Defender ATP service
|
||||
description: Onboard Windows servers so that they can send sensor data to the Microsoft Defender ATP sensor.
|
||||
keywords: onboard server, server, 2012r2, 2016, 2019, server onboarding, device management, configure Windows ATP servers, onboard Microsoft Defender Advanced Threat Protection servers
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
search.appverid: met150
|
||||
@ -17,7 +17,7 @@ ms.collection: M365-security-compliance
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Onboard servers to the Microsoft Defender ATP service
|
||||
# Onboard Windows servers to the Microsoft Defender ATP service
|
||||
|
||||
**Applies to:**
|
||||
|
||||
@ -34,7 +34,7 @@ ms.topic: article
|
||||
|
||||
Microsoft Defender ATP extends support to also include the Windows Server operating system. This support provides advanced attack detection and investigation capabilities seamlessly through the Microsoft Defender Security Center console.
|
||||
|
||||
The service supports the onboarding of the following servers:
|
||||
The service supports the onboarding of the following Windows servers:
|
||||
- Windows Server 2008 R2 SP1
|
||||
- Windows Server 2012 R2
|
||||
- Windows Server 2016
|
||||
@ -44,38 +44,41 @@ The service supports the onboarding of the following servers:
|
||||
|
||||
For a practical guidance on what needs to be in place for licensing and infrastructure, see [Protecting Windows Servers with Microsoft Defender ATP](https://techcommunity.microsoft.com/t5/What-s-New/Protecting-Windows-Server-with-Windows-Defender-ATP/m-p/267114#M128).
|
||||
|
||||
For guidance on how to download and use Windows Security Baselines for Windows servers, see [Windows Security Baselines](https://docs.microsoft.com/windows/device-security/windows-security-baselines).
|
||||
|
||||
|
||||
## Windows Server 2008 R2 SP1, Windows Server 2012 R2, and Windows Server 2016
|
||||
|
||||
There are two options to onboard Windows Server 2008 R2 SP1, Windows Server 2012 R2 and Windows Server 2016 to Microsoft Defender ATP:
|
||||
You can onboard Windows Server 2008 R2 SP1, Windows Server 2012 R2, and Windows Server 2016 to Microsoft Defender ATP by using any of the following options:
|
||||
|
||||
- **Option 1**: Onboard through Microsoft Defender Security Center
|
||||
- **Option 2**: Onboard through Azure Security Center
|
||||
- **Option 1**: [Onboard through Microsoft Defender Security Center](#option-1-onboard-windows-servers-through-microsoft-defender-security-center)
|
||||
- **Option 2**: [Onboard through Azure Security Center](#option-2-onboard-windows-servers-through-azure-security-center)
|
||||
- **Option 3**: [Onboard through Microsoft Endpoint Configuration Manager version 2002 and later (only for Windows Server 2012 R2 and Windows Server 2016)](#option-3-onboard-windows-servers-through-microsoft-endpoint-configuration-manager-version-2002-and-later)
|
||||
|
||||
> [!NOTE]
|
||||
> Microsoft defender ATP standalone server license is required, per node, in order to onboard the server through Microsoft Defender Security Center (Option 1), or an Azure Security Center Standard license is required, per node, in order to onboard a server through Azure Security Center (Option 2), see [Supported features available in Azure Security Center](https://docs.microsoft.com/azure/security-center/security-center-services).
|
||||
> Microsoft defender ATP standalone server license is required, per node, in order to onboard a Windows server through Microsoft Defender Security Center (Option 1), or an Azure Security Center Standard license is required, per node, in order to onboard a Windows server through Azure Security Center (Option 2), see [Supported features available in Azure Security Center](https://docs.microsoft.com/azure/security-center/security-center-services).
|
||||
|
||||
|
||||
### Option 1: Onboard servers through Microsoft Defender Security Center
|
||||
You'll need to take the following steps if you choose to onboard servers through Microsoft Defender Security Center.
|
||||
### Option 1: Onboard Windows servers through Microsoft Defender Security Center
|
||||
Perform the following steps to onboard Windows servers through Microsoft Defender Security Center:
|
||||
|
||||
- For Windows Server 2008 R2 SP1 or Windows Server 2012 R2, ensure that you install the following hotfix:
|
||||
- [Update for customer experience and diagnostic telemetry](https://support.microsoft.com/en-us/help/3080149/update-for-customer-experience-and-diagnostic-telemetry)
|
||||
- [Update for customer experience and diagnostic telemetry](https://support.microsoft.com/help/3080149/update-for-customer-experience-and-diagnostic-telemetry)
|
||||
|
||||
- In addition, for Windows Server 2008 R2 SP1, ensure that you fulfill the following requirements:
|
||||
- Install the [February monthly update rollup](https://support.microsoft.com/en-us/help/4074598/windows-7-update-kb4074598)
|
||||
- Install the [February monthly update rollup](https://support.microsoft.com/help/4074598/windows-7-update-kb4074598)
|
||||
- Install either [.NET framework 4.5](https://www.microsoft.com/download/details.aspx?id=30653) (or later) or [KB3154518](https://support.microsoft.com/help/3154518/support-for-tls-system-default-versions-included-in-the-net-framework)
|
||||
|
||||
- For Windows Server 2008 R2 SP1 and Windows Server 2012 R2: Configure and update System Center Endpoint Protection clients.
|
||||
- For Windows Server 2008 R2 SP1 and Windows Server 2012 R2: [Configure and update System Center Endpoint Protection clients](#configure-and-update-system-center-endpoint-protection-clients).
|
||||
|
||||
> [!NOTE]
|
||||
> This step is required only if your organization uses System Center Endpoint Protection (SCEP) and you're onboarding Windows Server 2008 R2 SP1 and Windows Server 2012 R2.
|
||||
|
||||
- Turn on server monitoring from Microsoft Defender Security Center.
|
||||
- [Turn on server monitoring from Microsoft Defender Security Center](#turn-on-server-monitoring-from-the-microsoft-defender-security-center-portal).
|
||||
|
||||
- If you're already leveraging System Center Operations Manager (SCOM) or Azure Monitor (formerly known as Operations Management Suite (OMS)), attach the Microsoft Monitoring Agent (MMA) to report to your Microsoft Defender ATP workspace through Multihoming support.
|
||||
|
||||
Otherwise, install and configure MMA to report sensor data to Microsoft Defender ATP as instructed below. For more information, see [Collect log data with Azure Log Analytics agent](https://docs.microsoft.com/azure/azure-monitor/platform/log-analytics-agent).
|
||||
Otherwise, [install and configure MMA to report sensor data to Microsoft Defender ATP](#install-and-configure-microsoft-monitoring-agent-mma-to-report-sensor-data-to-microsoft-defender-atp). For more information, see [Collect log data with Azure Log Analytics agent](https://docs.microsoft.com/azure/azure-monitor/platform/log-analytics-agent).
|
||||
|
||||
> [!TIP]
|
||||
> After onboarding the device, you can choose to run a detection test to verify that it is properly onboarded to the service. For more information, see [Run a detection test on a newly onboarded Microsoft Defender ATP endpoint](run-detection-test.md).
|
||||
@ -94,7 +97,7 @@ The following steps are required to enable this integration:
|
||||
|
||||
1. In the navigation pane, select **Settings** > **Device management** > **Onboarding**.
|
||||
|
||||
2. Select Windows Server 2008 R2 SP1, 2012 R2 and 2016 as the operating system.
|
||||
2. Select **Windows Server 2008 R2 SP1, 2012 R2 and 2016** as the operating system.
|
||||
|
||||
3. Click **Turn on server monitoring** and confirm that you'd like to proceed with the environment setup. When the setup completes, the **Workspace ID** and **Workspace key** fields are populated with unique values. You'll need to use these values to configure the MMA agent.
|
||||
|
||||
@ -104,52 +107,50 @@ The following steps are required to enable this integration:
|
||||
|
||||
1. Download the agent setup file: [Windows 64-bit agent](https://go.microsoft.com/fwlink/?LinkId=828603).
|
||||
|
||||
2. Using the Workspace ID and Workspace key provided in the previous procedure, choose any of the following installation methods to install the agent on the server:
|
||||
2. Using the Workspace ID and Workspace key obtained in the previous procedure, choose any of the following installation methods to install the agent on the Windows server:
|
||||
- [Manually install the agent using setup](https://docs.microsoft.com/azure/log-analytics/log-analytics-windows-agents#install-the-agent-using-setup) <br>
|
||||
On the **Agent Setup Options** page, choose **Connect the agent to Azure Log Analytics (OMS)**.
|
||||
- [Install the agent using the command line](https://docs.microsoft.com/azure/log-analytics/log-analytics-windows-agents#install-the-agent-using-the-command-line) and [configure the agent using a script](https://docs.microsoft.com/azure/log-analytics/log-analytics-windows-agents#add-a-workspace-using-a-script).
|
||||
|
||||
3. You'll need to configure proxy settings for the Microsoft Monitoring Agent. For more information, see [Configure proxy settings](configure-proxy-internet.md).
|
||||
|
||||
Once completed, you should see onboarded servers in the portal within an hour.
|
||||
Once completed, you should see onboarded Windows servers in the portal within an hour.
|
||||
|
||||
<span id="server-proxy"/>
|
||||
|
||||
### Configure server proxy and Internet connectivity settings
|
||||
### Configure Windows server proxy and Internet connectivity settings
|
||||
|
||||
- Each Windows server must be able to connect to the Internet using HTTPS. This connection can be direct, using a proxy, or through the <a href="https://docs.microsoft.com/azure/log-analytics/log-analytics-oms-gateway" data-raw-source="[OMS Gateway](https://docs.microsoft.com/azure/log-analytics/log-analytics-oms-gateway)">OMS Gateway</a>.
|
||||
- If a proxy or firewall is blocking all traffic by default and allowing only specific domains through or HTTPS scanning (SSL inspection) is enabled, make sure that you [enable access to Microsoft Defender ATP service URLs](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/configure-proxy-internet#enable-access-to-microsoft-defender-atp-service-urls-in-the-proxy-server).
|
||||
|
||||
### Option 2: Onboard Windows servers through Azure Security Center
|
||||
1. In the Microsoft Defender Security Center navigation pane, select **Settings** > **Device management** > **Onboarding**.
|
||||
|
||||
|
||||
### Option 2: Onboard servers through Azure Security Center
|
||||
1. In the navigation pane, select **Settings** > **Device management** > **Onboarding**.
|
||||
|
||||
2. Select Windows Server 2008 R2 SP1, 2012 R2 and 2016 as the operating system.
|
||||
2. Select **Windows Server 2008 R2 SP1, 2012 R2 and 2016** as the operating system.
|
||||
|
||||
3. Click **Onboard Servers in Azure Security Center**.
|
||||
|
||||
4. Follow the onboarding instructions in [Microsoft Defender Advanced Threat Protection with Azure Security Center](https://docs.microsoft.com/azure/security-center/security-center-wdatp).
|
||||
|
||||
### Option 3: Onboard Windows servers through Microsoft Endpoint Configuration Manager version 2002 and later
|
||||
You can onboard Windows Server 2012 R2 and Windows Server 2016 by using Microsoft Endpoint Configuration Manager version 2002 and later. For more information, see [Microsoft Defender Advanced Threat Protection in Microsoft Endpoint Configuration Manager current branch](https://docs.microsoft.com/mem/configmgr/protect/deploy-use/defender-advanced-threat-protection).
|
||||
|
||||
## Windows Server (SAC) version 1803, Windows Server 2019, and Windows Server 2019 Core edition
|
||||
To onboard Windows Server (SAC) version 1803, Windows Server 2019, or Windows Server 2019 Core edition, refer to the supported methods and versions below.
|
||||
You can onboard Windows Server (SAC) version 1803, Windows Server 2019, or Windows Server 2019 Core edition by using the following deployment methods:
|
||||
|
||||
- [Local script](configure-endpoints-script.md)
|
||||
- [Group Policy](configure-endpoints-gp.md)
|
||||
- [Microsoft Endpoint Configuration Manager](configure-endpoints-sccm.md#onboard-windows-10-devices-using-microsoft-endpoint-configuration-manager-current-branch)
|
||||
- [System Center Configuration Manager 2012 / 2012 R2 1511 / 1602](configure-endpoints-sccm.md#onboard-windows-10-devices-using-earlier-versions-of-system-center-configuration-manager)
|
||||
- [VDI onboarding scripts for non-persistent devices](configure-endpoints-vdi.md)
|
||||
|
||||
> [!NOTE]
|
||||
> The Onboarding package for Windows Server 2019 through Microsoft Endpoint Configuration Manager currently ships a script. For more information on how to deploy scripts in Configuration Manager, see [Packages and programs in Configuration Manager](https://docs.microsoft.com/configmgr/apps/deploy-use/packages-and-programs).
|
||||
> - The Onboarding package for Windows Server 2019 through Microsoft Endpoint Configuration Manager currently ships a script. For more information on how to deploy scripts in Configuration Manager, see [Packages and programs in Configuration Manager](https://docs.microsoft.com/configmgr/apps/deploy-use/packages-and-programs).
|
||||
> - A local script is suitable for a proof of concept but should not be used for production deployment. For a production deployment, we recommend using Group Policy, Microsoft Endpoint Configuration Manager, or Intune.
|
||||
|
||||
Supported tools include:
|
||||
- Local script
|
||||
- Group Policy
|
||||
- Microsoft Endpoint Configuration Manager
|
||||
- System Center Configuration Manager 2012 / 2012 R2 1511 / 1602
|
||||
- VDI onboarding scripts for non-persistent devices
|
||||
Support for Windows Server, provide deeper insight into activities happening on the Windows server, coverage for kernel and memory attack detection, and enables response actions on Windows Server endpoint as well.
|
||||
|
||||
For more information, see [Onboard Windows 10 devices](configure-endpoints.md).
|
||||
|
||||
Support for Windows Server, provide deeper insight into activities happening on the server, coverage for kernel and memory attack detection, and enables response actions on Windows Server endpoint as well.
|
||||
|
||||
1. Configure Microsoft Defender ATP onboarding settings on the server. For more information, see [Onboard Windows 10 devices](configure-endpoints.md).
|
||||
1. Configure Microsoft Defender ATP onboarding settings on the Windows server. For more information, see [Onboard Windows 10 devices](configure-endpoints.md).
|
||||
|
||||
2. If you're running a third-party antimalware solution, you'll need to apply the following Microsoft Defender AV passive mode settings. Verify that it was configured correctly:
|
||||
|
||||
@ -175,9 +176,10 @@ Support for Windows Server, provide deeper insight into activities happening on
|
||||
|
||||
If the result is 'The specified service does not exist as an installed service', then you'll need to install Microsoft Defender AV. For more information, see [Microsoft Defender Antivirus in Windows 10](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-antivirus/microsoft-defender-antivirus-in-windows-10).
|
||||
|
||||
For information on how to use Group Policy to configure and manage Microsoft Defender Antivirus on your Windows servers, see [Use Group Policy settings to configure and manage Microsoft Defender Antivirus](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-antivirus/use-group-policy-microsoft-defender-antivirus).
|
||||
|
||||
## Integration with Azure Security Center
|
||||
Microsoft Defender ATP can integrate with Azure Security Center to provide a comprehensive server protection solution. With this integration, Azure Security Center can leverage the power of Microsoft Defender ATP to provide improved threat detection for Windows Servers.
|
||||
Microsoft Defender ATP can integrate with Azure Security Center to provide a comprehensive Windows server protection solution. With this integration, Azure Security Center can leverage the power of Microsoft Defender ATP to provide improved threat detection for Windows Servers.
|
||||
|
||||
The following capabilities are included in this integration:
|
||||
- Automated onboarding - Microsoft Defender ATP sensor is automatically enabled on Windows Servers that are onboarded to Azure Security Center. For more information on Azure Security Center onboarding, see [Onboarding to Azure Security Center Standard for enhanced security](https://docs.microsoft.com/azure/security-center/security-center-onboarding).
|
||||
@ -185,31 +187,30 @@ The following capabilities are included in this integration:
|
||||
> [!NOTE]
|
||||
> Automated onboarding is only applicable for Windows Server 2008 R2 SP1, Windows Server 2012 R2, and Windows Server 2016.
|
||||
|
||||
- Servers monitored by Azure Security Center will also be available in Microsoft Defender ATP - Azure Security Center seamlessly connects to the Microsoft Defender ATP tenant, providing a single view across clients and servers. In addition, Microsoft Defender ATP alerts will be available in the Azure Security Center console.
|
||||
- Windows servers monitored by Azure Security Center will also be available in Microsoft Defender ATP - Azure Security Center seamlessly connects to the Microsoft Defender ATP tenant, providing a single view across clients and servers. In addition, Microsoft Defender ATP alerts will be available in the Azure Security Center console.
|
||||
- Server investigation - Azure Security Center customers can access Microsoft Defender Security Center to perform detailed investigation to uncover the scope of a potential breach.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> - When you use Azure Security Center to monitor servers, a Microsoft Defender ATP tenant is automatically created (in the US for US users, in the EU for European and UK users).
|
||||
> - If you use Microsoft Defender ATP before using Azure Security Center, your data will be stored in the location you specified when you created your tenant even if you integrate with Azure Security Center at a later time.
|
||||
> - When you use Azure Security Center to monitor servers, a Microsoft Defender ATP tenant is automatically created and the Microsoft Defender ATP data is stored in Europe by default. If you need to move your data to another location, you need to contact Microsoft Support to reset the tenant. Server endpoint monitoring utilizing this integration has been disabled for Office 365 GCC customers.
|
||||
> - When you use Azure Security Center to monitor Windows servers, a Microsoft Defender ATP tenant is automatically created and the Microsoft Defender ATP data is stored in Europe by default. If you need to move your data to another location, you need to contact Microsoft Support to reset the tenant. Server endpoint monitoring utilizing this integration has been disabled for Office 365 GCC customers.
|
||||
|
||||
|
||||
## Offboard servers
|
||||
## Offboard Windows servers
|
||||
You can offboard Windows Server (SAC), Windows Server 2019, and Windows Server 2019 Core edition in the same method available for Windows 10 client devices.
|
||||
|
||||
For other server versions, you have two options to offboard servers from the service:
|
||||
For other Windows server versions, you have two options to offboard Windows servers from the service:
|
||||
- Uninstall the MMA agent
|
||||
- Remove the Microsoft Defender ATP workspace configuration
|
||||
|
||||
> [!NOTE]
|
||||
> Offboarding causes the server to stop sending sensor data to the portal but data from the server, including reference to any alerts it has had will be retained for up to 6 months.
|
||||
> Offboarding causes the Windows server to stop sending sensor data to the portal but data from the Windows server, including reference to any alerts it has had will be retained for up to 6 months.
|
||||
|
||||
### Uninstall servers by uninstalling the MMA agent
|
||||
To offboard the server, you can uninstall the MMA agent from the server or detach it from reporting to your Microsoft Defender ATP workspace. After offboarding the agent, the server will no longer send sensor data to Microsoft Defender ATP.
|
||||
### Uninstall Windows servers by uninstalling the MMA agent
|
||||
To offboard the Windows server, you can uninstall the MMA agent from the Windows server or detach it from reporting to your Microsoft Defender ATP workspace. After offboarding the agent, the Windows server will no longer send sensor data to Microsoft Defender ATP.
|
||||
For more information, see [To disable an agent](https://docs.microsoft.com/azure/log-analytics/log-analytics-windows-agents#to-disable-an-agent).
|
||||
|
||||
### Remove the Microsoft Defender ATP workspace configuration
|
||||
To offboard the server, you can use either of the following methods:
|
||||
To offboard the Windows server, you can use either of the following methods:
|
||||
|
||||
- Remove the Microsoft Defender ATP workspace configuration from the MMA agent
|
||||
- Run a PowerShell command to remove the configuration
|
||||
@ -230,7 +231,7 @@ To offboard the server, you can use either of the following methods:
|
||||
|
||||
1. Select **Windows Server 2008 R2 SP1, 2012 R2 and 2016** as the operating system and get your Workspace ID:
|
||||
|
||||
|
||||
|
||||
|
||||
2. Open an elevated PowerShell and run the following command. Use the Workspace ID you obtained and replacing `WorkspaceID`:
|
||||
|
||||
@ -242,7 +243,6 @@ To offboard the server, you can use either of the following methods:
|
||||
# Reload the configuration and apply changes
|
||||
$AgentCfg.ReloadConfiguration()
|
||||
```
|
||||
|
||||
## Related topics
|
||||
- [Onboard Windows 10 devices](configure-endpoints.md)
|
||||
- [Onboard non-Windows devices](configure-endpoints-non-windows.md)
|
||||
|
||||
@ -29,45 +29,113 @@ Not all properties are filterable.
|
||||
|
||||
## Properties that supports $filter:
|
||||
|
||||
- [Alert](alerts.md): Id, IncidentId, AlertCreationTime, Status, Severity and Category.
|
||||
- [Machine](machine.md): Id, ComputerDnsName, LastSeen, LastIpAddress, HealthStatus, OsPlatform, RiskScore, MachineTags and RbacGroupId.
|
||||
- [MachineAction](machineaction.md): Id, Status, MachineId, Type, Requestor and CreationDateTimeUtc.
|
||||
- [Alert](alerts.md): ```alertCreationTime```, ```lastUpdateTime```, ```incidentId```,```InvestigationId```, ```status```, ```severity``` and ```category```.
|
||||
- [Machine](machine.md): ```ComputerDnsName```, ```LastSeen```, ```HealthStatus```, ```OsPlatform```, ```RiskScore``` and ```RbacGroupId```.
|
||||
- [MachineAction](machineaction.md): ```Status```, ```MachineId```, ```Type```, ```Requestor``` and ```CreationDateTimeUtc```.
|
||||
- [Indicator](ti-indicator.md): ```indicatorValue```, ```indicatorType```, ```creationTimeDateTimeUtc```, ```createdBy```, ```severity ``` and ```action ```.
|
||||
|
||||
### Example 1
|
||||
|
||||
Get all the devices with the tag 'ExampleTag'
|
||||
Get 10 latest Alerts with related Evidence
|
||||
|
||||
```
|
||||
HTTP GET https://api.securitycenter.windows.com/api/machines?$filter=machineTags/any(tag: tag eq 'ExampleTag')
|
||||
HTTP GET https://api.securitycenter.microsoft.com/api/alerts?$top=10&$expand=evidence
|
||||
```
|
||||
|
||||
**Response:**
|
||||
|
||||
```
|
||||
HTTP/1.1 200 OK
|
||||
Content-type: application/json
|
||||
```json
|
||||
{
|
||||
"@odata.context": "https://api.securitycenter.windows.com/api/$metadata#Machines",
|
||||
"@odata.context": "https://api.securitycenter.microsoft.com/api/$metadata#Alerts",
|
||||
"value": [
|
||||
{
|
||||
"id": "1e5bc9d7e413ddd7902c2932e418702b84d0cc07",
|
||||
"computerDnsName": "mymachine1.contoso.com",
|
||||
"firstSeen": "2018-08-02T14:55:03.7791856Z",
|
||||
"lastSeen": "2018-08-02T14:55:03.7791856Z",
|
||||
"osPlatform": "Windows10",
|
||||
"version": "1709",
|
||||
"osProcessor": "x64",
|
||||
"lastIpAddress": "172.17.230.209",
|
||||
"lastExternalIpAddress": "167.220.196.71",
|
||||
"osBuild": 18209,
|
||||
"healthStatus": "Active",
|
||||
"rbacGroupId": 140,
|
||||
"rbacGroupName": "The-A-Team",
|
||||
"riskScore": "Low",
|
||||
"exposureLevel": "Medium",
|
||||
"isAadJoined": true,
|
||||
"aadDeviceId": "80fe8ff8-2624-418e-9591-41f0491218f9",
|
||||
"machineTags": [ "test tag 1", "ExampleTag" ]
|
||||
"id": "da637306396589640224_1753239473",
|
||||
"incidentId": 875832,
|
||||
"investigationId": 478434,
|
||||
"assignedTo": null,
|
||||
"severity": "Low",
|
||||
"status": "New",
|
||||
"classification": null,
|
||||
"determination": null,
|
||||
"investigationState": "PendingApproval",
|
||||
"detectionSource": "WindowsDefenderAv",
|
||||
"category": "UnwantedSoftware",
|
||||
"threatFamilyName": "InstallCore",
|
||||
"title": "An active 'InstallCore' unwanted software was detected",
|
||||
"description": "Potentially unwanted applications (PUA) often impact productivity and performance and are often unwanted in enterprise environments. This category of applications include torrent downloaders, cryptocurrency miners, browser advertising software, and evasion software.\n\nAn application is considered active if it is found running on the machine or it already has persistence mechanisms in place.\n\nBecause this PUA was active, take precautionary measures and check for residual signs of infection.",
|
||||
"alertCreationTime": "2020-07-18T03:27:38.9483995Z",
|
||||
"firstEventTime": "2020-07-18T03:25:39.6124549Z",
|
||||
"lastEventTime": "2020-07-18T03:26:18.4362304Z",
|
||||
"lastUpdateTime": "2020-07-18T03:28:19.76Z",
|
||||
"resolvedTime": null,
|
||||
"machineId": "97868b864dc8fa09cc8726c37a1fcd8ab582f3aa",
|
||||
"computerDnsName": "temp2.redmond.corp.microsoft.com",
|
||||
"rbacGroupName": "Ring0",
|
||||
"aadTenantId": "12f988bf-1234-1234-91ab-2d7cd011db47",
|
||||
"relatedUser": {
|
||||
"userName": "temp2",
|
||||
"domainName": "REDMOND"
|
||||
},
|
||||
"comments": [],
|
||||
"evidence": [
|
||||
{
|
||||
"entityType": "File",
|
||||
"sha1": "ff02786682af8a6ae2842b64c8da543c4d76823c",
|
||||
"sha256": "16dafd771171b619a472bb23cd55bc069625be8de5ee01b37b41de1216b2bbb2",
|
||||
"fileName": "Your File Is Ready To Download_1911150169.exe",
|
||||
"filePath": "C:\\Users\\temp2\\Downloads",
|
||||
"processId": null,
|
||||
"processCommandLine": null,
|
||||
"processCreationTime": null,
|
||||
"parentProcessId": null,
|
||||
"parentProcessCreationTime": null,
|
||||
"ipAddress": null,
|
||||
"url": null,
|
||||
"accountName": null,
|
||||
"domainName": null,
|
||||
"userSid": null,
|
||||
"aadUserId": null,
|
||||
"userPrincipalName": null
|
||||
},
|
||||
{
|
||||
"entityType": "Process",
|
||||
"sha1": "ff02786682af8a6ae2842b64c8da543c4d76823c",
|
||||
"sha256": "16dafd771171b619a472bb23cd55bc069625be8de5ee01b37b41de1216b2bbb2",
|
||||
"fileName": "Your File Is Ready To Download_1911150169.exe",
|
||||
"filePath": "C:\\Users\\temp2\\Downloads",
|
||||
"processId": 24348,
|
||||
"processCommandLine": "\"Your File Is Ready To Download_1911150169.exe\" ",
|
||||
"processCreationTime": "2020-07-18T03:25:38.5269993Z",
|
||||
"parentProcessId": 16840,
|
||||
"parentProcessCreationTime": "2020-07-18T02:12:32.8616797Z",
|
||||
"ipAddress": null,
|
||||
"url": null,
|
||||
"accountName": null,
|
||||
"domainName": null,
|
||||
"userSid": null,
|
||||
"aadUserId": null,
|
||||
"userPrincipalName": null
|
||||
},
|
||||
{
|
||||
"entityType": "User",
|
||||
"sha1": null,
|
||||
"sha256": null,
|
||||
"fileName": null,
|
||||
"filePath": null,
|
||||
"processId": null,
|
||||
"processCommandLine": null,
|
||||
"processCreationTime": null,
|
||||
"parentProcessId": null,
|
||||
"parentProcessCreationTime": null,
|
||||
"ipAddress": null,
|
||||
"url": null,
|
||||
"accountName": "temp2",
|
||||
"domainName": "REDMOND",
|
||||
"userSid": "S-1-5-21-1127532184-1642412920-1887927527-75363",
|
||||
"aadUserId": "319dc320-4ce3-4cd7-a0de-c476d146342d",
|
||||
"userPrincipalName": "temp2@microsoft.com"
|
||||
}
|
||||
]
|
||||
},
|
||||
...
|
||||
]
|
||||
@ -76,49 +144,55 @@ Content-type: application/json
|
||||
|
||||
### Example 2
|
||||
|
||||
Get all the alerts that created after 2018-10-20 00:00:00
|
||||
Get all the alerts last updated after 2019-10-20 00:00:00
|
||||
|
||||
```
|
||||
HTTP GET https://api.securitycenter.windows.com/api/alerts?$filter=alertCreationTime+gt+2018-11-22T00:00:00Z
|
||||
HTTP GET https://api.securitycenter.windows.com/api/alerts?$filter=lastUpdateTime+ge+2019-11-22T00:00:00Z
|
||||
```
|
||||
|
||||
**Response:**
|
||||
|
||||
```
|
||||
HTTP/1.1 200 OK
|
||||
Content-type: application/json
|
||||
```json
|
||||
{
|
||||
"@odata.context": "https://api.securitycenter.windows.com/api/$metadata#Alerts",
|
||||
"value": [
|
||||
{
|
||||
"id": "da637084217856368682_-292920499",
|
||||
"incidentId": 66860,
|
||||
"investigationId": 4416234,
|
||||
"investigationState": "Running",
|
||||
"assignedTo": "secop@contoso.com",
|
||||
"id": "da637308392288907382_-880718168",
|
||||
"incidentId": 7587,
|
||||
"investigationId": 723156,
|
||||
"assignedTo": "secop123@contoso.com",
|
||||
"severity": "Low",
|
||||
"status": "New",
|
||||
"classification": "TruePositive",
|
||||
"determination": null,
|
||||
"detectionSource": "WindowsDefenderAtp",
|
||||
"category": "CommandAndControl",
|
||||
"threatFamilyName": null,
|
||||
"title": "Network connection to a risky host",
|
||||
"description": "A network connection was made to a risky host which has exhibited malicious activity.",
|
||||
"alertCreationTime": "2019-11-03T23:49:45.3823185Z",
|
||||
"firstEventTime": "2019-11-03T23:47:16.2288822Z",
|
||||
"lastEventTime": "2019-11-03T23:47:51.2966758Z",
|
||||
"lastUpdateTime": "2019-11-03T23:55:52.6Z",
|
||||
"investigationState": "Queued",
|
||||
"detectionSource": "WindowsDefenderAv",
|
||||
"category": "SuspiciousActivity",
|
||||
"threatFamilyName": "Meterpreter",
|
||||
"title": "Suspicious 'Meterpreter' behavior was detected",
|
||||
"description": "Malware and unwanted software are undesirable applications that perform annoying, disruptive, or harmful actions on affected machines. Some of these undesirable applications can replicate and spread from one machine to another. Others are able to receive commands from remote attackers and perform activities associated with cyber attacks.\n\nA malware is considered active if it is found running on the machine or it already has persistence mechanisms in place. Active malware detections are assigned higher severity ratings.\n\nBecause this malware was active, take precautionary measures and check for residual signs of infection.",
|
||||
"alertCreationTime": "2020-07-20T10:53:48.7657932Z",
|
||||
"firstEventTime": "2020-07-20T10:52:17.6654369Z",
|
||||
"lastEventTime": "2020-07-20T10:52:18.1362905Z",
|
||||
"lastUpdateTime": "2020-07-20T10:53:50.19Z",
|
||||
"resolvedTime": null,
|
||||
"machineId": "986e5df8b73dacd43c8917d17e523e76b13c75cd",
|
||||
"machineId": "12ee6dd8c833c8a052ea231ec1b19adaf497b625",
|
||||
"computerDnsName": "temp123.middleeast.corp.microsoft.com",
|
||||
"rbacGroupName": "MiddleEast",
|
||||
"aadTenantId": "a839b112-1253-6432-9bf6-94542403f21c",
|
||||
"relatedUser": {
|
||||
"userName": "temp123",
|
||||
"domainName": "MIDDLEEAST"
|
||||
},
|
||||
"comments": [
|
||||
{
|
||||
"comment": "test comment for docs",
|
||||
"createdBy": "secop@contoso.com",
|
||||
"createdTime": "2019-11-05T14:08:37.8404534Z"
|
||||
"createdBy": "secop123@contoso.com",
|
||||
"createdTime": "2020-07-21T01:00:37.8404534Z"
|
||||
}
|
||||
],
|
||||
"evidence": []
|
||||
}
|
||||
]
|
||||
},
|
||||
...
|
||||
]
|
||||
}
|
||||
@ -134,9 +208,7 @@ HTTP GET https://api.securitycenter.windows.com/api/machines?$filter=riskScore+
|
||||
|
||||
**Response:**
|
||||
|
||||
```
|
||||
HTTP/1.1 200 OK
|
||||
Content-type: application/json
|
||||
```json
|
||||
{
|
||||
"@odata.context": "https://api.securitycenter.windows.com/api/$metadata#Machines",
|
||||
"value": [
|
||||
@ -175,9 +247,7 @@ HTTP GET https://api.securitycenter.windows.com/api/machines?$filter=healthStat
|
||||
|
||||
**Response:**
|
||||
|
||||
```
|
||||
HTTP/1.1 200 OK
|
||||
Content-type: application/json
|
||||
```json
|
||||
{
|
||||
"@odata.context": "https://api.securitycenter.windows.com/api/$metadata#Machines",
|
||||
"value": [
|
||||
@ -216,9 +286,7 @@ HTTP GET https://api.securitycenter.windows.com/api/machines?$filter=lastSeen g
|
||||
|
||||
**Response:**
|
||||
|
||||
```
|
||||
HTTP/1.1 200 OK
|
||||
Content-type: application/json
|
||||
```json
|
||||
{
|
||||
"@odata.context": "https://api.securitycenter.windows.com/api/$metadata#Machines",
|
||||
"value": [
|
||||
@ -257,10 +325,8 @@ HTTP GET https://api.securitycenter.windows.com/api/machineactions?$filter=requ
|
||||
|
||||
**Response:**
|
||||
|
||||
```
|
||||
HTTP/1.1 200 OK
|
||||
Content-type: application/json
|
||||
{
|
||||
```json
|
||||
json{
|
||||
"@odata.context": "https://api.securitycenter.windows.com/api/$metadata#MachineActions",
|
||||
"value": [
|
||||
{
|
||||
@ -291,10 +357,7 @@ HTTP GET https://api.securitycenter.windows.com/api/machines/123321d0c675eaa415
|
||||
|
||||
**Response:**
|
||||
|
||||
```
|
||||
HTTP/1.1 200 OK
|
||||
Content-type: application/json
|
||||
|
||||
```json
|
||||
4
|
||||
```
|
||||
|
||||
|
||||
@ -26,7 +26,11 @@ ms.topic: article
|
||||
## API description
|
||||
Retrieves a collection of Alerts.
|
||||
<br>Supports [OData V4 queries](https://www.odata.org/documentation/).
|
||||
<br>The OData's ```$filter``` query is supported on: ```alertCreationTime```, ```lastUpdateTime```, ```incidentId```,```InvestigationId```, ```status```, ```severity``` and ```category``` properties.
|
||||
<br>OData supported operators:
|
||||
<br>```$filter``` on: ```alertCreationTime```, ```lastUpdateTime```, ```incidentId```,```InvestigationId```, ```status```, ```severity``` and ```category``` properties.
|
||||
<br>```$top``` with max value of 10,000
|
||||
<br>```$skip```
|
||||
<br>```$expand``` of ```evidence```
|
||||
<br>See examples at [OData queries with Microsoft Defender ATP](exposed-apis-odata-samples.md)
|
||||
|
||||
|
||||
@ -70,14 +74,14 @@ Empty
|
||||
If successful, this method returns 200 OK, and a list of [alert](alerts.md) objects in the response body.
|
||||
|
||||
|
||||
## Example
|
||||
## Example 1 - Default
|
||||
|
||||
**Request**
|
||||
|
||||
Here is an example of the request.
|
||||
|
||||
```
|
||||
GET https://api.securitycenter.windows.com/api/alerts
|
||||
GET https://api.securitycenter.microsoft.com/api/alerts
|
||||
```
|
||||
|
||||
[!include[Improve request performance](../../includes/improve-request-performance.md)]
|
||||
@ -93,41 +97,167 @@ Here is an example of the response.
|
||||
|
||||
```json
|
||||
{
|
||||
"@odata.context": "https://api.securitycenter.windows.com/api/$metadata#Alerts",
|
||||
"@odata.context": "https://api.securitycenter.microsoft.com/api/$metadata#Alerts",
|
||||
"value": [
|
||||
{
|
||||
"id": "da637084217856368682_-292920499",
|
||||
"incidentId": 66860,
|
||||
"investigationId": 4416234,
|
||||
"assignedTo": "secop@contoso.com",
|
||||
"id": "da637308392288907382_-880718168",
|
||||
"incidentId": 7587,
|
||||
"investigationId": 723156,
|
||||
"assignedTo": "secop123@contoso.com",
|
||||
"severity": "Low",
|
||||
"status": "New",
|
||||
"classification": "TruePositive",
|
||||
"determination": null,
|
||||
"investigationState": "Running",
|
||||
"detectionSource": "WindowsDefenderAtp",
|
||||
"category": "CommandAndControl",
|
||||
"threatFamilyName": null,
|
||||
"title": "Network connection to a risky host",
|
||||
"description": "A network connection was made to a risky host which has exhibited malicious activity.",
|
||||
"alertCreationTime": "2019-11-03T23:49:45.3823185Z",
|
||||
"firstEventTime": "2019-11-03T23:47:16.2288822Z",
|
||||
"lastEventTime": "2019-11-03T23:47:51.2966758Z",
|
||||
"lastUpdateTime": "2019-11-03T23:55:52.6Z",
|
||||
"investigationState": "Queued",
|
||||
"detectionSource": "WindowsDefenderAv",
|
||||
"category": "SuspiciousActivity",
|
||||
"threatFamilyName": "Meterpreter",
|
||||
"title": "Suspicious 'Meterpreter' behavior was detected",
|
||||
"description": "Malware and unwanted software are undesirable applications that perform annoying, disruptive, or harmful actions on affected machines. Some of these undesirable applications can replicate and spread from one machine to another. Others are able to receive commands from remote attackers and perform activities associated with cyber attacks.\n\nA malware is considered active if it is found running on the machine or it already has persistence mechanisms in place. Active malware detections are assigned higher severity ratings.\n\nBecause this malware was active, take precautionary measures and check for residual signs of infection.",
|
||||
"alertCreationTime": "2020-07-20T10:53:48.7657932Z",
|
||||
"firstEventTime": "2020-07-20T10:52:17.6654369Z",
|
||||
"lastEventTime": "2020-07-20T10:52:18.1362905Z",
|
||||
"lastUpdateTime": "2020-07-20T10:53:50.19Z",
|
||||
"resolvedTime": null,
|
||||
"machineId": "986e5df8b73dacd43c8917d17e523e76b13c75cd",
|
||||
"machineId": "12ee6dd8c833c8a052ea231ec1b19adaf497b625",
|
||||
"computerDnsName": "temp123.middleeast.corp.microsoft.com",
|
||||
"rbacGroupName": "MiddleEast",
|
||||
"aadTenantId": "a839b112-1253-6432-9bf6-94542403f21c",
|
||||
"relatedUser": {
|
||||
"userName": "temp123",
|
||||
"domainName": "MIDDLEEAST"
|
||||
},
|
||||
"comments": [
|
||||
{
|
||||
"comment": "test comment for docs",
|
||||
"createdBy": "secop@contoso.com",
|
||||
"createdTime": "2019-11-05T14:08:37.8404534Z"
|
||||
"createdBy": "secop123@contoso.com",
|
||||
"createdTime": "2020-07-21T01:00:37.8404534Z"
|
||||
}
|
||||
]
|
||||
],
|
||||
"evidence": []
|
||||
}
|
||||
...
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
## Example 2 - Get 10 latest Alerts with related Evidence
|
||||
|
||||
**Request**
|
||||
|
||||
Here is an example of the request.
|
||||
|
||||
```
|
||||
GET https://api.securitycenter.microsoft.com/api/alerts?$top=10&$expand=evidence
|
||||
```
|
||||
|
||||
|
||||
**Response**
|
||||
|
||||
Here is an example of the response.
|
||||
|
||||
>[!NOTE]
|
||||
>The response list shown here may be truncated for brevity. All alerts will be returned from an actual call.
|
||||
|
||||
|
||||
```json
|
||||
{
|
||||
"@odata.context": "https://api.securitycenter.microsoft.com/api/$metadata#Alerts",
|
||||
"value": [
|
||||
{
|
||||
"id": "da637306396589640224_1753239473",
|
||||
"incidentId": 875832,
|
||||
"investigationId": 478434,
|
||||
"assignedTo": null,
|
||||
"severity": "Low",
|
||||
"status": "New",
|
||||
"classification": null,
|
||||
"determination": null,
|
||||
"investigationState": "PendingApproval",
|
||||
"detectionSource": "WindowsDefenderAv",
|
||||
"category": "UnwantedSoftware",
|
||||
"threatFamilyName": "InstallCore",
|
||||
"title": "An active 'InstallCore' unwanted software was detected",
|
||||
"description": "Potentially unwanted applications (PUA) often impact productivity and performance and are often unwanted in enterprise environments. This category of applications include torrent downloaders, cryptocurrency miners, browser advertising software, and evasion software.\n\nAn application is considered active if it is found running on the machine or it already has persistence mechanisms in place.\n\nBecause this PUA was active, take precautionary measures and check for residual signs of infection.",
|
||||
"alertCreationTime": "2020-07-18T03:27:38.9483995Z",
|
||||
"firstEventTime": "2020-07-18T03:25:39.6124549Z",
|
||||
"lastEventTime": "2020-07-18T03:26:18.4362304Z",
|
||||
"lastUpdateTime": "2020-07-18T03:28:19.76Z",
|
||||
"resolvedTime": null,
|
||||
"machineId": "97868b864dc8fa09cc8726c37a1fcd8ab582f3aa",
|
||||
"computerDnsName": "temp2.redmond.corp.microsoft.com",
|
||||
"rbacGroupName": "Ring0",
|
||||
"aadTenantId": "12f988bf-1234-1234-91ab-2d7cd011db47",
|
||||
"relatedUser": {
|
||||
"userName": "temp2",
|
||||
"domainName": "REDMOND"
|
||||
},
|
||||
"comments": [],
|
||||
"evidence": [
|
||||
{
|
||||
"entityType": "File",
|
||||
"sha1": "ff02786682af8a6ae2842b64c8da543c4d76823c",
|
||||
"sha256": "16dafd771171b619a472bb23cd55bc069625be8de5ee01b37b41de1216b2bbb2",
|
||||
"fileName": "Your File Is Ready To Download_1911150169.exe",
|
||||
"filePath": "C:\\Users\\temp2\\Downloads",
|
||||
"processId": null,
|
||||
"processCommandLine": null,
|
||||
"processCreationTime": null,
|
||||
"parentProcessId": null,
|
||||
"parentProcessCreationTime": null,
|
||||
"ipAddress": null,
|
||||
"url": null,
|
||||
"accountName": null,
|
||||
"domainName": null,
|
||||
"userSid": null,
|
||||
"aadUserId": null,
|
||||
"userPrincipalName": null
|
||||
},
|
||||
{
|
||||
"entityType": "Process",
|
||||
"sha1": "ff02786682af8a6ae2842b64c8da543c4d76823c",
|
||||
"sha256": "16dafd771171b619a472bb23cd55bc069625be8de5ee01b37b41de1216b2bbb2",
|
||||
"fileName": "Your File Is Ready To Download_1911150169.exe",
|
||||
"filePath": "C:\\Users\\temp2\\Downloads",
|
||||
"processId": 24348,
|
||||
"processCommandLine": "\"Your File Is Ready To Download_1911150169.exe\" ",
|
||||
"processCreationTime": "2020-07-18T03:25:38.5269993Z",
|
||||
"parentProcessId": 16840,
|
||||
"parentProcessCreationTime": "2020-07-18T02:12:32.8616797Z",
|
||||
"ipAddress": null,
|
||||
"url": null,
|
||||
"accountName": null,
|
||||
"domainName": null,
|
||||
"userSid": null,
|
||||
"aadUserId": null,
|
||||
"userPrincipalName": null
|
||||
},
|
||||
{
|
||||
"entityType": "User",
|
||||
"sha1": null,
|
||||
"sha256": null,
|
||||
"fileName": null,
|
||||
"filePath": null,
|
||||
"processId": null,
|
||||
"processCommandLine": null,
|
||||
"processCreationTime": null,
|
||||
"parentProcessId": null,
|
||||
"parentProcessCreationTime": null,
|
||||
"ipAddress": null,
|
||||
"url": null,
|
||||
"accountName": "temp2",
|
||||
"domainName": "REDMOND",
|
||||
"userSid": "S-1-5-21-1127532184-1642412920-1887927527-75363",
|
||||
"aadUserId": "319dc320-4ce3-4cd7-a0de-c476d146342d",
|
||||
"userPrincipalName": "temp2@microsoft.com"
|
||||
}
|
||||
]
|
||||
},
|
||||
...
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
|
||||
## Related topics
|
||||
- [OData queries with Microsoft Defender ATP](exposed-apis-odata-samples.md)
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Get all vulnerabilities by Machine and Software
|
||||
title: Get all vulnerabilities by machine and software
|
||||
description: Retrieves a list of all the vulnerabilities affecting the organization by Machine and Software
|
||||
keywords: apis, graph api, supported apis, get, vulnerability information, mdatp tvm api
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
@ -16,13 +16,14 @@ ms.collection: M365-security-compliance
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# List vulnerabilities by Machine and Software
|
||||
# List vulnerabilities by machine and software
|
||||
|
||||
**Applies to:** [Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP)](https://go.microsoft.com/fwlink/p/?linkid=2069559)
|
||||
|
||||
Retrieves a list of all the vulnerabilities affecting the organization per [Machine](machine.md) and [Software](software.md).
|
||||
<br>If the vulnerability has a fixing KB, it will appear in the response.
|
||||
<br>Supports [OData V4 queries](https://www.odata.org/documentation/).
|
||||
<br>The OData ```$filter``` is supported on all properties.
|
||||
Retrieves a list of all the vulnerabilities affecting the organization per [machine](machine.md) and [software](software.md).
|
||||
- If the vulnerability has a fixing KB, it will appear in the response.
|
||||
- Supports [OData V4 queries](https://www.odata.org/documentation/).
|
||||
- The OData ```$filter``` is supported on all properties.
|
||||
|
||||
>[!Tip]
|
||||
>This is great API for [Power BI integration](api-power-bi.md).
|
||||
@ -100,5 +101,6 @@ Here is an example of the response.
|
||||
```
|
||||
|
||||
## Related topics
|
||||
- [Risk-based Threat & Vulnerability Management](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/next-gen-threat-and-vuln-mgt)
|
||||
|
||||
- [Risk-based threat and vulnerability management](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/next-gen-threat-and-vuln-mgt)
|
||||
- [Vulnerabilities in your organization](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/tvm-weaknesses)
|
||||
|
||||
@ -26,7 +26,7 @@ ms.topic: article
|
||||
## API description
|
||||
Retrieves a collection of [Machines](machine.md) that have communicated with Microsoft Defender ATP cloud on the last 30 days.
|
||||
<br>Supports [OData V4 queries](https://www.odata.org/documentation/).
|
||||
<br>The OData's ```$filter``` query is supported on: ```computerDnsName```, ```lastSeen```, ```lastIpAddress```, ```healthStatus```, ```osPlatform```, ```riskScore```, ```rbacGroupId``` and ```machineTags``` properties.
|
||||
<br>The OData's ```$filter``` query is supported on: ```computerDnsName```, ```lastSeen```, ```healthStatus```, ```osPlatform```, ```riskScore``` and ```rbacGroupId```.
|
||||
<br>See examples at [OData queries with Microsoft Defender ATP](exposed-apis-odata-samples.md)
|
||||
|
||||
|
||||
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 273 KiB After Width: | Height: | Size: 273 KiB |
@ -67,6 +67,9 @@ You can specify the file names that you want to be excluded in a specific direct
|
||||
|
||||
4. Click **Save**.
|
||||
|
||||
>[!NOTE]
|
||||
> Live Response commands to collect or examine excluded files will fail with error: "File is excluded". In addition, automated investigations will ignore the excluded items.
|
||||
|
||||
## Edit an automation folder exclusion
|
||||
1. In the navigation pane, select **Settings** > **Automation folder exclusions**.
|
||||
|
||||
|
||||
@ -110,6 +110,7 @@ See the following topics for related APIs:
|
||||
- [Score APIs](score.md)
|
||||
- [Software APIs](software.md)
|
||||
- [Vulnerability APIs](vulnerability.md)
|
||||
- [List vulnerabilities by machine and software](get-all-vulnerabilities-by-machines.md)
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
@ -37,7 +37,7 @@ Follow the corresponding instructions depending on your preferred deployment met
|
||||
- [Offboard devices using Mobile Device Management tools](configure-endpoints-mdm.md#offboard-and-monitor-devices-using-mobile-device-management-tools)
|
||||
|
||||
## Offboard Servers
|
||||
- [Offboard servers](configure-server-endpoints.md#offboard-servers)
|
||||
- [Offboard servers](configure-server-endpoints.md#offboard-windows-servers)
|
||||
|
||||
## Offboard non-Windows devices
|
||||
- [Offboard non-Windows devices](configure-endpoints-non-windows.md#offboard-non-windows-devices)
|
||||
|
||||
@ -49,9 +49,9 @@ Deployment methods vary, depending on which operating system is selected. Refer
|
||||
|---------|---------|
|
||||
|Windows 10 |- [Group Policy](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/configure-endpoints-gp)<br/>- [Configuration Manager](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/configure-endpoints-sccm)<br/>- [Mobile Device Management (Intune)](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/configure-endpoints-mdm)<br/>- [Local script](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/configure-endpoints-script) <br/><br/>**NOTE**: A local script is suitable for a proof of concept but should not be used for production deployment. For a production deployment, we recommend using Group Policy, Microsoft Endpoint Configuration Manager, or Intune. |
|
||||
|- Windows 8.1 Enterprise <br/>- Windows 8.1 Pro <br/>- Windows 7 SP1 Enterprise <br/>- Windows 7 SP1 Pro | [Microsoft Monitoring Agent](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/onboard-downlevel#install-and-configure-microsoft-monitoring-agent-mma-to-report-sensor-data-to-microsoft-defender-atp)<br/><br/>**NOTE**: Microsoft Monitoring Agent is now Azure Log Analytics agent. To learn more, see [Log Analytics agent overview](https://docs.microsoft.com/azure/azure-monitor/platform/log-analytics-agent). |
|
||||
|- Windows Server 2019 and later <br/>- Windows Server 2019 core edition <br/>- Windows Server version 1803 and later |- [Local script](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/configure-endpoints-script) <br/>- [Group Policy](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/configure-endpoints-gp) <br/>- [Configuration Manager](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/configure-endpoints-sccm) <br/>- [System Center Configuration Manager](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/configure-endpoints-sccm#onboard-windows-10-machines-using-earlier-versions-of-system-center-configuration-manager) <br/>- [VDI onboarding scripts for non-persistent machines](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/configure-endpoints-vdi) <br/><br/>**NOTE**: A local script is suitable for a proof of concept but should not be used for production deployment. For a production deployment, we recommend using Group Policy, Microsoft Endpoint Configuration Manager, or Intune. |
|
||||
|- Windows Server 2019 and later <br/>- Windows Server 2019 core edition <br/>- Windows Server version 1803 and later |- [Local script](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/configure-endpoints-script) <br/>- [Group Policy](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/configure-endpoints-gp) <br/>- [Configuration Manager](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/configure-endpoints-sccm) <br/>- [System Center Configuration Manager](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/configure-endpoints-sccm#onboard-windows-10-devices-using-earlier-versions-of-system-center-configuration-manager) <br/>- [VDI onboarding scripts for non-persistent devices](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/configure-endpoints-vdi) <br/><br/>**NOTE**: A local script is suitable for a proof of concept but should not be used for production deployment. For a production deployment, we recommend using Group Policy, Microsoft Endpoint Configuration Manager, or Intune. |
|
||||
|- Windows Server 2016 <br/>- Windows Server 2012 R2 <br/>- Windows Server 2008 R2 SP1 |- [Microsoft Defender Security Center](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/configure-server-endpoints#option-1-onboard-servers-through-microsoft-defender-security-center)<br/>- [Azure Security Center](https://docs.microsoft.com/azure/security-center/security-center-wdatp) |
|
||||
|macOS<br/>- 10.15 (Catalina)<br/>- 10.14 (Mojave)<br/>- 10.13 (High Sierra)<br/><br/>iOS<br/><br/>Linux:<br/>- RHEL 7.2+<br/>- CentOS Linux 7.2+<br/>- Ubuntu 16 LTS, or higher LTS<br/>- SLES 12+<br/>- Debian 9+<br/>- Oracle Linux 7.2 |[Onboard non-Windows machines](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/configure-endpoints-non-windows) |
|
||||
|macOS<br/>- 10.15 (Catalina)<br/>- 10.14 (Mojave)<br/>- 10.13 (High Sierra)<br/><br/>iOS<br/><br/>Linux:<br/>- RHEL 7.2+<br/>- CentOS Linux 7.2+<br/>- Ubuntu 16 LTS, or higher LTS<br/>- SLES 12+<br/>- Debian 9+<br/>- Oracle Linux 7.2 |[Onboard non-Windows devices](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/configure-endpoints-non-windows) |
|
||||
|
||||
## Run a detection test
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user