The ETW logging may be local, but one of the main reasons to use ETW is high-performance logging to .etl files for offline analysis. Those files can then be re-processed and transmitted over the network at a later time. We won't know where the telemetry actually goes until Microsoft comments on it.
Also, while the invoked/returned part probably isn't a big deal, the full path will capture the username if the program is running from within the user profile. This can be a problem if the username counts as personally identifiable information for your purposes.
I suppose we should assume the etw logs are being collected and submitted to Microsoft as part of their telemetry. This is a very disturbing realization.
35
u/xon_xoff May 07 '16
The ETW logging may be local, but one of the main reasons to use ETW is high-performance logging to .etl files for offline analysis. Those files can then be re-processed and transmitted over the network at a later time. We won't know where the telemetry actually goes until Microsoft comments on it.
Also, while the invoked/returned part probably isn't a big deal, the full path will capture the username if the program is running from within the user profile. This can be a problem if the username counts as personally identifiable information for your purposes.