UCF STIG Viewer Logo
Changes are coming to https://stigviewer.com. Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey

The Terminal Server does not require secure RPC communication (Terminal Server Role).


Overview

Finding ID Version Rule ID IA Controls Severity
V-4447 5.103 SV-16952r1_rule ECSC-1 Medium
Description
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.
STIG Date
Windows 2008 Member Server Security Technical Implementation Guide 2015-06-03

Details

Check Text ( C-1934r1_chk )
If the following registry value doesn’t exist or its value is not set to 1, then this is a finding:

Registry Hive: HKEY_LOCAL_MACHINE
Subkey: \Software\Policies\Microsoft\Windows NT\Terminal Services\
Value Name: fEncryptRPCTraffic
Type: REG_DWORD
Value: 1
Fix Text (F-16022r1_fix)
2008 - Configure the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Terminal Services -> Terminal Server -> Security “Require secure RPC communication” will be set to “Enabled”.