-
Notifications
You must be signed in to change notification settings - Fork 419
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
Add Ingest Pipeline script to map IANA Protocol Numbers #2470
Conversation
787dc04
to
76816e0
Compare
/test |
packages/gcp/data_stream/vpcflow/_dev/test/pipeline/test-vpcflow.log-expected.json
Outdated
Show resolved
Hide resolved
packages/aws/data_stream/vpcflow/elasticsearch/ingest_pipeline/default.yml
Outdated
Show resolved
Hide resolved
I think a few more IANA numbers should be added to the list. This issue mentions several other values that show up frequently in the user's network (like SCTP). |
I'll add them. |
Updated script with additional IANA numbers. |
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.
LGTM.
/test
/test |
c736d27
to
3dab1b7
Compare
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
3dab1b7
to
1b10b82
Compare
* Add script to CheckPoint * Add script to AWS VPC Flow * Add script to Crowdstrike * Add script to Fortinet * Add script to GCP * Add script to Juniper SRX
What does this PR do?
Adds an Ingest Pipeline script to multiple network based integrations to map IANA Protocol Numbers (1,6,17..) to their associated name (icmp, tcp, udp...)
Checklist
changelog.yml
file.Author's Checklist
How to test this PR locally
Related issues
Screenshots