Microsoft Sentinel
A scalable, cloud-native solution for security information event management and security orchestration automated response. Previously known as Azure Sentinel.
1,224 questions
Alert XX was added to the incident by Microsoft Defender XDR - alert correlation
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(176, 37%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EHL%3C/text%3E%3C/svg%3E)
Horne, Lorents Birkeland
0
Reputation points
Hey, I am sending alarms/incidents from another SIEM to sentinel for centralization. The goal is that sentinel mirrors the alarms/incidents exactly.
The data is sent to a custom log table, in the log analytics workspace through an API call, and I have a NRT analytics rule that creates an alert pr event, and places it in an incident in sentinel.
But if any of the N next alarms being sent from my other SIEM has the same entities, XDR correlates them into one incident. This breaks my mirroring. I have tried to set an entity with a unique identifier to be created in each alert, but that doesn't work.
Any idea how I can exclude the alarms/incidents created from my custom table from this alert correlation?
Sign in to answer