You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
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 ofposture_type
.In order to fix this, we need to adjust the filters to look for
posture type: kspm
The text was updated successfully, but these errors were encountered: