-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Broken Entity Mapping in Azure Active Directory rule template #8946
Comments
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. |
Hi @goosvorbook, thanks for flagging this issue, we will soon get back to you on this. Thanks! |
Hi @goosvorbook, we are looking into this issue, please can you add below shared KQL query while create an analytic rule and let us know if it works for you.
Sharing the steps and screenshot for reference.
Thanks. |
Yes that will work |
Hello @goosvorbook, please can you let us know the above shared steps are work for you? Thanks |
yes they did |
@goosvorbook, Thanks for sharing the update, we will raise the PR with the changes. can we close this issue? please let us know if you need any further assistance. Thanks |
Describe the bug
One of the "Azure Active Directory" Analytic rules from the Content hub have a mismatch on their entity mapping.
Rule:
"Successful logon from IP and failure from a different IP"
Does not actually contain name and UPNSuffix
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Full entity mapping with the correct fields, e.g. Name and UPNSuffix, this requires a rewrite of the KQL to actually contain the Name and UPNSuffix
Screenshots
The text was updated successfully, but these errors were encountered: