STIGhubSTIGhub
STIGsRMF ControlsCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 7 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to Microsoft Exchange 2016 Edge Transport Server Security Technical Implementation Guide

V-221233

CAT II (Medium)

Exchange messages with a blank sender field must be filtered.

Rule ID

SV-221233r961161_rule

STIG

Microsoft Exchange 2016 Edge Transport Server Security Technical Implementation Guide

Version

V2R6

CCIs

CCI-001308

Discussion

By performing filtering at the perimeter, up to 90 percent of spam, malware, and other undesirable messages are eliminated from the message stream rather than admitting them into the mail server environment. Anonymous email (messages with blank sender fields) cannot be replied to. Messages formatted in this way may be attempting to hide their true origin to avoid responses or to spam any receiver with impunity while hiding their source of origination. Rather than spend resources and risk infection while evaluating them, it is recommended that these messages be filtered immediately upon receipt and not forwarded to end users.

Check Content

This requirement is N/A for SIPR enclaves. 

This requirement is N/A if the organization subscribes to EEMSG or other similar DoD enterprise protections for email services.

Open the Exchange Management Shell and enter the following command:

Get-SenderFilterConfig | Select Name, BlankSenderBlockingEnabled

If the value of "BlankSenderBlockingEnabled" is not set to "True", this is a finding.

Fix Text

Open the Exchange Management Shell and enter the following command:

Set-SenderFilterConfig -BlankSenderBlockingEnabled $true