-
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
Cis k8s name migration #3113
Cis k8s name migration #3113
Conversation
Maybe a rename is possible instead of this duplication - the package only exists in Additionally I think it's a wrong name for this integration package that we will have to refactor again. |
@eyalkraft why do you think it's wrong? |
I don't want to rename before we update kibana, cloudbeat and the automation (not 100% sure about that automation needs to be updated) to use the new name. As it can cause breaking changes. therefore I duplicate it as a migration phase. |
I don't think it's inherently wrong but it has some implications. |
Co-authored-by: eyalkraft <[email protected]>
this is on point, the rule templates will all be saved (which i think is ok), but we will need to distinguish between policy_templates. which I named as kspm. so this should be added on our hook. |
@eyalkraft, @amitkanfer I've tested it, and we can distinguish between different tiles being installed. This is the test I've taken: format_version: 1.0.0
name: cloud_security_posture
-title: "CIS Kubernetes Benchmark"
+title: "CIS Security Posture"
policy_templates:
- name: kspm
title: CIS Kubernetes Benchmark
description: Check Kubernetes cluster compliance with the Kubernetes CIS benchmark.
multiple: false
inputs:
- type: cloudbeat
title: Enable CIS Kubernetes Benchmark
description: Collecting findings
+ - name: cspm
+ title: CIS Cloud Benchmark
+ description: testing third tile
+ multiple: false
+ inputs:
+ - type: cloudbeat
+ title: Enable CIS Cloud Benchmark
+ description: Collecting findings And I examined it during debug and you can see different inputs and their |
Nice, so I think in this case in order to keep our kibana plugin free from strings representing the names of our benchmarks we would want to add a field for our rule templates to indicate which policy template(s?) they belong to. |
…ations into feature/labels-cloud-ephemeral-components * 'feature/labels-cloud-ephemeral-components' of github.com:v1v/integrations: (23 commits) use branch standardise labels/tags Update .ci/Jenkinsfile [ci][terraform][aws] tags with metadata Bump github.com/elastic/elastic-package from 0.46.0 to 0.47.0 (elastic#3182) Spring boot package [Memory - data stream] (elastic#2979) [cisco_ise] Add Cisco ISE package (elastic#2855) [apache_spark][executor] Add Apache Spark package with Executor data stream (elastic#2943) [apache_spark][driver] Add Apache Spark package with Driver data stream (elastic#2945) cisco_duo: simplify grok expression for handling ports (elastic#3170) cisco_duo: fix handling of IP addresses with port numbers (elastic#3117) [sophos] Various improvements and log samples from 18.5 (elastic#3127) [cisco_asa] fix visualizations (elastic#3146) [apache_spark][application] Add Apache Spark package with Application data stream (elastic#2941) Fix pagination bug that skipped events when more than one page is present. (elastic#3140) Cis k8s name migration (elastic#3113) remove exported fields; these will be added to Kibana docs instead (elastic#3093) Exclude ecosystem as owner of subdirectories of packages (elastic#3132) [awsfargate] bump package version (elastic#3130) add first csp rule template (elastic#3081) ...
{ | ||
"attributes": { | ||
"description": "", | ||
"title": "logs-cloud_security_posture.findings-*" |
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.
"title": "logs-cloud_security_posture.findings-*" | |
"title": "logs-cloud_security_posture.findings*" |
@kfirpeled I know it's already merged, but since the current findings index is logs-cloud_security_posture.findings_latest-default
this data view didn't catch it 😢
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.
@oren-zohar This is on purpose, we'll move the findings_latest
index in a different PR
What does this PR do?
This pr is part of a larger change to rename the current integration of
cis_kubernetes_benchmark
tocloud_security_posture
as it will contain more benchmarks in the future and should have a proper naming.A followup PR will be to remove the
cis_kubernetes_benchmark
package once all code base in the different repos will be aligned to the new namingChecklist
changelog.yml
file.Author's Checklist
How to test this PR locally
Related issues
Screenshots