Receive Connector timeout must be limited.

From Exchange 2010 Hub Transport Server STIG

Associated with IA controls: ECSC-1

SV-43984r1_rule Receive Connector timeout must be limited.

Vulnerability discussion

Email system availability depends in part on best practices strategies for setting tuning. This configuration controls the number of idle minutes before the connection is dropped. It works in conjunction with the Maximum Inbound Connections Count setting. Connections, once established, may incur delays in message transfer. If the timeout period is too long, there is risk that idle connections may be maintained for unnecessarily long time periods, preventing new connections from being established.

Check content

Obtain the Email Domain Security Plan (EDSP) and locate the 'Connection Timeout' value. Open the Exchange Management Shell and enter the following command: Get-ReceiveConnector | Select Name, Identity, ConnectionTimeout If the value of 'ConnectionTimeout' is set to 00:10:00, this is not a finding. If 'ConnectionTimeout' is set to other than 00:10:00, and has signoff and risk acceptance in the EDSP, this is not a finding.

Fix text

Open the Exchange Management Shell and enter the following command: Set-ReceiveConnector -Identity <'ReceiveConnector'> -ConnectionTimeout 00:10:00 or other value as identified by the EDSP.

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.