Cortex CSPM + Azure: Best practices for handling the initial wave of findings?

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

Cortex CSPM + Azure: Best practices for handling the initial wave of findings?

L0 Member

Hi everyone,

We are about to integrate our Azure subscription into Cortex CSPM. Since I don't have prior experience with this specific module, my main concern is how to manage the initial flood of findings, issues, and potential false positives once the read-only connection is established.

I understand that these are initially logged as findings rather than incidents, but I would like to ask the community:

  • Handling the Volume: How do you manage and filter this massive initial wave of findings to prevent them from skewing the posture metrics on the dashboards?

  • Configuration & Tuning: What is the recommended workflow to tune the module, rule out false positives, and configure these findings effectively right after deployment?

Any guidance, best practices, or documentation on how to set this up would be greatly appreciated!

Thanks in advance.

0 REPLIES 0
  • 8 Views
  • 0 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!