-
Notifications
You must be signed in to change notification settings - Fork 444
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
[Cisco ASA] Add support for SIP events #1865
Conversation
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
🤖 GitHub commentsTo re-run your PR in the CI, just comment with:
|
/test |
1 similar comment
/test |
@efd6 just a heads up that we have a set of proposed SIP fields in ECS, which are worth checking out incase any of the fields are relevant to these Cisco events. https://github.com/elastic/ecs/blob/master/rfcs/text/0011-sip-fields.md @marc-gr implemented SIP support in Packetbeat and may have some input. |
It is probably worth mirroring the addresses and port into sip.{from,to}. It doesn't look like the remainder map well to that scheme, but I'll wait for further input. |
packages/cisco_asa/data_stream/log/elasticsearch/ingest_pipeline/default.yml
Outdated
Show resolved
Hide resolved
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
description: "607001" | ||
field: "_temp_.cisco.connection_type" | ||
patterns: | ||
- "%{PROTOCOLS:network.transport}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
RTP and RTCP are not transport protocols, they're layer 7 so would belong in network.protocol
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks. Fixed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd combine those into a single grok processor. No reason to break it up.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks. Is this better?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Small comment and LGTM :)
packages/cisco_asa/changelog.yml
Outdated
@@ -19,3 +19,6 @@ | |||
- description: Split Cisco ASA into its own package | |||
type: enhancement | |||
link: https://github.com/elastic/integrations/pull/1583 | |||
- description: Add support for Cisco ASA SIP events |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you add your own changelog entry and bump the version in changelog.yml and the manifest? I think its better that we differentiate between them, rather than trying to put them under the same version
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed
What does this PR do?
Checklist
changelog.yml
file.manifest.yml
file to point to the latest Elastic stack release (e.g.^7.13.0
).Author's Checklist
How to test this PR locally
Related issues
Screenshots
N/A