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 #14035 to 7.4: Fix Cisco ASA and FTD parsing of unexpected domain names #14040

Merged
merged 2 commits into from
Oct 15, 2019

Conversation

adriansr
Copy link
Contributor

Cherry-pick of PR #14035 to 7.4 branch. Original message:

This patch makes the Cisco ASA and FTD ingest pipeline handle the case
where a domain name is found for a field where an IP is expected
according to the documentation.

To do so it follows ECS guidelines, setting .address to be the raw value
and .ip or .domain from it, depending if it's a valid IP address or not.

Fixes #14034

This patch makes the Cisco ASA and FTD ingest pipeline handle the case
where a domain name is found for a field where an IP is expected
according to the documentation.

To do so it follows ECS guidelines, setting .address to be the raw value
and .ip or .domain from it, depending if it's a valid IP address or not.

Fixes elastic#14034

(cherry picked from commit a678bc9)
@adriansr adriansr requested a review from a team as a code owner October 14, 2019 17:27
@adriansr
Copy link
Contributor Author

jenkins, test this

@adriansr adriansr merged commit 9bc4dcd into elastic:7.4 Oct 15, 2019
leweafan pushed a commit to leweafan/beats that referenced this pull request Apr 28, 2023
…expected domain names (elastic#14040)

This patch makes the Cisco ASA and FTD ingest pipeline handle the case
where a domain name is found for a field where an IP is expected
according to the documentation.

To do so it follows ECS guidelines, setting .address to be the raw value
and .ip or .domain from it, depending if it's a valid IP address or not.

Fixes elastic#14034

(cherry picked from commit 9f20d7c)
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.

2 participants