Cherry-pick #20958 to 7.x: [Filebeat][zeek] Add mappings for x509 fields in kerberos#20975
Merged
marc-gr merged 1 commit intoelastic:7.xfrom Sep 4, 2020
Merged
Cherry-pick #20958 to 7.x: [Filebeat][zeek] Add mappings for x509 fields in kerberos#20975marc-gr merged 1 commit intoelastic:7.xfrom
marc-gr merged 1 commit intoelastic:7.xfrom
Conversation
) * Add mappings for x509 fields in kerberos * Add changelog entry * Do gsub in place (cherry picked from commit de5a419)
Contributor
|
Pinging @elastic/siem (Team:SIEM) |
Contributor
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
|
leehinman
approved these changes
Sep 4, 2020
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
3 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.
Cherry-pick of PR #20958 to 7.x branch. Original message:
What does this PR do?
Adds mappings for the new
x509ecs fields inkebreroszeekmoduleWhy is it important?
To keep our modules up to date with ecs 1.6.0
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.asciidocorCHANGELOG-developer.next.asciidoc.Related issues