-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[Filebeat][auditd] Fix event types and categories to comply with ECS #20652
Conversation
💔 Tests FailedExpand to view the summary
Build stats
Test stats 🧪
Test errorsExpand to view the tests failures
Steps errorsExpand to view the steps failures
Log outputExpand to view the last 100 lines of log output
|
Pinging @elastic/siem (Team:SIEM) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
9aaf63f
to
84ec230
Compare
84ec230
to
8bca15f
Compare
…lastic#20652) * Fix event types and categories to comply with ECS * Add CHANGELOG entry * Regenerate test files (cherry picked from commit 8d77c1c)
…lastic#20652) * Fix event types and categories to comply with ECS * Add CHANGELOG entry * Regenerate test files (cherry picked from commit 8d77c1c)
…lastic#20652) * Fix event types and categories to comply with ECS * Add CHANGELOG entry * Regenerate test files
…lastic#20652) (elastic#20794) * Fix event types and categories to comply with ECS * Add CHANGELOG entry * Regenerate test files (cherry picked from commit 2eef257)
What does this PR do?
Sets correct
event.category
andevent.type
fields where incorrectevent.type
fields were set.Why is it important?
The auditd module was using several
event.type
values that are not in ECS.https://www.elastic.co/guide/en/ecs/current/ecs-allowed-values-event-type.html
Checklist
- [ ] My code follows the style guidelines of this project- [ ] I have commented my code, particularly in hard-to-understand areas- [ ] I have made corresponding changes to the documentation- [ ] I have made corresponding change to the default configuration filesCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Related issues
Closes #20411