The Terminal Server does not require secure RPC communication.

From Windows 2003 Member Server Security Technical Implementation Guide

Part of TS/RDS - Secure RPC Connection.

Associated with IA controls: ECSC-1

SV-29108r1_rule The Terminal Server does not require secure RPC communication.

Vulnerability discussion

Allowing unsecure RPC communication exposes the server to man in the middle attacks and data disclosure attacks. A man in the middle attack occurs when an intruder captures packets between a client and server and modifies them before allowing the packets to be exchanged. Usually the attacker will modify the information in the packets in an attempt to cause either the client or server to reveal sensitive information.

Check content

Fix text

Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Terminal Services -> Encryption and Security -> RPC Security Policy “Secure Server (Require Security)” to “Enabled”.

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.

Powered by sagemincer