Closed
Labels
enhancementNew feature or requestNew feature or requestexternalDepends on a bug or feature external to this projectDepends on a bug or feature external to this projectlogstashRelating to Malcolm's use of LogstashRelating to Malcolm's use of LogstashzeekRelating to Malcolm's use of ZeekRelating to Malcolm's use of Zeek
Milestone
Description
@mmguero cloned issue idaholab/Malcolm#444 on 2024-03-14:
It may be useful in some cases to have community ID as part of more zeek logs than conn.log. This would be a configurable option.
However, (at least as of 2020) there isn't a generalized mechanism to add a field to ALL logs. See corelight/zeek-community-id#3.
This gives us a few options, if we wanted to do this:
hook EVERY log type (sort of like this project) and add them manually
calculate community ID in logstash and add it during enrichment instead
???
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or requestexternalDepends on a bug or feature external to this projectDepends on a bug or feature external to this projectlogstashRelating to Malcolm's use of LogstashRelating to Malcolm's use of LogstashzeekRelating to Malcolm's use of ZeekRelating to Malcolm's use of Zeek
Type
Fields
No fields configured for issues without a type.
Projects
- StatusShow more project fieldsReleased
Activity
Infer Zeek transport by log type for Community ID enrichment (cisagov…
Infer Zeek transport by log type for Community ID enrichment (#400)
Fix Community ID transport lookup reading a renamed field (#400)
Fix hardcoded Zeek transports for MQTT and DTLS (#400)
Infer Zeek transport by log type for Community ID enrichment (cisagov…
Infer Zeek transport by log type for Community ID enrichment (cisagov…