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

Add syslog output #9

Open
WilliamBruneau opened this issue Jun 15, 2023 · 3 comments
Open

Add syslog output #9

WilliamBruneau opened this issue Jun 15, 2023 · 3 comments
Labels
enhancement New feature or request

Comments

@WilliamBruneau
Copy link
Member

Some SIEM can only receive logs in syslog messages. To support these SIEM, we need to add a syslog output.

cf RFC 5424.

It may be useful to add 2 variant of syslog output for TCP and UDP.

@WilliamBruneau WilliamBruneau added the enhancement New feature or request label Jun 15, 2023
@MrAnno
Copy link
Contributor

MrAnno commented Nov 23, 2023

Until this is implemented, a workaround can be (and an overkill) using the unixdatagram output to forward raw events to a tool that can process them further to conform to the requirements of different SIEMs.

https://github.com/cea-sec/openwec/blob/main/doc/outputs.md#unix-domain-socket

We do something similar using OpenWEC together with syslog-ng.

@necouchman
Copy link

I'll also add that a nice-to-have would be output to systemd-journald-remote, in the journald format, which has largely supplanted syslog on newer Linux distributions.

@a139786
Copy link

a139786 commented May 9, 2024

I have OpenWEC and rsyslog sharing a box - OpenWEC writing to files rsyslog reads from. That way any issues with the syslog server don't result in loss of logs. HTH.

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

4 participants