You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/security-center/security-center-provide-security-contact-details.md
+13-12Lines changed: 13 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,15 +16,18 @@ ms.author: memildin
16
16
17
17
---
18
18
# 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 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.
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.
20
20
21
21
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.
22
22
23
23
Alert email notifications are sent:
24
-
- Only for high severity alerts
25
24
- To a single email recipient per alert type per day
26
25
- No more than 3 email messages are sent to a single recipient in a single day
27
26
- 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.
28
31
29
32
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.
30
33
@@ -33,20 +36,18 @@ For example, if an email message was already sent to alert you about an RDP atta
33
36
34
37
## Set up email notifications for alerts <aname="email"></a>
35
38
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:
39
40
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**.
42
44
43
45
![Provide security contact details][2]
44
46
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**.
50
51
51
52
## See also
52
53
To learn more about Security Center, see the following:
Copy file name to clipboardExpand all lines: articles/security-center/workflow-automation.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -61,7 +61,10 @@ This article describes the workflow automation feature of Azure Security Center.
61
61
In the Logic App designer the following triggers from the Security Center connectors are supported:
62
62
63
63
***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.
65
68
66
69
> [!NOTE]
67
70
> 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