-
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
Update "TI Map" analytics rules for performance #9181
Conversation
To whoever ends up picking this up, the KQL validation failures is due to Line 397 of https://github.com/Azure/Azure-Sentinel/blob/master/.script/tests/KqlvalidationsTests/KqlValidationTests.cs The regex being used is overly-specific and not conducive for the performance improvements being made here. |
Hi @kfriede, thanks for raising this PR. We will review this PR by 13 Oct 2023. |
This traces back to commit 16564be from @aprakash13. Query layouts looked largely performance-optimized before this change. |
Hi @kfriede, for KQL validation, we will see what can be done in this case. We would need you to repackage this solution using this tool https://github.com/Azure/Azure-Sentinel/tree/master/Tools/Create-Azure-Sentinel-Solution/V3 Also update the release notes for the same. Thanks |
Hi @kfriede, please provide update on above comment. |
Hi @kfriede, please provide some update on this PR |
Hi @v-rbajaj, apologies I was out last week. I will look at repackaging the solution for these edits Edit: Solution has been repackaged for 3.0.2 |
@@ -6,7 +6,7 @@ | |||
"config": { | |||
"isWizard": false, | |||
"basics": { | |||
"description": "<img src=\"https://raw.githubusercontent.com/Azure/Azure-Sentinel/master/Logos/Azure_Sentinel.svg\"width=\"75px\" height=\"75px\">\n\n**Note:** Please refer to the following before installing the solution: \r \n • Review the solution [Release Notes](https://github.com/Azure/Azure-Sentinel/tree/master/Solutions/Threat Intelligence/ReleaseNotes.md)\r \n • There may be [known issues](https://aka.ms/sentinelsolutionsknownissues) pertaining to this Solution, please refer to them before installing.\n\nThe Threat Intelligence solution contains data connectors for import of threat indicators into Microsoft Sentinel, analytic rules for matching TI data with event data, workbook, and hunting queries. Threat indicators can be malicious IP's, URL's, filehashes, domains, email addresses etc.\n\n**Data Connectors:** 4, **Workbooks:** 1, **Analytic Rules:** 38, **Hunting Queries:** 5\n\n[Learn more about Microsoft Sentinel](https://aka.ms/azuresentinel) | [Learn more about Solutions](https://aka.ms/azuresentinelsolutionsdoc)", | |||
"description": "<img src=\"https://raw.githubusercontent.com/Azure/Azure-Sentinel/master/Logos/Azure_Sentinel.svg\"width=\"75px\" height=\"75px\">\n\n**Note:** _There may be [known issues](https://aka.ms/sentinelsolutionsknownissues) pertaining to this Solution, please refer to them before installing._\n\nThe Threat Intelligence solution contains data connectors for import of threat indicators into Microsoft Sentinel, analytic rules for matching TI data with event data, workbook, and hunting queries. Threat indicators can be malicious IP's, URL's, filehashes, domains, email addresses etc.\n\n**Workbooks:** 1, **Analytic Rules:** 38, **Hunting Queries:** 5\n\n[Learn more about Microsoft Sentinel](https://aka.ms/azuresentinel) | [Learn more about Solutions](https://aka.ms/azuresentinelsolutionsdoc)", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @kfriede, Please revert this change.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@v-rbajaj done!
1dbaca4
to
4e2bde4
Compare
Hi @kfriede, thanks. We are currently looking into the KQL validations and once that is fixed, we will revisit this PR by 2 Nov 2023. |
Hi @kfriede, we are still investigating on KQL validations, will get back to by 06 Nov 2023. |
Hi @v-rbajaj, it's been over 1 week since your last update. Is this still under review? |
Hi @kfriede, |
Hi @kfriede, we are working on the KQL changes and we will soon provide an update. |
…tatements for performance
…sult differences noted by @blauwers
4e2bde4
to
f07b36b
Compare
@v-rbajaj after refactoring, files now give: |
Hi @kfriede, sorry for the above commits, was trying to fix few errors from KQL validations. We are checking on it, will get back to you by 29 Nov 2023. |
… --
Kevin Friedemann
On Nov 28, 2023 at 5:01 AM -0800, v-rbajaj ***@***.***>, wrote:
Hi @kfriede, can we merge #9369 as the changes there look similar and all the KQL validations have been fixed by @blauwers.
If there are any changes you want to suggest on #9369 or want to contribute your changes, can you please comment on that PR?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Closing this PR as #9369 is merged. |
Required items, please complete
Change(s):
Reason for Change(s):
Version Updated:
Testing Completed:
Checked that the validations are passing and have addressed any issues that are present: