Restrict MDE FileHash - Alert Triggered

Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊

Back to Content Index


This playbook will take FileHash entities and generate alert and block threat indicators for each file hash in MDE for 90 days. It will also add a comment to the incident with the file hash and action taken.

Attribute Value
Type Playbook
Solution MicrosoftDefenderForEndpoint
Source View on GitHub

Logic App Connectors

This playbook uses 2 Logic App connectors / built-in actions:

Connector / Action Type Connections Actions
azuresentinel Managed 1 4
http Built-in 0 2
Action parameters (URLs, paths, function IDs)

azuresentinel (Managed)

Action Method Endpoint Other
Alert_-_Get_incident get /Incidents/subscriptions/@{encodeURIComponent(triggerBody()?['WorkspaceSubscriptionId'])}/resourceGroups/@{encodeURIComponent(triggerBody()?['WorkspaceResourceGroup'])}/workspaces/@{encodeURIComponent(triggerBody()?['WorkspaceId'])}/alerts/@{encodeURIComponent(triggerBody()?['SystemAlertId'])}
Entities_-_Get_FileHashes post /entities/filehash
Add_comment_to_incident_(V3)-1 post /Incidents/Comment
Add_comment_to_incident_(V3)-2 post /Incidents/Comment

http (Built-in)

Action Method Endpoint Other
HTTP POST https://api.securitycenter.windows.com/api/indicators
HTTP_2 POST https://api.securitycenter.windows.com/api/indicators

Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊

Back to Playbooks · Back to MicrosoftDefenderForEndpoint