Administrators should be notified when an internal user sends malware
This check looks at the anti-malware policies in Exchange Online and whether administrators are notified when a message from an internal sender is found to contain malware. The safe setting is to have that notification on and pointed at a mailbox that someone actually reads.
Why it matters
When a message sent from inside your own organisation contains malware, the sender is rarely the real culprit. A far more likely explanation is a compromised account or an infected device that is sending mail on the user's behalf. That makes an internal malware detection one of the clearest early signs of a problem that is already inside your environment.
Without a notification, the detection is handled quietly by the filtering service and nobody learns that an account or machine needs attention. Microsoft's anti-malware policy settings include an option to notify an administrator about messages from internal senders that are quarantined as malware (Configure anti-malware policies). Turning it on turns a silent block into a prompt to investigate the sender.
How to check it yourself
In the Microsoft Defender portal, open Email & collaboration > Policies & rules > Threat policies > Anti-malware, select a policy and look under Notifications for the option to notify an administrator about undelivered messages from internal senders, plus the address that receives them.
From PowerShell, these read-only commands show the same fields for every policy:
Connect-ExchangeOnline
Get-MalwareFilterPolicy | Format-Table Identity, EnableInternalSenderAdminNotifications, InternalSenderAdminAddressEach policy should show EnableInternalSenderAdminNotifications as True and an address that is not empty. Check that the address is a mailbox or group that is monitored, not a former employee or a dead alias.
How to fix it
In the Defender portal, open the anti-malware policy, choose Edit protection settings, and under Notifications tick the option to notify an administrator about undelivered messages from internal senders. Enter the address of your security or IT mailbox and save.
With PowerShell, an administrator can set it as follows, replacing the address with your own monitored mailbox:
Set-MalwareFilterPolicy -Identity "Default" -EnableInternalSenderAdminNotifications $true -InternalSenderAdminAddress "security-alerts@contoso.example"Do this for each policy that your check reported. The commands change your tenant, so review them first. ConfigCobra only reads your tenant and shows you what to do; it never makes the change.
What changes when you fix it
No user sees any difference in how mail is delivered or blocked. The only change is that the chosen administrator address starts to receive a notification each time an internal sender's message is caught as malware.
That means the person or team behind the address should expect extra mail, and should agree beforehand what to do when one arrives: reset the sender's credentials, check the device, and look at recent sign-ins. In a tenant with a lot of unmanaged devices, the first days may bring more notifications than expected, because the setting reveals problems that were already there. Use a shared mailbox or distribution group rather than a personal address, so the notifications do not stop when one person is away or leaves.
Included in
| Benchmark | CIS ID | Profile |
|---|---|---|
| CIS Microsoft 365 Foundations v7.0.0 | 2.1.3 | E3 Level 1 |
More checks in Microsoft Defender
- Safe Links for Office Applications should be enabledCIS 2.1.1
- The common attachment types filter should be enabledCIS 2.1.2
- Safe Attachments policy should be enabledCIS 2.1.4
- Safe Attachments for SharePoint, OneDrive, and Microsoft Teams should be enabledCIS 2.1.5
- Exchange Online spam policies should notify administratorsCIS 2.1.6
Go further
- Microsoft Defender21 controls in this section
- CIS Microsoft 365 Foundations v7.0.0160 controls
- CIS Microsoft 365 Foundations checklistEvery control in one list, as CSV
- RemediationSee what a fix changes in your tenant before you apply it, then use the generated script
- Monitoring & DriftScheduled scans, drift detection and email alerts when a control regresses
Check this on your Microsoft 365
ConfigCobra runs this check with every other control of the CIS Microsoft 365 Foundations Benchmark, read-only.