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

HexToDecimal field data mapping #1133

Closed
YamatoSecurity opened this issue Jul 19, 2023 · 3 comments
Closed

HexToDecimal field data mapping #1133

YamatoSecurity opened this issue Jul 19, 2023 · 3 comments
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@YamatoSecurity
Copy link
Collaborator

@fukusuket Could I ask you to do this one since you are now the most familiar with field data mapping?
No hurry, so it can be done in the next release if it will take time.
I added a HexToDecimal section in the config files here: https://github.com/Yamato-Security/hayabusa-rules/tree/main/config/data_mapping

Most time it will be just one field: HexToDecimal: 'ProcessId'

But sometimes can be multiple (EID: 4688):

HexToDecimal:
    - 'NewProcessId'
    - 'ProcessId'

Unfortunately most PIDs in Windows events are in hex so would be better to convert to decimal.
HexToDecimal will also be ignored when -F is used.
The ProcessId fields should probably always exist in the defined EIDs but may not in some circumstances so might want to test that hayabusa does not crash, etc.. if the field does not exist.

@YamatoSecurity YamatoSecurity added the enhancement New feature or request label Jul 19, 2023
@fukusuket
Copy link
Collaborator

@YamatoSecurity
Thank you for the mention :) Yes, I would love to implement it!💪

@YamatoSecurity
Copy link
Collaborator Author

@fukusuket Thank you so much! Then I will assign you to this one.

@YamatoSecurity
Copy link
Collaborator Author

closed by #1154

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants