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 Posture] Fix kubernetes dashboard links leading to findings page with not cspm filter #195213

Closed
JordanSh opened this issue Oct 7, 2024 · 2 comments · Fixed by #195241
Closed
Assignees
Labels
8.16 candidate Team:Cloud Security Cloud Security team related

Comments

@JordanSh
Copy link
Contributor

JordanSh commented Oct 7, 2024

Summary

After CSPM was introduced, we identified findings by adding a new posture_type field. In order to keep support for older findings without this field, we assumed all findings without it are of type KSPM (since this field was only added when CSPM was first introduced)

We relied on the logic to create links from the dashboard to the findings page. Links from the kubernetes dashboard lead to findings page with a filter for posture type: not cspm. this aimed to find kspm findings before the introduction of posture_type.

In order to fix this, we need to adjust the filters to look for posture type: kspm

@JordanSh JordanSh added the Team:Cloud Security Cloud Security team related label Oct 7, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-cloud-security-posture (Team:Cloud Security)

@JordanSh JordanSh self-assigned this Oct 7, 2024
@acorretti acorretti added bug Fixes for quality problems that affect the customer experience and removed bug Fixes for quality problems that affect the customer experience labels Oct 7, 2024
@orouz
Copy link
Contributor

orouz commented Oct 28, 2024

verified


Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
8.16 candidate Team:Cloud Security Cloud Security team related
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants