Azure-Sentinel/Playbooks/Start-MDEAutomatedInvestiga...
Lior Tamir aad48299ca Update playbook trigger names 2022-02-22 17:02:56 +02:00
..
alert-trigger Update playbook trigger names 2022-02-22 17:02:56 +02:00
incident-trigger Update playbook trigger names 2022-02-22 17:02:56 +02:00
readme.md updated README.MD 2021-09-01 15:24:57 -07:00

readme.md

Start-MDEAutomatedInvestigation

author: Nicholas DiCola

This playbook will call the start automated investigation in MDE. It will then add a comment to the incident and post a message in Teams.

Quick Deployment

Deploy with incident trigger (recommended)

After deployment, attach this playbook to an automation rule so it runs when the incident is created.

Learn more about automation rules

Deploy to Azure Deploy to Azure Gov

Deploy with alert trigger

After deployment, you can run this playbook manually on an alert or attach it to an analytics rule so it will rune when an alert is created.

Deploy to Azure Deploy to Azure Gov

Prerequisites

  • This blog shows some simple methods to get the Team Id. You will need the Team Id and Channel Id.
  • You will need to grant Alert.ReadWrite.All permissions to the managed identity. Run the following code replacing the managed identity object id. You find the managed identity object id on the Identity blade under Settings for the Logic App.
$MIGuid = "<Enter your managed identity guid here>"
$MI = Get-AzureADServicePrincipal -ObjectId $MIGuid

$MDEAppId = "fc780465-2017-40d4-a0c5-307022471b92"
$PermissionName = "Alert.ReadWrite.All" 

$MDEServicePrincipal = Get-AzureADServicePrincipal -Filter "appId eq '$MDEAppId'"
$AppRole = $MDEServicePrincipal.AppRoles | Where-Object {$_.Value -eq $PermissionName -and $_.AllowedMemberTypes -contains "Application"}
New-AzureAdServiceAppRoleAssignment -ObjectId $MI.ObjectId -PrincipalId $MI.ObjectId `
-ResourceId $MDEServicePrincipal.ObjectId -Id $AppRole.Id

Screenshots

Incident Trigger
Incident Trigger

Alert Trigger
Alert Trigger