mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-15 06:47:21 +00:00
Merge remote-tracking branch 'refs/remotes/origin/atp-telemetry'
This commit is contained in:
commit
f802a78b9a
@ -45,7 +45,7 @@ You can also manually onboard individual endpoints to Windows Defender ATP. You
|
|||||||
|
|
||||||
5. Press the **Enter** key or click **OK**.
|
5. Press the **Enter** key or click **OK**.
|
||||||
|
|
||||||
For for information on how you can manually validate that the endpoint is compliant and correctly reports telemetry see, [Troubleshoot Windows Defender Advanced Threat Protection onboarding issues](troubleshoot-onboarding-windows-defender-advanced-threat-protection.md).
|
For for information on how you can manually validate that the endpoint is compliant and correctly reports sensor data see, [Troubleshoot Windows Defender Advanced Threat Protection onboarding issues](troubleshoot-onboarding-windows-defender-advanced-threat-protection.md).
|
||||||
|
|
||||||
## Configure sample collection settings
|
## Configure sample collection settings
|
||||||
For each endpoint, you can set a configuration value to state whether samples can be collected from the endpoint when a request is made through the Windows Defender ATP portal to submit a file for deep analysis.
|
For each endpoint, you can set a configuration value to state whether samples can be collected from the endpoint when a request is made through the Windows Defender ATP portal to submit a file for deep analysis.
|
||||||
|
@ -21,7 +21,7 @@ localizationpriority: high
|
|||||||
- Windows 10 Pro Education
|
- Windows 10 Pro Education
|
||||||
- Windows Defender Advanced Threat Protection (Windows Defender ATP)
|
- Windows Defender Advanced Threat Protection (Windows Defender ATP)
|
||||||
|
|
||||||
Endpoints in your organization must be configured so that the Windows Defender ATP service can get telemetry from them. There are various methods and deployment tools that you can use to configure the endpoints in your organization.
|
Endpoints in your organization must be configured so that the Windows Defender ATP service can get sensor data from them. There are various methods and deployment tools that you can use to configure the endpoints in your organization.
|
||||||
|
|
||||||
Windows Defender ATP supports the following deployment tools and methods:
|
Windows Defender ATP supports the following deployment tools and methods:
|
||||||
|
|
||||||
|
@ -22,7 +22,7 @@ localizationpriority: high
|
|||||||
- Windows 10 Pro Education
|
- Windows 10 Pro Education
|
||||||
- Windows Defender Advanced Threat Protection (Windows Defender ATP)
|
- Windows Defender Advanced Threat Protection (Windows Defender ATP)
|
||||||
|
|
||||||
The Window Defender ATP sensor requires Microsoft Windows HTTP (WinHTTP) to report telemetry and communicate with the Windows Defender ATP service.
|
The Window Defender ATP sensor requires Microsoft Windows HTTP (WinHTTP) to report sensor data and communicate with the Windows Defender ATP service.
|
||||||
|
|
||||||
The embedded Windows Defender ATP sensor runs in system context using the LocalSystem account. The sensor uses Microsoft Windows HTTP Services (WinHTTP) to enable communication with the Windows Defender ATP cloud service.
|
The embedded Windows Defender ATP sensor runs in system context using the LocalSystem account. The sensor uses Microsoft Windows HTTP Services (WinHTTP) to enable communication with the Windows Defender ATP cloud service.
|
||||||
|
|
||||||
|
@ -21,12 +21,12 @@ localizationpriority: high
|
|||||||
- Windows 10 Pro Education
|
- Windows 10 Pro Education
|
||||||
- Windows Defender Advanced Threat Protection (Windows Defender ATP)
|
- Windows Defender Advanced Threat Protection (Windows Defender ATP)
|
||||||
|
|
||||||
The **Machines view** shows a list of the machines in your network, the corresponding number of active alerts for each machine categorized by alert severity levels, and the number of active malware detections. This view allows you to identify machines with the highest risk at a glance, and keep track of all the machines that are reporting telemetry in your network.
|
The **Machines view** shows a list of the machines in your network, the corresponding number of active alerts for each machine categorized by alert severity levels, and the number of active malware detections. This view allows you to identify machines with the highest risk at a glance, and keep track of all the machines that are reporting sensor data in your network.
|
||||||
|
|
||||||
Use the Machines view in these two main scenarios:
|
Use the Machines view in these two main scenarios:
|
||||||
|
|
||||||
- **During onboarding**
|
- **During onboarding**
|
||||||
- During the onboarding process, the Machines view gradually gets populated with endpoints as they begin to report telemetry. Use this view to track your onboarded endpoints as they appear. Use the available features to sort and filer to see which endpoints have most recently reported telemetry, or download the complete endpoint list as a CSV file for offline analysis.
|
- During the onboarding process, the Machines view gradually gets populated with endpoints as they begin to report sensor data. Use this view to track your onboarded endpoints as they appear. Use the available features to sort and filer to see which endpoints have most recently reported sensor data, or download the complete endpoint list as a CSV file for offline analysis.
|
||||||
- **Day-to-day work**
|
- **Day-to-day work**
|
||||||
- The **Machines view** enables you to identify machines that are most at risk in a glance. High-risk machines are those with the greatest number and highest-severity alerts. By sorting the machines by risk, you'll be able to identify the most vulnerable machines and take action on them.
|
- The **Machines view** enables you to identify machines that are most at risk in a glance. High-risk machines are those with the greatest number and highest-severity alerts. By sorting the machines by risk, you'll be able to identify the most vulnerable machines and take action on them.
|
||||||
|
|
||||||
@ -34,7 +34,7 @@ The Machines view contains the following columns:
|
|||||||
|
|
||||||
- **Machine name** - the name or GUID of the machine
|
- **Machine name** - the name or GUID of the machine
|
||||||
- **Domain** - the domain the machine belongs to
|
- **Domain** - the domain the machine belongs to
|
||||||
- **Last seen** - when the machine last reported telemetry
|
- **Last seen** - when the machine last reported sensor data
|
||||||
- **Internal IP** - the local internal Internet Protocol (IP) address of the machine
|
- **Internal IP** - the local internal Internet Protocol (IP) address of the machine
|
||||||
- **Active Alerts** - the number of alerts reported by the machine by severity
|
- **Active Alerts** - the number of alerts reported by the machine by severity
|
||||||
- **Active malware detections** - the number of active malware detections reported by the machine
|
- **Active malware detections** - the number of active malware detections reported by the machine
|
||||||
@ -59,7 +59,7 @@ You can filter the view by the following time periods:
|
|||||||
- 6 months
|
- 6 months
|
||||||
|
|
||||||
> [!NOTE]
|
> [!NOTE]
|
||||||
> When you select a time period, the list will only display machines that reported within the selected time period. For example, selecting 1 day will only display a list of machines that reported telemetry within the last 24-hour period.
|
> When you select a time period, the list will only display machines that reported within the selected time period. For example, selecting 1 day will only display a list of machines that reported sensor data within the last 24-hour period.
|
||||||
|
|
||||||
The threat category filter lets you filter the view by the following categories:
|
The threat category filter lets you filter the view by the following categories:
|
||||||
|
|
||||||
@ -94,7 +94,7 @@ When you investigate a specific machine, you'll see:
|
|||||||
- **Alerts related to this machine**
|
- **Alerts related to this machine**
|
||||||
- **Machine timeline**
|
- **Machine timeline**
|
||||||
|
|
||||||
The machine details, IP, and reporting sections display some attributes of the machine such as its name, domain, OS, IP address, and how long it's been reporting telemetry to the Windows Defender ATP service.
|
The machine details, IP, and reporting sections display some attributes of the machine such as its name, domain, OS, IP address, and how long it's been reporting sensor data to the Windows Defender ATP service.
|
||||||
|
|
||||||
The **Alerts related to this machine** section provides a list of alerts that are associated with the machine. This list is a simplified version of the [Alerts queue](alerts-queue-windows-defender-advanced-threat-protection.md), and shows the date that the alert was detected, a short description of the alert, the alert's severity, the alert's threat category, and the alert's status in the queue.
|
The **Alerts related to this machine** section provides a list of alerts that are associated with the machine. This list is a simplified version of the [Alerts queue](alerts-queue-windows-defender-advanced-threat-protection.md), and shows the date that the alert was detected, a short description of the alert, the alert's severity, the alert's threat category, and the alert's status in the queue.
|
||||||
|
|
||||||
|
@ -61,7 +61,7 @@ Before you configure endpoints, the telemetry and diagnostics service must be en
|
|||||||
|
|
||||||
### Telemetry and diagnostics settings
|
### Telemetry and diagnostics settings
|
||||||
You must ensure that the telemetry and diagnostics service is enabled on all the endpoints in your organization.
|
You must ensure that the telemetry and diagnostics service is enabled on all the endpoints in your organization.
|
||||||
By default, this service is enabled, but it's good practice to check to ensure that you'll get telemetry from them.
|
By default, this service is enabled, but it's good practice to check to ensure that you'll get sensor data from them.
|
||||||
|
|
||||||
**Use the command line to check the Windows 10 telemetry and diagnostics service startup type**:
|
**Use the command line to check the Windows 10 telemetry and diagnostics service startup type**:
|
||||||
|
|
||||||
|
@ -1,7 +1,7 @@
|
|||||||
---
|
---
|
||||||
title: Troubleshoot Windows Defender ATP onboarding issues
|
title: Troubleshoot Windows Defender ATP onboarding issues
|
||||||
description: Troubleshoot issues that might arise during the onboarding of endpoints or to the Windows Defender ATP service.
|
description: Troubleshoot issues that might arise during the onboarding of endpoints or to the Windows Defender ATP service.
|
||||||
keywords: troubleshoot onboarding, onboarding issues, event viewer, data collection and preview builds, telemetry and diagnostics
|
keywords: troubleshoot onboarding, onboarding issues, event viewer, data collection and preview builds, sensor data and diagnostics
|
||||||
search.product: eADQiWindows 10XVcnh
|
search.product: eADQiWindows 10XVcnh
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.mktglfcycl: deploy
|
ms.mktglfcycl: deploy
|
||||||
@ -214,7 +214,7 @@ First, you should check that the service is set to start automatically when Wind
|
|||||||
|
|
||||||
### Ensure the endpoint has an Internet connection
|
### Ensure the endpoint has an Internet connection
|
||||||
|
|
||||||
The Window Defender ATP sensor requires Microsoft Windows HTTP (WinHTTP) to report telemetry and communicate with the Windows Defender ATP service.
|
The Window Defender ATP sensor requires Microsoft Windows HTTP (WinHTTP) to report sensor data and communicate with the Windows Defender ATP service.
|
||||||
|
|
||||||
WinHTTP is independent of the Internet browsing proxy settings and other user context applications and must be able to detect the proxy servers that are available in your particular environment.
|
WinHTTP is independent of the Internet browsing proxy settings and other user context applications and must be able to detect the proxy servers that are available in your particular environment.
|
||||||
|
|
||||||
|
@ -32,7 +32,7 @@ Windows Defender ATP uses the following combination of technology built into Win
|
|||||||
- **Endpoint behavioral sensors**: Embedded in Windows 10, these sensors
|
- **Endpoint behavioral sensors**: Embedded in Windows 10, these sensors
|
||||||
collect and process behavioral signals from the operating system
|
collect and process behavioral signals from the operating system
|
||||||
(for example, process, registry, file, and network communications)
|
(for example, process, registry, file, and network communications)
|
||||||
and sends this telemetry to your private, isolated, cloud instance of Windows Defender ATP.
|
and sends this sensor data to your private, isolated, cloud instance of Windows Defender ATP.
|
||||||
|
|
||||||
|
|
||||||
- **Cloud security analytics**: Leveraging big-data, machine-learning, and
|
- **Cloud security analytics**: Leveraging big-data, machine-learning, and
|
||||||
@ -47,7 +47,7 @@ Windows Defender ATP uses the following combination of technology built into Win
|
|||||||
and augmented by threat intelligence provided by partners, threat
|
and augmented by threat intelligence provided by partners, threat
|
||||||
intelligence enables Windows Defender ATP to identify attacker
|
intelligence enables Windows Defender ATP to identify attacker
|
||||||
tools, techniques, and procedures, and generate alerts when these
|
tools, techniques, and procedures, and generate alerts when these
|
||||||
are observed in collected telemetry.
|
are observed in collected sensor data.
|
||||||
|
|
||||||
The following diagram shows these Windows Defender ATP service
|
The following diagram shows these Windows Defender ATP service
|
||||||
components:
|
components:
|
||||||
|
Loading…
x
Reference in New Issue
Block a user