Add winlog.event_data.PrivilegeList to security events #547
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
ayfaouzi changed the title 
ayfaouzi force-pushed the ayfaouzi-etw-security-auditing branch from 6f9ad18 to 727535d Compare 
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.
Change Summary
This PR adds a custom schema for
winlogthat the security auditing provider produces.The reason for the uncommon casing is that we're trying to match the field that are defined in
winlogbeat: https://www.elastic.co/guide/en/beats/winlogbeat/current/exported-fields-winlog.htmlSample values
Here is an example of the (
winlog.event_data.PrivilegeList) that will be added by this PR.Release Target
8.16
For mapping changes:
makeafter making the schema changes, and committed all changes