STIGhubSTIGhub
STIGsRMF ControlsCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 3 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to Microsoft Exchange 2016 Edge Transport Server Security Technical Implementation Guide

V-221225

CAT III (Low)

Exchange Send connectors must be clearly named.

Rule ID

SV-221225r961155_rule

STIG

Microsoft Exchange 2016 Edge Transport Server Security Technical Implementation Guide

Version

V2R6

CCIs

CCI-001095

Discussion

For Send 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-SendConnector | Select Name, Identity

Review the naming for connectors. 

For each send connector, 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-SendConnector -Name <'NewName'> -Identity <'IdentityName'>

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

Repeat the procedure for each send connector.