Cherry-pick #23072 to 7.x: [Filebeat] Add fortinet/firewall network direction override based on interface#23085
Merged
andrewstucki merged 4 commits intoelastic:7.xfrom Dec 11, 2020
Conversation
…interface (elastic#23072) * [Filebeat] Add fortinet/firewall network direction override based on interface * Add changelog entry * Don't override categorization if no interface name is set (cherry picked from commit 5a03647)
Contributor
|
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
leehinman
approved these changes
Dec 10, 2020
Contributor
leehinman
left a comment
There was a problem hiding this comment.
couple extra lines in CHANGELOG
Contributor
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
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 #23072 to 7.x branch. Original message:
What does this PR do?
This is pretty similar to the other PRs that allow override based off zone, such as #23066. However, since fortinet doesn't ship zone information, this uses the interface instead.
Additionally, I found some values in the utm source that were setting network.direction to "outgoing"/"incoming", so I normalized those.
Checklist
CHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Related issues