Skip to content

Commit 8ed4645

Browse files
committed
Added notes about using WA for alerts at all severity levels
1 parent 55b6231 commit 8ed4645

File tree

2 files changed

+17
-13
lines changed

2 files changed

+17
-13
lines changed

articles/security-center/security-center-provide-security-contact-details.md

Lines changed: 13 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -16,15 +16,18 @@ ms.author: memildin
1616

1717
---
1818
# Provide security contact details in Azure Security Center
19-
Azure Security Center will recommend that you provide security contact details for your Azure subscription if you havent already. This information will be used by Microsoft to contact you if the Microsoft Security Response Center (MSRC) discovers that your customer data has been accessed by an unlawful or unauthorized party. MSRC performs select security monitoring of the Azure network and infrastructure and receives threat intelligence and abuse complaints from third parties.
19+
Azure Security Center will recommend that you provide security contact details for your Azure subscription if you haven't already. This information will be used by Microsoft to contact you if the Microsoft Security Response Center (MSRC) discovers that your customer data has been accessed by an unlawful or unauthorized party. MSRC performs select security monitoring of the Azure network and infrastructure and receives threat intelligence and abuse complaints from third parties.
2020

2121
An email notification is sent on the first daily occurrence of an alert and only for high severity alerts. Email preferences can only be configured for subscription policies. Resource groups within a subscription will inherit these settings. Alerts are available only in the Standard tier of Azure Security Center.
2222

2323
Alert email notifications are sent:
24-
- Only for high severity alerts
2524
- To a single email recipient per alert type per day
2625
- No more than 3 email messages are sent to a single recipient in a single day
2726
- Each email message contains a single alert, not an aggregation of alerts
27+
- Only for high severity alerts
28+
29+
> [!TIP]
30+
> For alerts with other severity levels, create a [workflow automation](workflow-automation.md) to use a Logic App that will send emails to the relevant personnel.
2831
2932
For example, if an email message was already sent to alert you about an RDP attack, you will not receive another email message about an RDP attack on the same day, even if another alert is triggered.
3033

@@ -33,20 +36,18 @@ For example, if an email message was already sent to alert you about an RDP atta
3336
3437
## Set up email notifications for alerts <a name="email"></a>
3538

36-
1. From the portal, select **Pricing & settings**.
37-
1. Click on the subscription.
38-
1. Click **Email notifications**.
39+
1. Open the **Email notifications** page:
3940

40-
> [!NOTE]
41-
> If you are implementing a recommendation, then Under **Recommendations**, select **Provide security contact details**, select the Azure subscription to provide contact information on. This opens **Email notifications**.
41+
1. For alerts, open **Pricing & settings**, select the relevant subscription, and select **Email notifications**.
42+
43+
1. If you are implementing a recommendation, then Under **Recommendations**, select **Provide security contact details**, select the Azure subscription to provide contact information on. This opens **Email notifications**.
4244

4345
![Provide security contact details][2]
4446

45-
* Enter the security contact email address or addresses separated by commas. There is not a limit to the number of email addresses that you can enter.
46-
* Enter one security contact international phone number.
47-
* To receive emails about high severity alerts, turn on the option **Send me emails about alerts**.
48-
* You have the option to send email notifications to subscription owners (classic Service Administrator and Co-Administrators, plus RBAC Owner role at the subscription scope).
49-
* Select **Save** to apply the security contact information to your subscription.
47+
* Enter the security contact email address or addresses separated by commas. There is no limit to the number of email addresses that you can enter.
48+
* To receive emails about high severity alerts, turn on the option **Send me emails about alerts**. For other severity levels use a Logic App as explained in [workflow automation](workflow-automation.md).
49+
* You can send email notifications to subscription owners (classic Service Administrator and Co-Administrators, plus RBAC Owner role at the subscription scope).
50+
* To apply the security contact information to your subscription, select **Save**.
5051

5152
## See also
5253
To learn more about Security Center, see the following:

articles/security-center/workflow-automation.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,10 @@ This article describes the workflow automation feature of Azure Security Center.
6161
In the Logic App designer the following triggers from the Security Center connectors are supported:
6262

6363
* **When an Azure Security Center Recommendation is created or triggered**
64-
* **When an Azure Security Center Alert is created or triggered**
64+
* **When an Azure Security Center Alert is created or triggered**
65+
66+
> [!TIP]
67+
> You can customize the trigger so that it relates only to alerts with the severity levels that interest you.
6568
6669
> [!NOTE]
6770
> If you are using the legacy trigger "When a response to an Azure Security Center alert is triggered", your Logic Apps will not be launched by the Workflow Automation feature. Instead, use either of the triggers mentioned above.

0 commit comments

Comments
 (0)