Skip to main content
Version: 3.0.0-preview

CIS.M365.6.5.5 - (L2) Ensure Direct Send submissions are rejected

Overviewโ€‹

Exchange Online rejects Direct Send submissions: unauthenticated messages sent to your tenant where the envelope sender (MAIL FROM) domain is one of your accepted domains and no eligible inbound connector matches the message.

Direct Send lets a device or application send mail to your tenant, from an address in your own domain, without signing in. Attackers use the same path to send phishing that looks like internal mail. When RejectDirectSend is turned on, Exchange Online rejects these messages instead of delivering them. It does not reject every anonymous message that shows an internal sender address. For example, a message can use an external envelope sender and still show one of your addresses in the From header. Anti-spoofing controls such as SPF, DKIM, DMARC and spoof intelligence are still needed for those messages.

Before you turn it on, find the devices and applications that rely on Direct Send, for example printers and scanners. Move them to authenticated SMTP submission, SMTP relay with a connector or High Volume Email.

Remediation actionโ€‹

  1. Connect to Exchange Online with Connect-ExchangeOnline.
  2. Run Set-OrganizationConfig -RejectDirectSend $true.
  3. Check the setting with Get-OrganizationConfig | Format-List RejectDirectSend.

Test Metadataโ€‹

FieldValue
Test IDCIS.M365.6.5.5
SeverityMedium
SuiteCIS
ProductExchange Online
FeatureMail flow
AreaEmail and collaboration protection
Resource typeTenant
User impactMedium
Implementation costMedium
MITRE ATT&CKT1566 Phishing, T1684.002 Email Spoofing
Supports benchmarkCIS Microsoft 365 Foundations Benchmark (version 7.0.0), requirement 6.5.5
Benchmark levelL2
Benchmark profilesE3 Level 2
Supports controlscis-m365:6.5.5, nist-800-53-r5:SI-8
PowerShell testTest-MtCisDirectSendRejected
ServicesExchangeOnline

Sourceโ€‹