ASUS AI EDR Windows telemetry#206
Open
shine0614 wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🖥️ EDR Telemetry Pull Request
📝 Contribution Details
This PR adds Windows telemetry coverage based on validation and testing using the official EDR Telemetry Windows testing methodology.
Telemetry validation used the provided
telemetry-generator.ps1workflow, Atomic Red Team simulations, and manual verification via the EDR dashboard, telemetry events, and sanitized logs.For telemetry categories not covered or reproducible through
telemetry-generator.ps1or Atomic Red Team, manual behavioral testing validated telemetry collection. This included controlled execution of Windows-native commands, PowerShell simulations, registry modifications, WMI event subscription testing, service activity, named pipe activity, and other relevant system behaviors.For telemetry categories without directly observable native OS-level events, behavioral validation used available telemetry sources (e.g., PowerShell Script Block Logging, WMI events, service activity, and command execution evidence).
✅ Validation Details
EDR Product Information
📊 Telemetry Validation
We validated telemetry by:
telemetry-generator.ps1)🪟 Windows Telemetry Coverage Validation
lsass.execreated successfully but execution timed outW64Timeservice creation observedFaxservice unavailable on tested Windows buildsekurlsa::logonpasswordsblocked by LSASS access protection (0x00000005)📊 Telemetry Evidence
event.action=process-created,event.type=creation,event.code=1event.action=process-exited,event.type=end,event.code=2event.action=process-accessed,provider=Microsoft-Windows-Kernel-Audit-API-Calls,event.code=6DllImport("kernel32.dll"),GetCurrentProcess()observed in Script Block Logging (4104)event.action=image-loaded,event.code=5event.action=thread-created,event.code=3process.stack_traceobservedevent.action=file-created,event.code=30event.action=file-opened,event.code=14event.action=file-modified,event.code=16Remove-Item "$env:TEMP\EDRTestFile.txt"observed in Script Block Logging (4104)lsass.exerename simulation)event.category=network,event.action=connectionevent.code=4104, PowerShell Script Block Logging observedRemove-ItemProperty,Remove-Item HKCU:\Software\EDRTestW64Time, test service)service_status_changeobservedSERVICE_KERNEL_DRIVER) observedHKLM\Software\Policies\Microsoft\Windows\Systemregistry modification observedGet-CimInstance Win32_ShadowCopy | Remove-CimInstanceNamedPipeServerStream,NamedPipeClientStreamobserved📃 Documentation or Evidence
📋 Proof Document
Evidence includes EDR dashboard screenshots and sanitized telemetry logs collected during validation.
Process Telemetry
Observed through PowerShell Script Block Logging rather than native Win32 API ETW telemetry.
File Telemetry
File deletion behavior observed through PowerShell Script Block Logging (4104).
Account Telemetry
Network Telemetry
Registry Telemetry
Scheduled Task Telemetry
Service Telemetry
Driver Telemetry
Device Telemetry
Group Policy Telemetry
Observed through PowerShell script block telemetry rather than native Group Policy file monitoring
Pipe Telemetry
WMI Telemetry
BITS Telemetry
Agent Telemetry
💡 Type of Contribution
Additional Notes
All testing was performed in a controlled environment.
Sensitive information present in screenshots and logs has been sanitized where applicable.
Some telemetry categories were validated through behavioral evidence (e.g., PowerShell Script Block Logging, WMI activity, service telemetry, and command execution traces) where native OS-level events were not directly observable within the current telemetry pipeline.