Default Field Mapping in QRadar Content Pack 2.5.7 on XSOAR 6.12

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

Content translations are temporarily unavailable due to site maintenance. We apologize for any inconvenience. Visit our blog to learn more.

Default Field Mapping in QRadar Content Pack 2.5.7 on XSOAR 6.12

L0 Member

Hello everyone,

I’m currently using Cortex XSOAR version 6.12 along with the IBM QRadar content pack version 2.5.7 (1602991). The pack includes two mappers for incoming incidents:

  • QRadar - Generic Incoming Mapper
  • QRadar - Incoming Mapper

However, I’ve noticed that the default configuration of both mappers only maps a few fields from the incident data. This raises a couple of questions:

  1. Is this limited field mapping the expected behavior for these mappers?
  2. Shouldn’t the majority of fields from QRadar be mapped by default so that playbooks can utilize them without additional manual configuration?

I’d appreciate any insights on whether this is by design or if there’s something missing in my setup. If this is normal, how do you recommend approaching the process of mapping additional fields efficiently?

Thanks in advance for your help!

0 REPLIES 0
  • 73 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!