-
Notifications
You must be signed in to change notification settings - Fork 458
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
Update Deployment and Devices integrations to ECS 8.16.0 (part 1) #12119
base: main
Are you sure you want to change the base?
Update Deployment and Devices integrations to ECS 8.16.0 (part 1) #12119
Conversation
ECS version in build manifest changed from [email protected] to [email protected]. The set ecs.version processor in pipelines was changed 8.16.0. Previously the pipeline was setting version 8.11.0. [git-generate] go run github.com/andrewkroh/go-examples/ecs-update@latest -ecs-version=8.16.0 [email protected] -pr=999999 packages/arista_ngfw
ECS version in build manifest changed from [email protected] to [email protected]. The set ecs.version processor in pipelines was changed 8.16.0. Previously the pipeline was setting version 8.11.0. The ecs.version in sample_event.json files was changed to 8.16.0. Previously sample_event.json files contained 8.11.0. [git-generate] go run github.com/andrewkroh/go-examples/ecs-update@latest -ecs-version=8.16.0 [email protected] -pr=999999 packages/cef
ECS version in build manifest changed from [email protected] to [email protected]. The set ecs.version processor in pipelines was changed 8.16.0. Previously the pipeline was setting version 8.11.0. The ecs.version in sample_event.json files was changed to 8.16.0. Previously sample_event.json files contained 8.11.0. [git-generate] go run github.com/andrewkroh/go-examples/ecs-update@latest -ecs-version=8.16.0 [email protected] -pr=999999 packages/checkpoint
ECS version in build manifest changed from [email protected] to [email protected]. The set ecs.version processor in pipelines was changed 8.16.0. Previously the pipeline was setting version 8.11.0. The ecs.version in sample_event.json files was changed to 8.16.0. Previously sample_event.json files contained 8.11.0. [git-generate] go run github.com/andrewkroh/go-examples/ecs-update@latest -ecs-version=8.16.0 [email protected] -pr=999999 packages/cisco_aironet
ECS version in build manifest changed from [email protected] to [email protected]. The set ecs.version processor in pipelines was changed 8.16.0. Previously the pipeline was setting version 8.11.0. The ecs.version in sample_event.json files was changed to 8.16.0. Previously sample_event.json files contained 8.11.0. [git-generate] go run github.com/andrewkroh/go-examples/ecs-update@latest -ecs-version=8.16.0 [email protected] -pr=999999 packages/cisco_asa
ECS version in build manifest changed from [email protected] to [email protected]. The set ecs.version processor in pipelines was changed 8.16.0. Previously the pipeline was setting version 8.11.0. The ecs.version in sample_event.json files was changed to 8.16.0. Previously sample_event.json files contained 8.11.0. [git-generate] go run github.com/andrewkroh/go-examples/ecs-update@latest -ecs-version=8.16.0 [email protected] -pr=999999 packages/cisco_ftd
ECS version in build manifest changed from [email protected] to [email protected]. The set ecs.version processor in pipelines was changed 8.16.0. Previously the pipeline was setting version 8.11.0. The ecs.version in sample_event.json files was changed to 8.16.0. Previously sample_event.json files contained 8.11.0. [git-generate] go run github.com/andrewkroh/go-examples/ecs-update@latest -ecs-version=8.16.0 [email protected] -pr=999999 packages/cisco_ios
ECS version in build manifest changed from [email protected] to [email protected]. The set ecs.version processor in pipelines was changed 8.16.0. Previously the pipeline was setting version 8.11.0. The ecs.version in sample_event.json files was changed to 8.16.0. Previously sample_event.json files contained 8.11.0. [git-generate] go run github.com/andrewkroh/go-examples/ecs-update@latest -ecs-version=8.16.0 [email protected] -pr=999999 packages/cisco_ise
ECS version in build manifest changed from [email protected] to [email protected]. The set ecs.version processor in pipelines was changed 8.16.0. Previously the pipeline was setting version 8.11.0. The ecs.version in sample_event.json files was changed to 8.16.0. Previously sample_event.json files contained 8.11.0. [git-generate] go run github.com/andrewkroh/go-examples/ecs-update@latest -ecs-version=8.16.0 [email protected] -pr=999999 packages/cisco_nexus
ECS version in build manifest changed from [email protected] to [email protected]. The set ecs.version processor in pipelines was changed 8.16.0. Previously the pipeline was setting version 8.11.0. The ecs.version in sample_event.json files was changed to 8.16.0. Previously sample_event.json files contained 8.11.0. [git-generate] go run github.com/andrewkroh/go-examples/ecs-update@latest -ecs-version=8.16.0 [email protected] -pr=999999 packages/cisco_secure_email_gateway
ECS version in build manifest changed from [email protected] to [email protected]. The set ecs.version processor in pipelines was changed 8.16.0. Previously the pipeline was setting version 8.11.0. The ecs.version in sample_event.json files was changed to 8.16.0. Previously sample_event.json files contained 8.11.0. [git-generate] go run github.com/andrewkroh/go-examples/ecs-update@latest -ecs-version=8.16.0 [email protected] -pr=999999 packages/citrix_waf
🚀 Benchmarks reportTo see the full report comment with |
Quality Gate passedIssues Measures |
💚 Build Succeeded
|
Pinging @elastic/sec-deployment-and-devices (Team:Security-Deployment and Devices) |
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.
Looks like there's a hyperlink that needs some attention. I will approve once it's fixed.
@@ -793,5 +793,5 @@ An example event for `firewall` looks as following: | |||
| user_agent.name | Name of the user agent. | keyword | | |||
| user_agent.original | Unparsed user_agent string. | keyword | | |||
| user_agent.original.text | Multi-field of `user_agent.original`. | match_only_text | | |||
| vulnerability.id | The identification (ID) is the number portion of a vulnerability entry. It includes a unique identification number for the vulnerability. For example (https://cve.mitre.org/about/faqs.html#what_is_cve_id)[Common Vulnerabilities and Exposure CVE ID] | keyword | | |||
| vulnerability.id | The identification (ID) is the number portion of a vulnerability entry. It includes a unique identification number for the vulnerability. For example (https://cve.mitre.org/about/faqs.html#what_is_cve_id[Common Vulnerabilities and Exposure CVE ID]) | keyword | |
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.
This doesn't look correct in the rich diff.
Shouldn't it be something like [Common Vulnerabilities and Exposure CVE ID](https://cve.mitre.org/about/faqs.html#what_is_cve_id)
?
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.
Oh good catch.
Let me go check ECS, I didn't hand write that, that's pulled directly from the ECS definition (but this could also be an issue with how elastic-package is rendering the markdown).
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.
Here's the related PR: elastic/ecs#2328
The links render correctly for the ECS docs, but the syntax used for the link is not valid markdown. The integrations doc site seems to use the readme markdown more or less directly, so that will have problems, too.
For comparison, the threat fields do not use a special markup, but rather use the link directly. The ECS docs and the integration readme page in Kibana (Suricata is an example), and the integrations doc site all enrich the URL into a link. Seems like we don't need any special markup here (unless you want to hide the URL behind friendly text, but that doesn't work if it doesn't render correctly).
Unfortunately, this would need to be fixed in ECS, first. Manually fixing it here won't help, since any re-render of the readme from here will just bring the issue back. It just so happens there's an ECS meeting today. I'll bring this issue up there and see where we go from here.
Proposed commit message
Updates the following integrations to ECS 8.16.0:
Checklist
changelog.yml
file.[ ] I have verified that any added dashboard complies with Kibana's Dashboard good practicesRelated issues