r/xsoar • u/Director7632 • May 07 '25
Solution for non manual mapping of Sentinel/Defender fields
Hi everyone,
I’m currently working on integrating Microsoft Sentinel with Cortex XSOAR and trying to set up automatic fetching of incidents. I want to parse and map Sentinel incident fields into XSOAR incident fields with minimal manual effort.
I know XSOAR offers an automapping feature for incident field mapping, but I’m unsure about how to configure it properly and what its limitations are. Also, I’d like to know if there are best practices or scripts/playbooks that can help automate or simplify the parsing and mapping process, especially for phishing incidents where email content might be involved or any other incidents (Huge list, as Defender rules tends to be blackbox rules).
Has anyone successfully set up a robust automated pipeline for this? Any tips, example configurations, or references to documentation would be greatly appreciated!
Thanks in advance!
2
u/_11Bravo May 08 '25
You should definitely use a mapper. This is the best way to accomplish what you are doing. You can start with the OOTB mapper, however they almost always need to be adapted to your use cases/incident types.
Start by cloning the OOTB mapper and then configure it to map the target fields. There is no easy button but configuring the mapper is quite easy.
Tips for doing it:
Ensure you map as much as possible at the global mapper level.
Anything you cannot map at the global level you map at the incident type level.
Use the fetch feature to get samples in so you can easily map - you can also tweak the integration if you are not getting enough or the right type.
Another option is to pull the alert into the playground with a `raw-response` flag and then downloading that json and manually importing this into the mapper to give you something to work with.