Cortex XSOAR Context Issue

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

Cortex XSOAR Context Issue

L1 Bithead


Hi Everyone, 

I have Cortex XSOAR with SplunkPY running and fetching incidents. I am using Splunk classifier and Splunk incoming mapper by default. 

Drill down is being enriched successfully and i can see it parsed at both classifier & mapper stages - see below screenshot

drilldown parsed in classifier&mapperdrilldown parsed in classifier&mapper

However, context is not splitting drill down details , It's all coming in one chunk of data and cannot be used in any playbook. - Below screenshot


drilldown nor parsed in contextdrilldown nor parsed in context


Any ideas what might be causing this? Is there anywhere else to check that might affect Drilldown parsing in context?


L0 Member

I think you have a transform issue.  

Look at the following link on YouTube to MOD44's PCSAE - Palo Alto Networks - Certification- Training- Domain 1 

Skip ahead to 34:15, I think this will help you.


@Strunce thank you for your reply. 

This video discusses splitting data at classifier level, but I have that already applied in my classifier & mapper as per the above screenshots. No transformations are present within my classifier or mapper. 

I just created a complete new account with fresh installation and integration with a totally different Splunk instance and the same issue persists. 

Do you happen to know how data is filled into context and what controls this process? should I dig into automations for pre-processing rules?

Hi @Rawabdeh , the fields you are showing (incident -> labels -> drilldown) are not being mapped. By default, each mapper has a couple of fields mapped. The rest of the fields are copied verbatim into the context data under "labels". This setting can be disable (if you wanted to) under the settings of the mapper under Advanced:



All data under the labels will be as presented by the source technology. If you would like the data parsed, you would need to alter the Splunk incoming mapper to map that field.


Do you know how you would like the data presented? As a table perhaps?





L1 Bithead

Thank you for your contribution @ABurt 

Actually drill down is supposed to look like the first screenshot (I'm using it in my playbooks as Drilldown.[0].Country.[0] >> maps to: Saudi Arabia in the first screenshot)

I have tried checking that box you mentioned and indeed, it stopped throwing all JSON details under incident.labels and I was able to use the custom field (mapped with drilldown values) I created. But that means I have to create a field for each value in each alert coming from Splunk and i don't think that's a feasible solution.


What's confusing me is that context had drill down parsed just the way it's seen in mapper and I built my playbooks based on this format. Out of nowhere it noticed empty data in sub-playbooks and found out about this issue. No changes were applied on any account


During the classification and mapping this is generally the way data is processed:

  1. Classification determines what type of incident each new incident creation is created as
  2. Mapping (specifically incoming in this instance) maps all the fields based on the type of incident (or globally)


It looks as if the incoming mapper in screenshot 1 is populating a field named "drilldown" in the incident. This would honour the transformation happening at the mapper (i.e. the parseJSON transformer). The second screenshot, when data ends up in the labels, does not undergo any mapper rules such as the parse JSON.


In the first screenshot, is the "drilldown" appearing in the incident as its own field or is this under the same "labels" as in the second screenshot?

@ABurt  This is exactly what's happening, context is not picking up this exact JSON parser. 

Drill down is coming under label as shown in this screenshot




Here i say it again, it was all parsed before and i built my playbooks based on these values.


Has anything else changed since you built the playbooks. Such as updating XSOAR or any changes to Splunk?

That's what I've been trying to find out. the only changes I've made are on playbook inputs and classification. I have no idea how context parsing started behaving like this

I have just created 4 fields and mapped their values to drill down details and it's working fine. I know this isn't the best practice to create custom fields for each alert coming from Splunk. This was only for testing purposes. 

I can confirm that this isn't related to drill down fetching or mapping. issue is narrowed down to context display i believe.







  • 9 replies
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!