Skip to content

Commit 32f0c16

Browse files
committed
continued draft
1 parent 49ba5cd commit 32f0c16

File tree

2 files changed

+7
-4
lines changed

2 files changed

+7
-4
lines changed

articles/sentinel/TOC.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -242,10 +242,10 @@
242242
href: authenticate-playbooks-to-sentinel.md
243243
- name: Use triggers and actions in playbooks
244244
href: playbook-triggers-actions.md
245-
- name: Use a watchlist and playbook to inform about alerts
246-
href: watchlists-playbooks-alerts.md
247245
- name: Customize playbooks from templates
248246
href: use-playbook-templates.md
247+
- name: Automate activity with both watchlists and playbooks
248+
href: automate-playbook-watchlists.md
249249
- name: Manage Microsoft Sentinel
250250
items:
251251
- name: Microsoft Sentinel for MSSPs

articles/sentinel/automate-playbook-watchlist.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Use a Microsoft Sentinel watchlist and playbook to inform owners of alerts
2+
title: Use a Microsoft Sentinel watchlist and playbook together to automate activity
33
description: Learn how to create a Microsoft Sentinel watchlist and playbook based on a Microsoft Defender for Cloud incident creation rule to inform resource owners of security alerts.
44
author: batamig
55
ms.author: bagol
@@ -9,8 +9,11 @@ ms.date: 09/20/2021
99

1010
# Use Microsoft Sentinel watchlists and playbooks together to automate activity
1111

12-
This article describes two, common situations where using watchlists and playbooks together are helpful in automating activity in your systems: informing resource owners about alerts and responding to incidents with deny and allow lists.
12+
This article describes two common situations where using watchlists and playbooks together are helpful in automating activity in your systems: informing resource owners about alerts and responding to incidents with allow lists.
1313

14+
> [!TIP]
15+
> Use these sample playbooks as examples or templates for how you can create automation in your own system, modifying the values as needed.
16+
>
1417
## Automatically inform owners of alerts
1518

1619
[Microsoft Defender for Cloud alerts](/azure/defender-for-cloud/defender-for-cloud-introduction) inform the Security Operations Center (SOC) about possible security attacks on Azure resources.

0 commit comments

Comments
 (0)