Details

This control is used to limit the servers that may use this server as a relay. If a Simple Mail Transport Protocol (SMTP) sender does not have a direct connection to the Internet (for example, an application that produces reports to be emailed), it will need to use an SMTP Receive connector that does have a path to the Internet (for example, a local email server) as a relay.

SMTP relay functions must be protected so third parties are not able to hijack a relay service for their own purposes. Most commonly, relay hijacking is done by spammers to disguise the source of their messages and may also be used to cover the source of more destructive attacks.

Relays can be restricted in one of three ways: by blocking relays (restrict to a blank list of servers); by restricting use to lists of valid servers; or by restricting use to servers that can authenticate. Because authenticated connections are the most secure for SMTP Receive connectors, it is recommended that relays allow only servers that can authenticate.

Solution

Open the Exchange Management Shell and enter the following command:

Set-ReceiveConnector -Identity <'IdentityName'> -PermissionGroups ‘valid user group(s)’

Note: The value and user group(s) must be in single quotes.

Example for user groups only: ‘ExchangeServers, ExchangeUsers’

Repeat the procedures for each Receive connector.

This is an Example only: Set-ReceiveConnector -Identity <'IdentityName'> -PermissionGroups ‘ExchangeUsers’

Supportive Information

The following resource is also helpful.

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

This security hardening control applies to the following category of controls within NIST 800-53: System and Information Integrity.This control applies to the following type of system Windows.

References

• 800-53|SI-8(2)
• CAT|II
• CCI|CCI-001308
• Rule-ID|SV-221245r612603_rule
• STIG-ID|EX16-ED-000490
• STIG-Legacy|SV-95281
• STIG-Legacy|V-80571
• Vuln-ID|V-221245

Source

• Tenable.com/audits