Detections
Analytics

EX16-MB-000220 - Exchange internal Receive connectors must require encryption.

Warning! Audit Deprecated

This audit has been deprecated and will be removed in a future update.

View Next Audit Version

Information

The Simple Mail Transfer Protocol (SMTP) Receive connector is used by Exchange to send and receive messages from server to server using SMTP protocol. This setting controls the encryption strength used for client connections to the SMTP Receive connector. With this feature enabled, only clients capable of supporting secure communications will be able to send mail using this SMTP server. Where secure channels are required, encryption can also be selected.

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 the client to the server adds protection by encrypting the sender and recipient information that cannot be encrypted by the sender.

Individually, channel security and encryption have been 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 the client and server.
Multiple values can be separated by commas, but some values have dependencies and exclusions. AuthMechanism may include other mechanisms as long as the 'Tls' is identified.
- Only use the value 'None' by itself.
- The value 'BasicAuthRequireTLS' requires the values 'BasicAuth' and 'Tls'.
- The only other value that can be used with ExternalAuthoritative is 'Tls'.
- The value 'Tls' is required when the value of the RequireTLS parameter is '$true'.
- The value 'ExternalAuthoritative' requires the value of the PermissionGroups parameter be set to 'ExchangeServers'.

Solution

Open the Exchange Management Shell and enter the following command:

Set-ReceiveConnector -Identity <'IdentityName'> -AuthMechanism 'Tls'

Note: The <IdentityName> value must be in single quotes.

Repeat the procedures for each Receive connector.

See Also

https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_MS_Exchange_2016_Y22M07_STIG.zip

Item Details

References: CAT|II, CCI|CCI-001184, Rule-ID|SV-228375r612748_rule, STIG-ID|EX16-MB-000220, STIG-Legacy|SV-95375, STIG-Legacy|V-80665, Vuln-ID|V-228375

Plugin: Windows

Control ID: 95c3b8bb5b3caa79a61362ccd0dc0c3063d7a8bb93ff4e52ce555574feeeedef