forked from Azure/Azure-Sentinel
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request Azure#7888 from BenjiSec/UpdateSOCProcessFramework
update to SOCProcessFramework solution
- Loading branch information
Showing
9 changed files
with
1,173 additions
and
331 deletions.
There are no files selected for viewing
File renamed without changes.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
1,005 changes: 1,005 additions & 0 deletions
1,005
Playbooks/Get-SentinelAlertsEvidence/incident-trigger/azuredeploy.json
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,23 +1,35 @@ | ||
# Get-SentinelAlertsEvidence | ||
Author: Yaniv Shasha | ||
|
||
This playbook will Logic will automatically attach alert evidence from Azure Sentinel alerts and send them to an Event Hub that can be consumed by a 3rd party SIEM solution. | ||
<br><br> | ||
|
||
|
||
Author: Yaniv Shasha | ||
|
||
Deploy the solution | ||
# Prerequisites | ||
1. Create an Event Hub using the article "Create an event hub using Azure portal" <br> | ||
https://docs.microsoft.com/azure/event-hubs/event-hubs-create or use an existing Event Hub. | ||
2. Go to the Playbook GitHub page.<br> | ||
3. Press the "deploy to azure" button.<br> | ||
4. Fill the above information:<br> | ||
- Azure Sentinel Workspace Name<br> | ||
- Azure Sentinel Workspace resource group name<br> | ||
- Number of events to pulls from Azure Sentinel (default value is 10 latest events )<br> | ||
<br><br> | ||
|
||
# Quick Deployment | ||
**Deploy with incident trigger** | ||
|
||
After deployment, you can run this playbook manually on an incident or attach this playbook to an **automation rule** so it runs when the incident is created. | ||
|
||
[![Deploy to Azure](https://aka.ms/deploytoazurebutton)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2FAzure-Sentinel%2Fmaster%2FPlaybooks%2FGet-SentinelAlertsEvidence%2Fincident-trigger%2Fazuredeploy.json) | ||
[![Deploy to Azure Gov](https://aka.ms/deploytoazuregovbutton)](https://portal.azure.us/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2FAzure-Sentinel%2Fmaster%2FPlaybooks%2FGet-SentinelAlertsEvidence%2Fincident-trigger%2Fazuredeploy.json) | ||
|
||
|
||
**Deploy with alert trigger** | ||
|
||
After deployment, you can run this playbook manually on an alert or attach it to an **automation rule** so it will rune when an alert is created. | ||
|
||
4. Once the playbook is deployed, Modify the “Run query and list results” actions and point it to your Azure sentinel workspace.<br> | ||
5. Next, configure the "send event" actions to use your Event Hub that created earlier.<br> | ||
[![Deploy to Azure](https://aka.ms/deploytoazurebutton)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2FAzure-Sentinel%2Fmaster%2FPlaybooks%2FGet-SentinelAlertsEvidence%2Falert-trigger%2Fazuredeploy.json) | ||
[![Deploy to Azure Gov](https://aka.ms/deploytoazuregovbutton)](https://portal.azure.us/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2FAzure-Sentinel%2Fmaster%2FPlaybooks%2FGet-SentinelAlertsEvidence%2Falert-trigger%2Fazuredeploy.json) | ||
<br><br> | ||
|
||
# Post-deployment | ||
1. Once the playbook is deployed, Modify the “Run query and list results” actions and point it to your Azure sentinel workspace.<br> | ||
2. Next, configure the "send event" actions to use your Event Hub that created earlier.<br><br> | ||
|
||
<[![Deploy to Azure](https://aka.ms/deploytoazurebutton)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2FAzure-Sentinel%2Fmaster%2FPlaybooks%2FGet-SentinelAlertsEvidence%2Fazuredeploy.json) | ||
[![Deploy to Azure Gov](https://aka.ms/deploytoazuregovbutton)](https://portal.azure.us/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2FAzure-Sentinel%2Fmaster%2FPlaybooks%2FGet-SentinelAlertsEvidence%2Fazuredeploy.json) | ||
# Screenshots | ||
**Incident Trigger** | ||
![Incident Trigger](./images/playbookDark.jpg) |
440 changes: 132 additions & 308 deletions
440
Solutions/SOC-Process-Framework/Playbooks/Get-SOCActions/azuredeploy.json
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
6 changes: 3 additions & 3 deletions
6
Solutions/SOC-Process-Framework/Watchlists/SOC-Recommended-Actions/SocRA.json
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters