-
Notifications
You must be signed in to change notification settings - Fork 489
Add vulnerability management integration #5266
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
Hi @amirbenun, Here's the icon for vulnerability management in case you want to include it in your PR SVG <svg xmlns="http://www.w3.org/2000/svg" width="32" height="32" fill="none" viewBox="0 0 32 32">
<path fill="#00BFB3" fill-rule="evenodd" d="M11.05 2.086 6.808 6.329 16 15.52l9.192-9.192-4.242-4.243L16 7.036l-4.95-4.95Z" clip-rule="evenodd"/>
<path fill="#FA744E" d="M4.686 19.764a8 8 0 0 1 0-11.314L16 19.764v11.313L4.686 19.763Z"/>
<path fill="#343741" d="M27.314 8.45a8 8 0 0 1 0 11.314L16 31.077V19.763L27.314 8.45Z"/>
</svg> File (to add to Suggested changes to add to manifest.yaml icons:
- src: /img/logo_vuln_mgnt.svg
title: Vulnerability Management logo
size: 32x32
type: image/svg+xml |
...cloud_security_posture/data_stream/vulnerabilities/elasticsearch/ingest_pipeline/default.yml
Outdated
Show resolved
Hide resolved
packages/cloud_security_posture/data_stream/vulnerabilities/fields/ecs.yml
Show resolved
Hide resolved
packages/cloud_security_posture/data_stream/vulnerabilities/manifest.yml
Outdated
Show resolved
Hide resolved
🌐 Coverage report
|
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
processors: | ||
- set: | ||
field: ecs.version | ||
value: '8.6.0' |
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.
shouldn't it be the same version as the ELK 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.
Honestly, I copied it from the findings data-stream. @kfirpeled what is the reason it points to 8.6?
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.
Because that is the ECS version we support, it is defined here: https://github.com/elastic/integrations/blob/main/packages/cloud_security_posture/_dev/build/build.yml
packages/cloud_security_posture/data_stream/vulnerabilities/fields/cloudbeat.yml
Outdated
Show resolved
Hide resolved
packages/cloud_security_posture/data_stream/vulnerabilities/manifest.yml
Outdated
Show resolved
Hide resolved
bb11a46
to
45d4158
Compare
type: date | ||
description: The commit time of the Cloudbeat. | ||
default_field: false | ||
- name: kubernetes.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.
removed from the wrong place?
title: Vulnerability Management | ||
description: Scan for cloud resources vulnerabilities | ||
categories: | ||
- Vulnerability Management |
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.
- Vulnerability Management | |
- vulnerability_management |
It looks like Credential Management
is credential_management
here (for reference categories.yml)
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 think the CI didn't like that in any case
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.
Should work based on the latest version of the package-registry
Hey @mrodm the CI fails on the new
|
Checking the A new release v0.75.0 has been created, once this version is updated in the integrations repository that category could be added in the packages. |
Package cloud_security_posture - 1.3.0-preview4 containing this change is available at https://epr.elastic.co/search?package=cloud_security_posture |
Package cloud_security_posture - 1.3.0-preview5 containing this change is available at https://epr.elastic.co/search?package=cloud_security_posture |
Package cloud_security_posture - 1.3.0-preview6 containing this change is available at https://epr.elastic.co/search?package=cloud_security_posture |
Package cloud_security_posture - 1.3.0-preview7 containing this change is available at https://epr.elastic.co/search?package=cloud_security_posture |
Package cloud_security_posture - 1.3.0-preview8 containing this change is available at https://epr.elastic.co/search?package=cloud_security_posture |
Package cloud_security_posture - 1.3.0-preview9 containing this change is available at https://epr.elastic.co/search?package=cloud_security_posture |
Package cloud_security_posture - 1.3.0-preview10 containing this change is available at https://epr.elastic.co/search?package=cloud_security_posture |
Package cloud_security_posture - 1.3.0-preview91 containing this change is available at https://epr.elastic.co/search?package=cloud_security_posture |
Package cloud_security_posture - 1.3.0 containing this change is available at https://epr.elastic.co/search?package=cloud_security_posture |
Package cloud_security_posture - 1.3.1 containing this change is available at https://epr.elastic.co/search?package=cloud_security_posture |
What does this PR do?
Add a new cloud security policy template for vulnerability management that will form as a new integration
Resolves #5328
Checklist
changelog.yml
file.Author's Checklist
How to test this PR locally
Related issues
Screenshots