<?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: How to mirror XSOAR severity incident field with an integrations severity in Cortex XSOAR Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/how-to-mirror-xsoar-severity-incident-field-with-an-integrations/m-p/512871#M1134</link>
    <description>&lt;P&gt;It was as easy as just mapping it, I was definitely overthinking it. Thank you!&lt;/P&gt;</description>
    <pubDate>Wed, 24 Aug 2022 15:54:52 GMT</pubDate>
    <dc:creator>king_penson</dc:creator>
    <dc:date>2022-08-24T15:54:52Z</dc:date>
    <item>
      <title>How to mirror XSOAR severity incident field with an integrations severity</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/how-to-mirror-xsoar-severity-incident-field-with-an-integrations/m-p/512396#M1123</link>
      <description>&lt;P&gt;What is the best path to change XSOARs incident severity to match the severity another tool is pulling in?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Ex. PhishER (KnowBe4) has it's own severity field called "PhishER" Severity, I want XSOAR's severity to mirror the incoming PhisihER severity&lt;/P&gt;</description>
      <pubDate>Fri, 19 Aug 2022 18:21:28 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/how-to-mirror-xsoar-severity-incident-field-with-an-integrations/m-p/512396#M1123</guid>
      <dc:creator>king_penson</dc:creator>
      <dc:date>2022-08-19T18:21:28Z</dc:date>
    </item>
    <item>
      <title>Re: How to mirror XSOAR severity incident field with an integrations severity</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/how-to-mirror-xsoar-severity-incident-field-with-an-integrations/m-p/512744#M1132</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/231519"&gt;@king_penson&lt;/a&gt; – The best way to set incident severity in this case would be to add it to the incoming mapper, so the severity field gets set for incoming incidents as they are ingested by the PhishER integration.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;XSOAR support using either a (case-insensitive) string or corresponding integer to set the severity of an incident. The supported Severity values are:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;SPAN&gt;Unknown (0)&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;Informational (0.5)&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;Low (1)&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;Medium (2)&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;High (3)&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;Critical (4)&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;SPAN&gt;If this corresponds with the severity values PhishER uses, you can map the PhishER severity with no modifications. If not, you may need to use transformers such as Replace to change the PhishER severity to an XSOAR-compatible value for the mapper. Please give that a try and let us know if you run into any issues.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 23 Aug 2022 20:33:05 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/how-to-mirror-xsoar-severity-incident-field-with-an-integrations/m-p/512744#M1132</guid>
      <dc:creator>asawyer</dc:creator>
      <dc:date>2022-08-23T20:33:05Z</dc:date>
    </item>
    <item>
      <title>Re: How to mirror XSOAR severity incident field with an integrations severity</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/how-to-mirror-xsoar-severity-incident-field-with-an-integrations/m-p/512871#M1134</link>
      <description>&lt;P&gt;It was as easy as just mapping it, I was definitely overthinking it. Thank you!&lt;/P&gt;</description>
      <pubDate>Wed, 24 Aug 2022 15:54:52 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/how-to-mirror-xsoar-severity-incident-field-with-an-integrations/m-p/512871#M1134</guid>
      <dc:creator>king_penson</dc:creator>
      <dc:date>2022-08-24T15:54:52Z</dc:date>
    </item>
    <item>
      <title>Re: How to mirror XSOAR severity incident field with an integrations severity</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/how-to-mirror-xsoar-severity-incident-field-with-an-integrations/m-p/528503#M1713</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/231519"&gt;@king_penson&lt;/a&gt; what field did you map this data to?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am trying to configure the elasticsearch incoming mapper to set the Incident Severity but it does not work.&lt;/P&gt;</description>
      <pubDate>Wed, 25 Jan 2023 09:36:06 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/how-to-mirror-xsoar-severity-incident-field-with-an-integrations/m-p/528503#M1713</guid>
      <dc:creator>ArthurCircus</dc:creator>
      <dc:date>2023-01-25T09:36:06Z</dc:date>
    </item>
    <item>
      <title>Re: How to mirror XSOAR severity incident field with an integrations severity</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/how-to-mirror-xsoar-severity-incident-field-with-an-integrations/m-p/530135#M1773</link>
      <description>&lt;P&gt;What data type is the data coming in as? (Integer, string)&lt;/P&gt;</description>
      <pubDate>Tue, 07 Feb 2023 15:43:02 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/how-to-mirror-xsoar-severity-incident-field-with-an-integrations/m-p/530135#M1773</guid>
      <dc:creator>king_penson</dc:creator>
      <dc:date>2023-02-07T15:43:02Z</dc:date>
    </item>
  </channel>
</rss>

