- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
12-31-2024 09:17 AM
Hi everyone,
I’m working on a QRadar integration (v2.5.7) in Cortex XSOAR (v6.12) and need to generate a JSON file for a specific offense to use in several scenarios, such as configuring an incident classifier. For example, in the classifier editor, you can upload a JSON file to analyze the data structure and map the fields correctly.
Here’s the situation:
#12 509 Impossible Travel Detected containing Primary Authentication Success
.I’ve tried running !js script="return ${.}"
in the War Room of the specific incident, but the JSON it returns contains significantly more fields than the one shown in the classifier editor when pulling data from QRadar.
I’ve also considered using the command:
!get-remote-data id=<offense_id> lastUpdate=<date_str>
Additionally, is it possible to extract the exact JSON used by XSOAR when it pulls data for the incident directly from QRadar, without additional fields or transformations?
Thanks in advance for your help!
01-07-2025 01:26 AM
Hey there,
thats a good question, top of mind and if I understood the question correctly, you could
01-07-2025 04:07 AM
Hi,
I found this command in the QRadar integration: !get-remote-data id=<offense_id> lastUpdate=<yyyymmdd>
.
This command retrieves only the data that XSOAR fetches from QRadar. After fetching the offense, XSOAR enriches it and adds more contextual information.
I need the original data to setup the mapper for QRadar offense to XSOAR fields. I can not use the context data because the mapping is done before the context data is available. Indeed, the mapper does build the context from the QRadar offense fields.
Regards,
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!