-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Support for Azure Sentinel Automation Rules #10960
Comments
Since creating my issue, it appears automation rules have gone public preview, with the relevant API Specs updated. I believe the issues that where previously encountered by @magodo have been solved in this API Spec, I see a very verbose response, with trigger Uri's for playbooks that where the previous blocking issue. New Specs here |
+1 This'll enhance our workflow and finally stop half of the manual editing of rules after running the pipeline. |
Just asked for a Go SDK release for this. Once it is done, we can move on. |
Got an issue link? |
@kaovd Unfortunately, this is driven by some internal infra. I've seen the release request issue has already been created, should be available in https://github.com/azure/azure-sdk-for-go soon. You can subscribe the release notification for that repo. |
Could this be it? @magodo - Looks promising on this release git diff Azure/azure-sdk-for-go@b7b1995 |
+1 this should make a world of difference to my organisations workflow. |
This PR implements a new sentinel resource called Automation Rule. This fixes: #10960.
This functionality has been released in v2.83.0 of the Terraform Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Community Note
Description
With the current blocked limbo that is the request for sentinel alert rule playbook actions (see Azure/azure-rest-api-specs#9424 spawned from #6820) - I believe rather than actually implementing this original feature, it is more likely that the new automations framework that will be coming out (currently in preview) is more favourable (mentioned on a duplicate complaint about triggerUrl not returning here.
As this is currently available and uses the preview API Spec instead, this might be implementable while still in its preview state via the 2019-01-01 Preview api here - however I'm not sure if the functionality from the automationRules api is actually implemented within this repository yet, while I can make it out in watching the API Calls, a ctrl f for an example containing this cannot be found... The feature is accessible through visiting aka.ms/incidenttrigger (prepends ?Feature.IncidentTriggering=true before #blade) and visiting an azure sentinel workspace. I don't believe this requires a preview sign up as from a fresh account I tested, this is accessible.Shortly after I originally made this request, the features went public preview and an API Spec is now available here
The functionality is under Microsoft.SecurityInsights/AutomationRules
New or Affected Resource(s)
Potential Terraform Configuration
References
The text was updated successfully, but these errors were encountered: