STIGhubSTIGhub
STIGsRMF ControlsCompare
STIGhub— A free STIG search and compliance tool·STIGs updated 3 days ago
Powered by Pylon·Privacy·Terms·© 2026 Beacon Cloud Solutions, Inc.
← Back to Microsoft Exchange 2016 Edge Transport Server Security Technical Implementation Guide

V-221227

CAT III (Low)

Exchange Receive connectors must be clearly named.

Rule ID

SV-221227r961155_rule

STIG

Microsoft Exchange 2016 Edge Transport Server Security Technical Implementation Guide

Version

V2R6

CCIs

CCI-001095

Discussion

For receive connectors, unclear naming as to direction and purpose increases risk that messages may not flow as intended, troubleshooting efforts may be impaired, or incorrect assumptions may be made about the completeness of the configuration. Collectively, connectors should account for all connections required for the overall email topology design. Simple Mail Transfer Protocol (SMTP) connectors, when listed, must name purpose and direction clearly, and their counterparts on servers to which they connect should be recognizable as their partners.

Check Content

Open the Exchange Management Shell and enter the following command:

Get-ReceiveConnector | Select Name, Identity

For each Receive connector, review the naming for connectors.

If the connectors are not clearly named for purpose and direction, this is a finding.

Fix Text

Open the Exchange Management Shell and enter the following command:

Set-ReceiveConnector -Name <'NewName'> -Identity <'IdentityName'>

Note: Both the <NewName> and <IdentityName> value must be in single quotes.

Repeat the procedure for each receive connector.