-
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] Cisco ASA pipeline is not parsing source.port
and destination.port
for message ID: 302022 correctly
#24405
Comments
source.port
and destination.port
for message ID: 302022 correctly
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
i created a PR with your fix and it looks good. do you know what the |
From Cisco's website (https://www.cisco.com/c/en/us/td/docs/security/asa/syslog/b_syslog/syslog-messages-302003-to-342008.html)
Looks liked NAT information? should this parser update to use the |
I am not sure, but they are the same in our case, e.g. |
Interesting. I guess we'll just ignore them for now until someone has a better answer. I'll take the PR out of draft. |
As we work ur issue, do u have any input on this #23764? It seems to point out that the source and destination should be switched at times |
* Fix cisco asa parser for message 302022 - fix parser to include mapped address and ports - add NAT addresses to related.ip Closes elastic#24695 Closes elastic#24405 (cherry picked from commit c685997)
* Fix cisco asa parser for message 302022 - fix parser to include mapped address and ports - add NAT addresses to related.ip Closes elastic#24695 Closes elastic#24405 (cherry picked from commit c685997)
…lastic#24712) * Fix cisco asa parser for message 302022 - fix parser to include mapped address and ports - add NAT addresses to related.ip Closes elastic#24695 Closes elastic#24405 (cherry picked from commit 6c9386d)
For confirmed bugs, please report:
filebeat-7.11.0-cisco-asa-asa-ftd-pipeline
pipeline).400
status error:failed to parse field [destination.port] of type [long] in document with id 'BkAHBngB0-vqe0TpMgeC'. Preview of field's value: '7503 (172.20.64.180/7503)'","caused_by":{"type":"illegal_argument_exception","reason":"For input string: \"7503 (172.20.64.180/7503)\"
Current dissect pattern:
Built %{} stub %{network.transport} connection for %{_temp_.cisco.source_interface}:%{source.address}/%{source.port} to %{_temp_.cisco.destination_interface}:%{destination.address}/%{destination.port}
Sample message:
Built director stub TCP connection for fw1111:10.10.10.10/38540 (8.8.8.5/38540) to net:192.168.2.2/10051 (8.8.8.8/10051)
Dissect pattern should be changed to, e.g.:
Built %{} stub %{network.transport} connection for %{_temp_.cisco.source_interface}:%{source.address}/%{source.port} %{} to %{_temp_.cisco.destination_interface}:%{destination.address}/%{destination.port} %{}
The text was updated successfully, but these errors were encountered: