-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Create Machine_Learning_Creation.yaml #11766
base: master
Are you sure you want to change the base?
Conversation
Machine Learning Analytic rule creation
added severity machine learning analytic
added aggregation
fixed azureresource
added frequency
Not exactly sure why ran against detecction and workbook template, anything specific i need to change? mine looks exacly like the current yaml files in analytics |
@v-prasadboke anything I need to change here |
Please add field query period. you can refer to any of the analytic rule from the solution. you keep it null as well. also please take a look at failing validation for api in workbook |
@v-prasadboke thanks I was able to pass everything now |
Machine learning creation event analytic
Required items, please complete
Change(s):
Added a new detection rule for Azure Machine Learning Write Operations.
Updated the YAML configuration to include tactics and techniques relevant to potential rogue access or resource creation.
Reason for Change(s):
To monitor and investigate write operations on Azure Machine Learning resources, ensuring that any unauthorized access or resource creation is detected.
Resolves ISSUE #1234 (if applicable).
Version Updated:
Yes
Detections/Analytic Rule templates are required to have the version updated.
Testing Completed:
Yes
The code has been tested in a Microsoft Sentinel environment to validate syntax and execution.
Checked that the validations are passing and have addressed any issues that are present:
Yes