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: Laurel for auditd #14461

Open
zbalkan opened this issue Aug 1, 2022 · 1 comment
Open

Feature request: Laurel for auditd #14461

zbalkan opened this issue Aug 1, 2022 · 1 comment

Comments

@zbalkan
Copy link
Contributor

zbalkan commented Aug 1, 2022

"LAUREL is an event post-processing plugin for auditd(8) to improve its usability in modern security monitoring setups", according to the project README. It has many capabilities for correlating the auditd logs in a performant way. Instead of using auditd_decoders.xml + logstash enrichment to provide similar capabilities would probably be not performant enough and also may not reach the same results.

In my email, I proposed if LAUREL + Wazuh scenario has ever been tried and requested for comments.

I was responded that that setup might work and I'd better create an issue for a feature request. However, I do not know how LAUREL can be integrated. Would that be included on the agent, which makes sense on performance level but it is against the Wazuh architecture. Or, its internal processing can be considered as an extension to auditd decoding. Of course, it's just my assumptions. YMMW.

@zbalkan
Copy link
Contributor Author

zbalkan commented Aug 3, 2022

In current scenario, using Laurel requires reading /var/log/laurel/audit.log using json decoder. But there is no rule that matches laurel generated auditd logs. I started implementing them but failed to translate auditd rules to laurel rules. So I had to rollback. I wish wazuh can provide auditd logs as much information as Laurel can do.

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

No branches or pull requests

2 participants