Correct Sysmon event-type documentation (Events 27-29) and fix eBPF link#50
Merged
darkoperator merged 1 commit intoJun 30, 2026
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.
Several accuracy fixes to the Sysmon event documentation. The "Windows Supported Event Types"
table stopped at Event 26 even though the guide already has dedicated chapters for File Block
Executable, File Block Shredding and File Executable Detected. The File Block Shredding chapter
also listed the wrong event ID, and the
What is Sysmonchapter linked to the wrong GitHub repofor the sysinternalsEBPF library (the guide's own eBPF chapter has the correct one).
Changes
chapters/what-is-sysmon.mdhttps://github.com/Sysinternals/SysinternalsEBPF(was the unrelatedebpf-for-windowsrepo; confirmed againstchapters/eBPF.md).Sysmon64a.exe, event coverage identical to x64 (same IDs/schema), and that the native build is required becauseSysmonDrvmust match the OS architecture.chapters/file-blockshredding.md