-
Notifications
You must be signed in to change notification settings - Fork 474
Add "Security Solution" tags to security-related CDR integrations #11716
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
Conversation
🚀 Benchmarks reportPackage
|
Data stream | Previous EPS | New EPS | Diff (%) | Result |
---|---|---|---|---|
cloud_configuration_finding |
5952.38 | 3533.57 | -2418.81 (-40.64%) | 💔 |
To see the full report comment with /test benchmark fullreport
|
💚 Build Succeeded
cc @albertoblaz |
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 good to me!
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 👍🏼
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
Package prisma_cloud - 1.4.0 containing this change is available at https://epr.elastic.co/package/prisma_cloud/1.4.0/ |
Package wiz - 2.3.0 containing this change is available at https://epr.elastic.co/package/wiz/2.3.0/ |
…astic#11716) * Add tags.yaml for prisma_cloud * Add tags.yaml for wiz
…astic#11716) * Add tags.yaml for prisma_cloud * Add tags.yaml for wiz
Description
Adds tags.yml to all security integrations so that dashboards and saved searches are tagged with "Security Solution", and will be shown in the Security Solution UI.
Related integrations with "Security solution" tag:
packages/aws
and they useasset_ids
Checklist
changelog.yml
file.Testing
Follow these guidelines to install
elastic-package
, build the new packages and integrates them with your local ES & KibanaRelated issues
Screenshots
I've got no Wiz-related data locally, but I do have it for Prisma Cloud and their tags config is the same:
Prisma Cloud
Warnings
Running
elastic-package lint
returned these pre-existent warnings for the modified packages. Is this something we should worry about? The packages were eventually build successfully though:wiz
prisma_cloud