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

Feature Request - Azure Sentinel - Configure entityMappings and Custom Details on Alert Rules #14078

Open
jstaffin-presidio opened this issue Apr 22, 2021 · 6 comments
Labels
question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Sentinel Service Attention Workflow: This issue is responsible by Azure service team.

Comments

@jstaffin-presidio
Copy link

Azure Sentinel has added a new method for configuring Entity mappings and a method for defining custom details (key/value pairs).

This page describes the Azure Portal method for configuring the Entity Mappings on an alert rule
https://docs.microsoft.com/en-us/azure/sentinel/map-data-fields-to-entities

This page describes the Azure Portal method for configuring the custom details key/value Paris on an alert rule
https://docs.microsoft.com/en-us/azure/sentinel/surface-custom-details-in-alerts

Neither the current GA nor the preview REST or SDK for go support configuring these elements on an alert rule.

At the moment all other aspects of our sentinel deployment are automated except for this capability. We require the ability to map these values to surface required context on the generated alert for use in our SOAR workflows. We currently deploy rules using an automated method and require Azure Portal manual configuration to perform the remaining entity mapping and custom details configuration.

@ghost ghost added needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Apr 22, 2021
@PhoenixHe-NV PhoenixHe-NV added Sentinel Service Attention Workflow: This issue is responsible by Azure service team. labels Apr 26, 2021
@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Apr 26, 2021
@kaovd
Copy link

kaovd commented May 11, 2021

Echoing this standpoint on SOAR Workflows in order to migrate to this new method we need this to come into the specs and downstream to relevant SDK providers for 2021-03-01-preview
https://github.com/Azure/azure-rest-api-specs/tree/master/specification/securityinsights/resource-manager/Microsoft.SecurityInsights/preview/2021-03-01-preview
From the looks of it this still seems heavy in dev and there is no SecurityInsights.json laid out. Is this getting backported to 2019-01-01-preview at all?

@kaovd
Copy link

kaovd commented Jun 10, 2021

I see this got removed from needs triage but still has no assigne - is there any attention to this? I think that #14753 is going to resolve this.

@PhoenixHe-NV PhoenixHe-NV added Service Attention Workflow: This issue is responsible by Azure service team. Sentinel and removed Service Attention Workflow: This issue is responsible by Azure service team. Sentinel labels Jun 11, 2021
@miaxou
Copy link

miaxou commented Sep 1, 2021

Would really like to see the functionality to add/update entityMappings via REST API restored.

@FormindGMO
Copy link

@kaovd you mentionned PR #14753 of swagger specs, flagged as "Merged", yet doesn't seem available in documentation. I don't know about MS internal processes, do you know when could we get the feature implemented?

@kaovd
Copy link

kaovd commented Sep 19, 2021

@FormindGMO in terms of the full RP / Spec this has been pushed back a fair bit and is now scheduled for 2021-09-01 API Spec - See here.
Azure/azure-sdk-for-go#14800

The change did go in, but they need the full stack of specs to produce a Package for it in the SDK and downstream - for that got a central tracker up here in azurerm
hashicorp/terraform-provider-azurerm#11667

However if you are just looking at the API sure you can call the 2021-03-01 API now and just use that
Endpoints at https://management.azure.com/subscriptions/{subid}/resourceGroups/{rg}/providers/Microsoft.OperationalInsights/workspaces/{workspace}/providers/Microsoft.SecurityInsights/alertRules/{id}?api-version=2021-03-01-preview And doc is still https://github.com/Azure/azure-rest-api-specs/blob/master/specification/securityinsights/resource-manager/Microsoft.SecurityInsights/preview/2021-03-01-preview/AlertRules.json. In terms of examples you can just rip the API calls out of the portal when you do stuff to get a better understanding. Also https://docs.microsoft.com/en-us/rest/api/securityinsights/alert-rules/create-or-update#code-try-0 is a nice interface

i.e If you are using something like terraform you can potentially use a null resource script provisioner and pwsh in order to Patch the entityDetails over your current infrastructure - although a bit hacky its a good temporary work around.

@kaovd
Copy link

kaovd commented Jan 27, 2022

@jstaffin-presidio this is closed with release of 2021-09-01-preview

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Sentinel Service Attention Workflow: This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests

5 participants