Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding xml_string parsing to Windows EVTX parser (winevtx.py) #3988

Closed
rj-chap opened this issue Dec 7, 2021 · 2 comments
Closed

Adding xml_string parsing to Windows EVTX parser (winevtx.py) #3988

rj-chap opened this issue Dec 7, 2021 · 2 comments
Assignees
Labels
duplicate Duplicate of another issue question

Comments

@rj-chap
Copy link

rj-chap commented Dec 7, 2021

Currently, the Windows EVTX parser pulls out the 'xml_string' field, but does not parse the items within this field. Is it possible to have this field parsed such that the XML content, at least the key:value pairs, are available as field/values? e.g. TargetUserName from a 4625 event.

Reason: Many entities rely on regex'ing through the xml_string field. Yet regex'ing through XML data not only adds processing overhead, but just seems daffy given the structured nature of the format. While regex'ing the field can work, the processing impact on this can be great, especially when users are running Elastic on a laptop (i.e. not on a beautiful, kick-butt cluster).

If the community could get some additional parsing of the 'xml_string' field, this would make everyone's life that much easier. And better. And cooler.

Thanks!

@joachimmetz
Copy link
Member

@joachimmetz joachimmetz self-assigned this Dec 8, 2021
@joachimmetz
Copy link
Member

Duplicate of #442

@joachimmetz joachimmetz marked this as a duplicate of #442 Dec 8, 2021
@joachimmetz joachimmetz added the duplicate Duplicate of another issue label Dec 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate Duplicate of another issue question
Projects
None yet
Development

No branches or pull requests

2 participants