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

Different Alert Descriptions from MDI and Sentinel #8965

Closed
jeffrywu28 opened this issue Sep 7, 2023 · 8 comments
Closed

Different Alert Descriptions from MDI and Sentinel #8965

jeffrywu28 opened this issue Sep 7, 2023 · 8 comments
Assignees

Comments

@jeffrywu28
Copy link

Describe the bug
There is a significant difference number descriptions when you are see M365 Portal Alert and Sentinel Alert.

To Reproduce
Steps to reproduce the behavior:

  1. Go to m365 Defender portal
  2. Click on Alert > filter the alert named "Suspicious Brute-force attack (LDAP)" alert from MDI > Click for details
  3. Scroll down to Descriptions
  4. Then Go to sentinel portal
  5. Click on Alert > choose the same alert. "Suspicious Brute-force attack (LDAP)"
  6. See the really different number

Expected behavior
Same Number from m365 Portal and sentinel.

Screenshots
image
image

Additional context
It's such a huge different right? but why?

@github-actions
Copy link
Contributor

github-actions bot commented Sep 7, 2023

Thank you for submitting an Issue to the Azure Sentinel GitHub repo! You should expect an initial response to your Issue from the team within 5 business days. Note that this response may be delayed during holiday periods. For urgent, production-affecting issues please raise a support ticket via the Azure Portal.

@v-sudkharat
Copy link
Contributor

Hi @jeffrywu28, thanks for flagging this issue, we will soon get back to you on this. Thanks!

@jeffrywu28
Copy link
Author

Hi @jeffrywu28, thanks for flagging this issue, we will soon get back to you on this. Thanks!

Any updates?

@v-sudkharat
Copy link
Contributor

Hello @jeffrywu28, we are connecting with our concerned team for this issue, once we get any information on this, we will update you. Thanks!

@v-sudkharat
Copy link
Contributor

Hello @jeffrywu28, Apologies for the inconvenience and delay. This issue needs to be further investigation. could you please create a support case for this issue? so, support team can connect with you to get more details that are needed about the problem and assist you in fixing it.
Please confirm us once you raise a support case so that we can close this issue from GitHub.
Thanks!

@v-sudkharat
Copy link
Contributor

Hello @jeffrywu28, could you please let us know if you have raised a support case and got assistance for this issue? so we can close this issue from GitHub.

@v-sudkharat
Copy link
Contributor

Hi @jeffrywu28, Gentle Reminder: We are waiting for your response on this issue. If you still need to keep this issue active, please respond to it in the next 2 days. If we don't receive a response by 28-09-2023 date, we will be closing this issue.
Thanks!

@v-sudkharat
Copy link
Contributor

Hi @jeffrywu28, since we have not received a response in the last 5 days, we are closing your issue #8965 as per our standard operating procedures. If you still need support for this issue, feel free to re-open at any time. Thank you for your co-operation.

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

No branches or pull requests

4 participants