How to mirror XSOAR severity incident field with an integrations severity

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Please sign in to see details of an important advisory in our Customer Advisories area.

How to mirror XSOAR severity incident field with an integrations severity

L1 Bithead

What is the best path to change XSOARs incident severity to match the severity another tool is pulling in? 

 

Ex. PhishER (KnowBe4) has it's own severity field called "PhishER" Severity, I want XSOAR's severity to mirror the incoming PhisihER severity

1 accepted solution

Accepted Solutions

L3 Networker

Hi @king_penson – 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.

 

XSOAR support using either a (case-insensitive) string or corresponding integer to set the severity of an incident. The supported Severity values are:

  • Unknown (0)
  • Informational (0.5)
  • Low (1)
  • Medium (2)
  • High (3)
  • Critical (4)

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.

View solution in original post

4 REPLIES 4

L3 Networker

Hi @king_penson – 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.

 

XSOAR support using either a (case-insensitive) string or corresponding integer to set the severity of an incident. The supported Severity values are:

  • Unknown (0)
  • Informational (0.5)
  • Low (1)
  • Medium (2)
  • High (3)
  • Critical (4)

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.

It was as easy as just mapping it, I was definitely overthinking it. Thank you!

L1 Bithead

@king_penson what field did you map this data to?

 

I am trying to configure the elasticsearch incoming mapper to set the Incident Severity but it does not work.

What data type is the data coming in as? (Integer, string)

  • 1 accepted solution
  • 2405 Views
  • 4 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!