-
Notifications
You must be signed in to change notification settings - Fork 266
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
Improve handling of registry hives #185
Comments
So I have not full checked the format but Chainsaw already supports So to write a rule, kind just needs to be set to |
The rule would need to look something like this:
Which could then be run like so
Some sort of container that can pull out matching values from an array of objects would probably need to be implemented to solve the array of values output noise. |
That will be great. Also an abstraction for the rules to be able to translate HKEY_LOCAL_MACHINE\SYSTEM in the rule format to SYSTEM hive file (without needing to put '\ROOT'). Changing the hive files to .hve also feels unnecessary (isn't there a file header or something?) Thanks for the help! |
That is doable too, but would need some code changes to handle that behind the scenes. You can bypass having to add |
I would like to have the ability to create rules on registry hives, for example:
I think that this feature will allow to get a lot value from the registry hives, both in forensics and threat hunting.
The text was updated successfully, but these errors were encountered: