Skip to content

add community ID to more (all) Zeek logs types #444

Closed

Description

@mmguero

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
  • ???

Activity

  1. added
    enhancementNew feature or request
    externalDepends on a bug or feature external to this project
    zeekRelating to Malcolm's use of Zeek
    on Mar 14, 2024
  2. added this to the z.staging milestone on Mar 14, 2024
  3. moved this to Todo (investigate) in Malcolmon Mar 14, 2024
  4. modified the milestone: z.staging on Aug 20, 2024
  5. removed this from the z.staging milestone on Oct 1, 2024
  6. mmguero commented on Nov 4, 2024

    @mmguero
    CollaboratorAuthor

    Kamino closed and cloned this issue to cisagov/Malcolm

  7. moved this from Todo (investigate) to Done in Malcolmon Nov 4, 2024
  8. moved this from Done to Migrated in Malcolmon Nov 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestexternalDepends on a bug or feature external to this projectzeekRelating to Malcolm's use of Zeek

    Type

    No type

    Projects

    • Status
      Migrated

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions