# How are you tuning Wiz scope rules to reduce alert churn in ephemeral Kubernetes workloads?

Wiz has given us strong visibility into container images and Kubernetes clusters without needing in-container agents, and the Security Graph helps connect vulnerabilities to misconfigurations and network exposure so we can focus on true runtime risk. It has also helped with multi-cloud container blind spots and Kubernetes configuration drift by mapping issues like exposed pod ports and overly permissive RBAC into one view with clear remediation steps. The main challenge has been alert churn in highly dynamic, ephemeral workloads when initial scope rules are not tuned carefully. How are others setting up scoping and alerting so it stays actionable as workloads change?

##### Post Metadata
- Posted at: 8 days ago
- Author title: --
- Net upvotes: 1



## Related Product
[Wiz](https://www.g2.com/products/wiz-wiz/reviews)

## Related Category
[Cloud Security Posture Management (CSPM)](https://www.g2.com/categories/cloud-security-posture-management-cspm)

## Related discussions
- [How well does Trello scale into a larger team?](https://www.g2.com/discussions/1-how-well-does-trello-scale-into-a-larger-team)
  - Posted at: over 13 years ago
  - Comments: 6
- [Can we please add a new section](https://www.g2.com/discussions/2-can-we-please-add-a-new-section)
  - Posted at: over 13 years ago
  - Comments: 0
- [Quantifiable benefits from implementing your CRM](https://www.g2.com/discussions/quantifiable-benefits-from-implementing-your-crm)
  - Posted at: over 13 years ago
  - Comments: 4