<?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 Re: Drop and Update but NOT Create (Pre-Processing) in Cortex XSOAR Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/drop-and-update-but-not-create-pre-processing/m-p/569754#M2913</link>
    <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/320837"&gt;@AFamera&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Drop and Update by design creates an incident from the incoming event if the comparison criteria with the existing incident is not met.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;For a complex logic like this, I would recommend using a script to cover all the options. You can take a look at some out of the box sample scripts by navigating to Automations and searching for &lt;STRONG&gt;tags: preProcessing&lt;/STRONG&gt;. Please note that pre-processing script should always return &lt;STRONG&gt;True&lt;/STRONG&gt; (if the incident will be created based on matching criteria) or &lt;STRONG&gt;False&lt;/STRONG&gt; (if the incident will be dropped).&lt;BR /&gt;From within the script, you can access your incoming event details to create your logic and make the decision and also update your existing incidents (Bitsight grade changes).&lt;BR /&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 13 Dec 2023 17:45:18 GMT</pubDate>
    <dc:creator>AbelSantamarina</dc:creator>
    <dc:date>2023-12-13T17:45:18Z</dc:date>
    <item>
      <title>Drop and Update but NOT Create (Pre-Processing)</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/drop-and-update-but-not-create-pre-processing/m-p/563971#M2796</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am trying to write some preprocessing rules to report on and update BitSight incidents. I only want to create incidents that have a grade of 'BAD' or 'WARN'. I do want to capture, however, when a given incident's grade is updated within BitSight to 'GOOD', because that will let me know the issue is resolved. I wrote my pre-processing rules in the following order:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;1. Drop and Update incidents with the same rolled up id&lt;/P&gt;
&lt;P&gt;2. Drop incidents that do not affect the BitSight rating&lt;/P&gt;
&lt;P&gt;3. Drop incidents that are not BAD/WARN&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;My thought process was that, if an incident already exists in Xsoar, and it's grade is updated in BitSight, I want to capture the new grade in the Xsoar incident when the integration fetches it. If it does not exits Xsoar, then I only want to create incidents that affect our score and have a poor grade. The "Drop and Update" function, however, will create an incident if the criteria is not met (unlike the "Drop" function, which just skips to the next rule). &lt;STRONG&gt;Is there a way to do a "Drop and Update" in the pre-processing step without having it create an incident if the criteria isn't met?&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you!&lt;/P&gt;</description>
      <pubDate>Wed, 01 Nov 2023 23:52:19 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/drop-and-update-but-not-create-pre-processing/m-p/563971#M2796</guid>
      <dc:creator>AFamera</dc:creator>
      <dc:date>2023-11-01T23:52:19Z</dc:date>
    </item>
    <item>
      <title>Re: Drop and Update but NOT Create (Pre-Processing)</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/drop-and-update-but-not-create-pre-processing/m-p/569754#M2913</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/320837"&gt;@AFamera&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Drop and Update by design creates an incident from the incoming event if the comparison criteria with the existing incident is not met.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;For a complex logic like this, I would recommend using a script to cover all the options. You can take a look at some out of the box sample scripts by navigating to Automations and searching for &lt;STRONG&gt;tags: preProcessing&lt;/STRONG&gt;. Please note that pre-processing script should always return &lt;STRONG&gt;True&lt;/STRONG&gt; (if the incident will be created based on matching criteria) or &lt;STRONG&gt;False&lt;/STRONG&gt; (if the incident will be dropped).&lt;BR /&gt;From within the script, you can access your incoming event details to create your logic and make the decision and also update your existing incidents (Bitsight grade changes).&lt;BR /&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 13 Dec 2023 17:45:18 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/drop-and-update-but-not-create-pre-processing/m-p/569754#M2913</guid>
      <dc:creator>AbelSantamarina</dc:creator>
      <dc:date>2023-12-13T17:45:18Z</dc:date>
    </item>
  </channel>
</rss>

