The German Federal Office for Information Security, BSI (Bundesamt für Sicherheit in der Informationstechnik) published a detailed Windows 10 Telemetry analysis on November 20, 2018.
The research paper, which is available in English (partially) and German, provides a deep analysis of Telemetry functionality that Microsoft implemented in the company’s Windows 10 operating system.
The paper is based on Windows 10 version 1607 Enterprise. It covers:
- An overview of Windows 10’s event tracing functionality for Telemetry.
- A technical analysis on how Telemetry data is collected and processed.
- An analysis of the network interfaces and connections used to transfer Telemetry data.
- A look at configuration and logging capabilities to monitor and control Telemetry data collecting.
The report is quite technical in nature and the first couple of pages are only available in German at the time of writing. You may want to skip ahead to page 9, Executive Summary, if you don’t understand German; the English part of the report begins with chapter 1.2.
Tip: An extra, German-only, paper is available that includes system-based and network-based options to limit or block the collection or transfer of Telemetry data to Microsoft.
You find interesting tidbits in the report even if you are not interested in technicalities like the number of Event Tracing for Windows (ETW) providers associated with Autologger-Diagtrack-Listener and Diagtrack Listener for each of the supported Telemetry levels:
- Security — 9 and 4 ETW Providers
- Basic — 93 and 410 ETW Providers
- Enhanced — 105 and 418 ETW Providers
- Full — 112 and 422 ETW Providers
The Security telemetry level is reserved to Enterprise editions of Windows 10. Home users may choose between Basic and Full, and the difference in providers is not as large as one would think based on the analysis.
The number of ETW Providers stands in no direct correlation to the amount of data that is collected or its quality according to the researchers.
The report list hostnames and IP addresses that Windows 10’s Telemetry service uses for communication based on a connection log of 48 hours.
|us.vortex-win.data.microsft.com||220.127.116.11||United States, Boston|
|vortex-win-sandbox.data.microsoft.com||18.104.22.168||United States, LA|
|alpha.telemetry.microsft.com||22.214.171.124||United States, LA|
|oca.telemetry.microsft.com||126.96.36.199||United States, Cheyenne|
Last but not least, there is an appendix that list external executable files. Not all of them are used for Telemetry purposes though.
Here is the entire listing:
|%SystemRoot%System32telsvc.exe||No description available|
|%SystemRoot%SysWow64dtdump.exe||No description available|
|%SystemRoot%SysWow64RdrLeakDiag.exe||No description available|
|%SystemRoot %system32RdrLeakDiag.exe||No description available|
|%SystemRoot%system32appidtel.exe||No description available|
|%SystemRoot%system32disksnapshot.exe||No description available|
|%SystemRoot%system32bcdedit.exe||A tool for managing the Boot Configuration Database (BCD);|
|%SystemRoot%system32dxdiag.exe||A tool for collecting information on devices;|
|%SystemRoot%system32dispdiag.exe||A tool for collecting and logging information on displays;|
|%ProgramFiles%internet exploreriediagcmd.exe||No description available|
|%SystemRoot%system32icacls.exe||A tool for displaying and modifying access control lists;|
|%SystemRoot%system32licensingdiag.exe||No description available|
|%SystemRoot%system32ipconfig.exe||A tool for displaying network information and configuring network settings|
|%SystemRoot%system32msinfo32.exe||A tool for displaying information about the hardware and software enviroment deployed on a platform;|
|%SystemRoot%system32logman.exe||A tool for configuring, and displaying information about, the ETW environment;|
|%SystemRoot%system32netsh.exe||A tool for displaying network information and configuring network settings;|
|%SystemRoot%system32netcfg.exe||A tool for installing the Windows preinstallation environment, a lightweight version of Windows;|
|%SystemRoot%system32route.exe||A tool for displaying and modifying the platform’s IP routing table;|
|%SystemRoot%system32powercfg.exe||A tool for configuring power settings (e.g., configuring the platform’s standby mode)|
|%SystemRoot%system32stordiag.exe||No description available|
|%SystemRoot%system32settingsynchost.exe||No description available|
|%SystemRoot%system32verifier.exe||A tool for detecting and troubleshooting driver issues;|
|%SystemRoot%system32tracelog.exe||A tool for managing ETW environment (e.g., activation and deactivation of ETW sessions);|
|%SystemRoot%system32whoami.exe||A tool for displaying information on the user currently logged on to the system; https|
|%SystemRoot%system32wevtutil.exe||A tool for managing the EventLog environment;|
|%SystemRoot%system32wscollect.exe||No description available|
Administrators and researchers may also be interested in a tools and script package that was released as part of the analysis.
The reports provide detailed Telemetry information that is useful to interested Windows users but especially to administrators who want to know more about how Telemetry works on Windows 10 devices.