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

[Feature request] Add prefix to enriched fields #244

Closed
ari-wein opened this issue Jan 10, 2025 · 6 comments · Fixed by #245
Closed

[Feature request] Add prefix to enriched fields #244

ari-wein opened this issue Jan 10, 2025 · 6 comments · Fixed by #245

Comments

@ari-wein
Copy link

Can a feature be added where all enrichment keys that are added by laurel are prepended by a string that the user sets in the config?
For example, when the uid is resolved and added as UID, you would have the option as adding it as L_UID.
The reason is that the SIEM that im using doesn't differentiate between case, so uid and UID are the same, and one gets dropped.
This should apply to all fields that are added by laurel to the log.

@ari-wein ari-wein changed the title [Feature request] Add prefix to enhanced fields [Feature request] Add prefix to enriched fields Jan 10, 2025
@hillu
Copy link
Collaborator

hillu commented Jan 13, 2025

Interesting. What kind of SIEM are you using that does not properly understand JSON objects?

This one is going to be a bit messy because this means that laurel should also rewrite enriched fields (SYSCALL, ARCH, *UID, *GID) that have been created by auditd.

@ari-wein
Copy link
Author

The SIEM is Wazuh.
If you take a look at my fork, you can see the job that AI did. I cant code in rust, so I don't actually know what it did, but if it provides any help at all, feel free to steal it. It got it working to add the prefix, but labels are not propagating down the process tree correctly.

@hillu
Copy link
Collaborator

hillu commented Jan 13, 2025

@ari-wein I don't see a LAUREL fork under your account.

@ari-wein
Copy link
Author

hillu added a commit to hillu/laurel that referenced this issue Jan 14, 2025
This seems useful for mis-designed log analysis software that treats
JSNO object keys as case-insensitive.

Close threathunters-io#244
@hillu
Copy link
Collaborator

hillu commented Jan 14, 2025

@ari-wein I decided that dealing with already-enriched fields coming from auditd is not worth the bother. Could you look if the changes made for PR #245 do what you want?

@ari-wein
Copy link
Author

Yup. Tested that build, and it works great.
Thanks SO much for implementing!

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

Successfully merging a pull request may close this issue.

2 participants