Exchange messages with a malformed From address must be rejected.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-221242 | EX16-ED-000430 | SV-221242r1040907_rule | CCI-001308 | medium |
| Description | ||||
| Sender Identification (SID) is an email antispam sanitization process. Sender ID uses DNS MX record lookups to verify the Simple Mail Transfer Protocol (SMTP) sending server is authorized to send email for the originating domain. Failure to implement Sender ID risks that spam could be admitted into the email domain that originates from rogue servers. Most spam content originates from domains where the IP address has been spoofed prior to sending, thereby avoiding detection. For example, messages with malformed or incorrect "purported responsible sender" data in the message header could be (best case) created by using RFI noncompliant software but is more likely to be spam. | ||||
| STIG | Date | |||
| Microsoft Exchange 2016 Edge Transport Server Security Technical Implementation Guide | 2024-12-06 | |||
Related Frameworks
1 mapping across 3 frameworks
Related Frameworks
SCF0 mappings
No source states a mapping between these directly.
Also reachable in 3 hops (1) derived by us, not asserted by any source
Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.
- DISA STIG Benchmark (XCCDF)V2R6intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
- SCF Secure Traceability Relationship Mapping (STRM)2026.2equal to
NIST 800-530 mappings
No source states a mapping between these directly.
Also reachable in 2 hops (1) derived by us, not asserted by any source
Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.
- DISA STIG Benchmark (XCCDF)V2R6intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
CCI1 mapping
CCI-001308
1.00
- DISA STIG Benchmark (XCCDF)V2R6intersects(normalised)
Details
Check Text (C-221242r1040907_chk)
If this server is in a SIPR Enclave, this requirement is Not Applicable.
Note: If third-party anti-spam product is being used, the anti-spam product must be configured to meet the requirement.
Open the Exchange Management Shell and enter the following command:
Get-SenderIdConfig | Select Name, Identity, SpoofedDomainAction
If the value of "SpoofedDomainAction" is not set to "Reject", this is a finding.
Fix Text (F-22946r411853_fix)
Open the Exchange Management Shell and enter the following command:
Set-SenderIdConfig -SpoofedDomainAction Reject