CIS Microsoft Azure Foundations Benchmark v1.4.0/Microsoft Defender for Cloud/35 of 115
2.13Ensure 'Additional email addresses' is Configured with a Security Contact Email
Control family: Microsoft Defender for Cloud
Control description
Microsoft Defender for Cloud emails the subscription owners whenever a high-severity alert is triggered for their subscription. You should provide a security contact email address as an additional email address.
How to implement
ResponsibilityCustomerYou configure and operate this in your own cloud accounts.
When Defender for Cloud raises a serious alert, it emails the subscription's owners. Owners change and often don't read those emails, so a shared security team mailbox is added as well, so that someone who acts on alerts always receives them.
Before you start
The same on every cloud, before the steps in the tabs.
- Choose the security contact: a shared security mailbox, not one person.
- Review it with the other notification settings (2.14, 2.15) at least once a year.
Evidence
- The named security mailbox and its review record
On Azure the tasks add the security mailbox in the Defender for Cloud email notification settings, then keep it checked with the CIS standard.
Task 1Add the security team's address
- Sign in to the Azure portal at portal.azure.com and open Microsoft Defender for Cloud > Environment settings.
- Select the subscription, then Email notifications.
- In the field for specific email addresses (separated by commas), enter the security team's shared mailbox.
- Select Save.
- Check it: reopen Email notifications and confirm the address is listed.
Task 2Keep it checked with the CIS v1.4.0 standard in Defender for Cloud
- Open Microsoft Defender for Cloud > Regulatory compliance and select Manage compliance policies.
- Select the subscription, select Security policies, find CIS Microsoft Azure Foundations Benchmark v1.4.0 and toggle its status to On (once per subscription).
- Back on Regulatory compliance, open the CIS Microsoft Azure Foundations Benchmark v1.4.0 standard and expand recommendation 2.13.
- Open the assessment for Subscriptions should have a contact email address for security issues and add the address to any subscription it lists.
- Check it: every resource under recommendation 2.13 shows as passing after the next evaluation.
Evidence
- Email notifications of each subscription, listing the security mailbox
- The CIS v1.4.0 standard, with recommendation 2.13 passing
Not applicable. This benchmark covers Azure only.
Not applicable. This benchmark covers Azure only.
Console steps as of 5 November 2026. Not every step has been confirmed in a live console yet, and menus and labels can move between releases, so look for the nearest match if one has changed.