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

Option to specify log facility in config #21

Open
dw-code opened this issue Jan 25, 2024 · 0 comments
Open

Option to specify log facility in config #21

dw-code opened this issue Jan 25, 2024 · 0 comments

Comments

@dw-code
Copy link

dw-code commented Jan 25, 2024

Right now, it looks like the log facility is set in estreamer/adapters/cef.py. It would be nice to have this as an option in the configuration to make it easily modifiable.

# Syslog settings
SYSLOG_FACILITY_USER   = 1
SYSLOG_PRIORITY_NOTICE = 5

# Calc and save the syslog numeric (do not change, gets calculated)
SYSLOG_NUMERIC = (SYSLOG_FACILITY_USER << 3  | SYSLOG_PRIORITY_NOTICE)

One use case is that in Microsoft Sentinel, the log level is used in Data Collection Rules to specify how logs are handled. By default, these come in under log facility user--which is the same as a lot of other log sources. Without having to spin up another collector, you can split up the parsing by specifying which log levels are applied to a data collection rule.

For example, you can have 1 Azure Monitor Agent collector that takes in Syslog on all facilities, but use a normally unused facility to split off the Common Event Format logs. For example, you may have a data collection rule that looks at local6 which is then tied to Sentinel's CEF ingest which will make them searchable. You may want to carve out CEF into their own facility so they are only captured once. If you have a data collection rule that looks at all facilities, and another that looks for the same information but passes it through the CEF ingest, CEF messages will be in duplicate tables (CommonSecurityLog and Syslog). 

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

No branches or pull requests

1 participant