OpenControls Logo

STIG Viewer

STIGViewer Support

Exchange internal Send connectors must use domain security (mutual authentication Transport Layer Security).

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-221218EX16-ED-000170SV-221218r1043178_ruleCCI-001184medium
Description
The Simple Mail Transfer Protocol (SMTP) connector is used by Exchange to send and receive messages from server to server. Several controls work together to provide security between internal servers. This setting controls the authentication method used for communications between servers. With this feature enabled, only servers capable of supporting domain authentication will be able to send and receive mail within the domain. The use of secure communication prevents eavesdroppers from reading or modifying communications between mail clients and servers. While sensitive message bodies should be encrypted by the sender at the client, requiring a secure connection from server to server adds protection by encrypting the sender and recipient information that cannot be encrypted by the sender. Individually, channel security and encryption can be compromised by attackers. Used together, email becomes a more difficult target, and security is heightened. Failure to enable this feature gives eavesdroppers an opportunity to read or modify messages between servers.
STIGDate
Microsoft Exchange 2016 Edge Transport Server Security Technical Implementation Guide2024-12-06

Related Frameworks

1 mapping across 4 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.

NET-09Session Integrity
1.00
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (30) 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.

AC-17(2)Protection of Confidentiality and Integrity Using Encryption
1.00
AU-10(1)Association of Identities
1.00
AU-10(2)Validate Binding of Information Producer Identity
1.00
AU-9(3)Cryptographic Protection
1.00
CM-14Signed Components
1.00
CM-5(3)Signed Components
1.00
CM-6Configuration Settings
1.00
CM-7Least Functionality
1.00
IA-2(1)Multi-factor Authentication to Privileged Accounts
1.00
IA-2(12)Acceptance of PIV Credentials
1.00

+20 more (top 10 by confidence shown)

NIST 800-1710 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.

3.13.15
1.00
CCI1 mapping
CCI-001184
1.00

Details

Check Text (C-221218r1043178_chk)

Open the Exchange Management Shell and enter the following command: Get-SendConnector | Select Name, Identity, DomainSecureEnabled, DNSRoutingEnabled, RequireTLS, TlsAuthLevel For each send connector: If the send connector does not use a smarthost and the value of "DomainSecureEnabled" is not set to "True", this is a finding. If the send connector does use a smarthost, "DomainSecureEnabled" will be set to "False". If the send connector does use a smarthost "DNSRoutingEnabled", "RequireTLS", and "TlsAuthLevel" must be set. If the send connector using a smart host has a value for “DNSRoutingEnabled” that is not set to “False”, this is a finding. If the send connector using a smarthost has a value for “RequireTLS” that is not set to “True”, this is a finding. If the send connector using a smarthost has a value for “TlsAuthLevel” that is not set to “DomainValidation”, this is a finding.

Fix Text (F-22922r811173_fix)

Open the Exchange Management Shell and enter the following command: Set-SendConnector <'IdentityName'> -DomainSecureEnabled $true Note: The <IdentityName> value must be in single quotes. Repeat the procedures for each send connector. The following commands can be executed if smarthosts are used: Set-SendConnector <'IdentityName'> -RequireTLS $true -DNSRoutingEnabled $False -TlsAuthLevel $DomainValidation