Internal Send Connectors must require encryption.

From Exchange 2010 Edge Transport Server STIG

SV-44012r3_rule Internal Send Connectors must require encryption.

Vulnerability discussion

The Simple Mail Transfer Protocol (SMTP) connector is used by Exchange to send and receive messages from server to server. There are several controls that work together to provide security between internal servers. This setting controls the encryption method used for communications between servers. With this feature enabled, only servers capable of supporting Transport Layer Security (TLS) 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.

Check content

Open the Exchange Management Shell and enter the following command: Get-SendConnector | Select Name, Identity, TlsDomain If the value of 'TlsDomain' is not set to the value of the internal <'SMTP Domain'>, this is a finding.

Fix text

Open the Exchange Management Shell and enter the following command: Set-SendConnector -Identity <'SendConnector'> -TlsDomain <'SMTP Domain'> <'SMTP Domain'> Note: 'SMTP Domain' is the internal SMTP domain within the organization.

Pro Tips

Lavender hyperlinks in small type off to the right (of CSS class id, if you view the page source) point to globally unique URIs for each document and item. Copy the link location and paste anywhere you need to talk unambiguously about these things.

You can obtain data about documents and items in other formats. Simply provide an HTTP header Accept: text/turtle or Accept: application/rdf+xml.