Skip to content
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

Cherry-pick #18376 to 7.7: Fix Cisco ASA/FTD msgs that use a host name as NAT address #18546

Merged
merged 2 commits into from
May 15, 2020

Conversation

adriansr
Copy link
Contributor

@adriansr adriansr commented May 14, 2020

Cherry-pick of PR #18376 to 7.7 branch. Original message:

What does this PR do?

Fixes the ingestion of Cisco ASA/FTD events that have a hostname as a NAT target, where an IP was expected.

Why is it important?

Because some NAT setups were causing ingestion failures.

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 files
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Related issues

…8376)

Sometimes the mapped source/destination IP field of an event is a hostname
instead of an IP address. This caused ingestion of the event to fail.

This patch makes the asa-ftd-pipeline to only populate those fields when
a valid IP address is found.

In the future we may want to revisit this if .nat.domain or
.nat.address fields become available.

(cherry picked from commit b24ed97)
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label May 14, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/siem (Team:SIEM)

@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label May 14, 2020
@botelastic
Copy link

botelastic bot commented May 14, 2020

This issue doesn't have a Team:<team> label.

@adriansr adriansr merged commit 5112d7d into elastic:7.7 May 15, 2020
leweafan pushed a commit to leweafan/beats that referenced this pull request Apr 28, 2023
…8376) (elastic#18546)

Sometimes the mapped source/destination IP field of an event is a hostname
instead of an IP address. This caused ingestion of the event to fail.

This patch makes the asa-ftd-pipeline to only populate those fields when
a valid IP address is found.

In the future we may want to revisit this if .nat.domain or
.nat.address fields become available.

(cherry picked from commit c4ccf2a)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants