-
Notifications
You must be signed in to change notification settings - Fork 15
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
Please double check your research findings #7
Comments
The format looks like a simple value type container format where the first 5 bytes are part of the first value. |
Thanks for the detailed proof-read, Joachim. Still new to the field so some of the terminology is still coming to me, regarding "value type container formats" 😄 will look into these though, and double check some previous points I made as well. I appreciate the tips! |
Note that this is anything far from an actual proof read. I mostly only skimmed the material, and my observations did not match yours.
TL;DR a format that defines pairs of value types and data, e.g. type: string, value: "TEST" or type: integer, value: 99
Maybe interesting contextual read about the importance about reproducible test data https://osdfir.blogspot.com/2020/09/testing-digital-forensic-data.html Not to influence you too much but documentation of my current findings: https://github.com/libyal/dtformats/blob/main/documentation/Windows%20Defender%20scan%20DetectionHistory%20file%20format.asciidoc |
From README
The files appear to be generated even with cloud-delivered protection turned off.
There are files under the MputHistory directory that start with the same 5 bytes that contain different information. So it does not look like to be a "signature" (as in something that uniquely identifies the DetectionHistory files)
The text was updated successfully, but these errors were encountered: