Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing incident description on Microsoft Defender XDR incidents created by Microsoft Sentinel #10446

Closed
ep3p opened this issue May 7, 2024 · 8 comments
Assignees
Labels
Connector Connector specialty review needed

Comments

@ep3p
Copy link
Contributor

ep3p commented May 7, 2024

Is your feature request related to a problem? Please describe.
Microsoft Defender XDR incidents have NEVER had a description field available in Microsoft Sentinel portal.

When "Incident provider name" is "Azure Sentinel" the incidents HAVE a description.

When "Incident provider name" is "Microsoft Defender XDR" the incidents do NOT have a description (in Microsoft Sentinel portal in Azure).

IF you integrate a Sentinel workspace to Microsoft Defender XDR , ALL the incidents will have now "Microsoft Defender XDR" as "Incident provider name", and ALL the incidents created by Microsoft Sentinel Analytics rules will LOSE their description (in Microsoft Sentinel portal in Azure).

There might be previous playbooks (logic apps) that USED the description field that now is empty, for incidents created by Microsoft Sentinel, and these playbooks now will continuously FAIL.

This is NOT expected, and is not mentioned in Microsoft Docs (https://learn.microsoft.com/en-us/azure/sentinel/microsoft-365-defender-sentinel-integration).

Describe the solution you'd like
Microsoft Defender XDR incidents SHOULD have a description in Microsoft Sentinel portal in Azure. They should not have missing attributes compared to incidents created directly by Microsoft Sentinel.

You should NOT LOSE capabilities when integrating Microsoft Sentinel with Microsoft Defender XDR.

image

image

@v-sudkharat v-sudkharat added the Connector Connector specialty review needed label May 7, 2024
@v-rusraut
Copy link
Contributor

Hi @ep3p
Thanks for flagging this issue, we will investigate this issue and get back to you with some updates by 15 May 2024. Thanks!

@v-rusraut
Copy link
Contributor

Hi @ep3p,
We are working with respective team, we will update you.
Thanks

@v-rusraut
Copy link
Contributor

Hi @ep3p,
We are waiting for response from respective team, we will update you.
Thanks

@v-rusraut
Copy link
Contributor

Hi @ep3p, Hope you're doing good. As you have raised the support case for this same issue, our support team is working on your ticket. ICM is raised for this issue and so this is duplicate issue that's why closing this issue.
Thanks

@ep3p
Copy link
Contributor Author

ep3p commented May 20, 2024

@v-rusraut what do you mean?? I have not raised any support case. I have only opened this issue on this GitHub repository.

@v-rusraut
Copy link
Contributor

Hi @ep3p,
Actually, our support team shared this issue with us and forwarded this ticket with respective team to work on this, so as other respective was working on this issue so we have closed this issue. but as you mentioned you did not raise any support case let us check with support team and verify once.

@v-rusraut
Copy link
Contributor

Hi @ep3p,
We have received the response from respective concern team, The description feature is currently in a private preview as (Enhanced Sync for XDR). so due to that currently it's not visible in incident tab.

Thanks!

@ep3p
Copy link
Contributor Author

ep3p commented May 23, 2024

Thank you very much @v-rusraut, understood.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Connector Connector specialty review needed
Projects
None yet
Development

No branches or pull requests

3 participants