Add ingress/egress and configuration categorization#80
Merged
andrewstucki merged 5 commits intoelastic:masterfrom Dec 8, 2020
Merged
Add ingress/egress and configuration categorization#80andrewstucki merged 5 commits intoelastic:masterfrom
andrewstucki merged 5 commits intoelastic:masterfrom
Conversation
added 2 commits
December 8, 2020 11:42
This was referenced Dec 8, 2020
renini
pushed a commit
to renini/go-libaudit
that referenced
this pull request
Jun 26, 2024
* Add ingress/egress/internal and configuration categorization * Add changelog entry * Fix up ingress/egress * Update changelog * remove internal
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This adds the new
configurationcategory to a few different auditd events. UnfortunatelyAUDIT_CONFIG_CHANGEand a few others already hadprocessas the category, so I just added the additional category so we don't potentially break anything in beats.The network direction changes are breaking, but that's what's needed for the ECS update.
Related: elastic/beats#21674, elastic/ecs#945