Skip to content
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

[Cloud Security] Update manifest format_version to 3.0.0 for cloud_security_posture package #8162

Merged
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions packages/cloud_security_posture/changelog.yml
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,11 @@
# 1.4.x - 8.9.x
# 1.3.x - 8.8.x
# 1.2.x - 8.7.x
- version: "1.6.2"
changes:
- description: Change the format_version in the package manifest to 3.0.0. Remove dotted YAML keys from package manifest. Add owner.type elastic to package manifest. Add missing object_type fields. Add security capability.
type: enhancement
link: https://github.com/elastic/integrations/pull/8162
- version: "1.6.1"
changes:
- description: Update ARM link for Azure
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -11,4 +11,5 @@
type: keyword
- name: raw
type: object
object_type: keyword
enabled: false
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,9 @@
type: keyword
- name: evidence
type: object
object_type: keyword
enabled: false
- name: expected
type: object
object_type: keyword
enabled: false
Original file line number Diff line number Diff line change
Expand Up @@ -12,8 +12,8 @@
- name: machine.Image
type: keyword
- name: Tags
type: object
type: flattened
- name: availability_zone
type: keyword
- name: Security.security_groups
type: object
type: nested
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In your tests, have you verified that these fields work as expected with the new type?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I didn't find anything weird about them. They show up in the document, and flyout Table/JSON view works, but searching doesn't work with these fields as it doesn't work without the change either, I guess because they are not being indexed

13 changes: 9 additions & 4 deletions packages/cloud_security_posture/manifest.yml
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
format_version: 2.3.0
format_version: 3.0.0
name: cloud_security_posture
title: "Security Posture Management"
version: "1.6.1"
version: "1.6.2"
source:
license: "Elastic-2.0"
description: "Identify & remediate configuration risks in your Cloud infrastructure"
Expand All @@ -11,8 +11,12 @@ categories:
- kubernetes
- security
conditions:
kibana.version: "^8.11.0"
elastic.subscription: basic
kibana:
version: "^8.11.0"
elastic:
subscription: basic
capabilities:
- security
screenshots:
- src: /img/dashboard.png
title: Dashboard page
Expand Down Expand Up @@ -175,3 +179,4 @@ policy_templates:
default: https://console.aws.amazon.com/cloudformation/home#/stacks/quickcreate?templateURL=https://elastic-cspm-cft.s3.eu-central-1.amazonaws.com/cloudformation-cnvm-8.11.0-2023-09-10-08-35-18.yml&stackName=Elastic-Vulnerability-Management&param_EnrollmentToken=FLEET_ENROLLMENT_TOKEN&param_FleetUrl=FLEET_URL&param_ElasticAgentVersion=KIBANA_VERSION&param_ElasticArtifactServer=https://artifacts.elastic.co/downloads/beats/elastic-agent
owner:
github: elastic/cloud-security-posture
type: elastic