<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Cortex CSPM + Azure: Best practices for handling the initial wave of findings? in Cortex XSIAM Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/cortex-xsiam-discussions/cortex-cspm-azure-best-practices-for-handling-the-initial-wave/m-p/1431500#M497</link>
    <description>&lt;P dir="ltr" data-path-to-node="2"&gt;&lt;SPAN&gt;Hi everyone,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P dir="ltr" data-path-to-node="3"&gt;&lt;SPAN class=""&gt;We are about to integrate our Azure subscription into Cortex CSPM.&lt;/SPAN&gt;&lt;SPAN class=""&gt; Since I don't have prior experience with this specific module,&lt;/SPAN&gt;&lt;SPAN&gt; my main concern is how to manage the initial flood of findings,&lt;/SPAN&gt;&lt;SPAN&gt; issues,&lt;/SPAN&gt;&lt;SPAN&gt; and potential false positives once the read-only connection is established.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P dir="ltr" data-path-to-node="4"&gt;&lt;SPAN&gt;I understand that these are initially logged as &lt;/SPAN&gt;&lt;I data-index-in-node="48" data-path-to-node="4"&gt;findings&lt;/I&gt;&lt;SPAN&gt; rather than &lt;/SPAN&gt;&lt;I data-index-in-node="69" data-path-to-node="4"&gt;incidents&lt;/I&gt;&lt;SPAN&gt;,&lt;/SPAN&gt;&lt;SPAN&gt; but I would like to ask the community:&lt;/SPAN&gt;&lt;/P&gt;
&lt;UL dir="ltr" data-path-to-node="5"&gt;
&lt;LI&gt;
&lt;P dir="ltr" data-path-to-node="5,0,0"&gt;&lt;STRONG data-index-in-node="0" data-path-to-node="5,0,0"&gt;Handling the Volume:&lt;/STRONG&gt;&lt;SPAN&gt; How do you manage and filter this massive initial wave of findings to prevent them from skewing the posture metrics on the dashboards?&lt;/SPAN&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P dir="ltr" data-path-to-node="5,1,0"&gt;&lt;STRONG data-index-in-node="0" data-path-to-node="5,1,0"&gt;Configuration &amp;amp; Tuning:&lt;/STRONG&gt;&lt;SPAN&gt; What is the recommended workflow to tune the module,&lt;/SPAN&gt;&lt;SPAN&gt; rule out false positives,&lt;/SPAN&gt;&lt;SPAN&gt; and configure these findings effectively right after deployment?&lt;/SPAN&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;P dir="ltr" data-path-to-node="6"&gt;&lt;SPAN&gt;Any guidance,&lt;/SPAN&gt;&lt;SPAN&gt; best practices,&lt;/SPAN&gt;&lt;SPAN&gt; or documentation on how to set this up would be greatly appreciated!&lt;/SPAN&gt;&lt;/P&gt;
&lt;P dir="ltr" data-path-to-node="7"&gt;&lt;SPAN&gt;Thanks in advance.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 19 Nov 2026 16:21:56 GMT</pubDate>
    <dc:creator>j.gamarra</dc:creator>
    <dc:date>2026-11-19T16:21:56Z</dc:date>
    <item>
      <title>Cortex CSPM + Azure: Best practices for handling the initial wave of findings?</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xsiam-discussions/cortex-cspm-azure-best-practices-for-handling-the-initial-wave/m-p/1431500#M497</link>
      <description>&lt;P dir="ltr" data-path-to-node="2"&gt;&lt;SPAN&gt;Hi everyone,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P dir="ltr" data-path-to-node="3"&gt;&lt;SPAN class=""&gt;We are about to integrate our Azure subscription into Cortex CSPM.&lt;/SPAN&gt;&lt;SPAN class=""&gt; Since I don't have prior experience with this specific module,&lt;/SPAN&gt;&lt;SPAN&gt; my main concern is how to manage the initial flood of findings,&lt;/SPAN&gt;&lt;SPAN&gt; issues,&lt;/SPAN&gt;&lt;SPAN&gt; and potential false positives once the read-only connection is established.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P dir="ltr" data-path-to-node="4"&gt;&lt;SPAN&gt;I understand that these are initially logged as &lt;/SPAN&gt;&lt;I data-index-in-node="48" data-path-to-node="4"&gt;findings&lt;/I&gt;&lt;SPAN&gt; rather than &lt;/SPAN&gt;&lt;I data-index-in-node="69" data-path-to-node="4"&gt;incidents&lt;/I&gt;&lt;SPAN&gt;,&lt;/SPAN&gt;&lt;SPAN&gt; but I would like to ask the community:&lt;/SPAN&gt;&lt;/P&gt;
&lt;UL dir="ltr" data-path-to-node="5"&gt;
&lt;LI&gt;
&lt;P dir="ltr" data-path-to-node="5,0,0"&gt;&lt;STRONG data-index-in-node="0" data-path-to-node="5,0,0"&gt;Handling the Volume:&lt;/STRONG&gt;&lt;SPAN&gt; How do you manage and filter this massive initial wave of findings to prevent them from skewing the posture metrics on the dashboards?&lt;/SPAN&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P dir="ltr" data-path-to-node="5,1,0"&gt;&lt;STRONG data-index-in-node="0" data-path-to-node="5,1,0"&gt;Configuration &amp;amp; Tuning:&lt;/STRONG&gt;&lt;SPAN&gt; What is the recommended workflow to tune the module,&lt;/SPAN&gt;&lt;SPAN&gt; rule out false positives,&lt;/SPAN&gt;&lt;SPAN&gt; and configure these findings effectively right after deployment?&lt;/SPAN&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;P dir="ltr" data-path-to-node="6"&gt;&lt;SPAN&gt;Any guidance,&lt;/SPAN&gt;&lt;SPAN&gt; best practices,&lt;/SPAN&gt;&lt;SPAN&gt; or documentation on how to set this up would be greatly appreciated!&lt;/SPAN&gt;&lt;/P&gt;
&lt;P dir="ltr" data-path-to-node="7"&gt;&lt;SPAN&gt;Thanks in advance.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 19 Nov 2026 16:21:56 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xsiam-discussions/cortex-cspm-azure-best-practices-for-handling-the-initial-wave/m-p/1431500#M497</guid>
      <dc:creator>j.gamarra</dc:creator>
      <dc:date>2026-11-19T16:21:56Z</dc:date>
    </item>
  </channel>
</rss>

