Repository navigation
Conversation
One Security 4688 event (line 83) closed its CommandLine element with </fData> instead of </Data>, so it was not well-formed XML. Replace it. The file is one byte shorter. Refs splunk#1270
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.
Fixes #1270.
Line 83 of
datasets/attack_techniques/T1059/excessive_distinct_processes_from_windows_temp/windows-xml.logcloses theCommandLineelement of a Security 4688 event with</fData>. This change replaces it with</Data>. That is the only change to the file content:</fData>becomes</Data>, so the file is one byte shorter (191,553 to 191,552 bytes) and the LFS pointer holds the new object id.Checked:
xml.etree.ElementTree). Before, line 83 did not.XmlWinEventLog:Securitythatdata.ymldeclares, all 136 events getProcess_Command_Line. With the old file, 135 do.