APPNET0060 - Remoting Services HTTP channels must utilize authentication and encryption - applications


Note: Microsoft recommends using the Windows Communication Framework (WCF) rather than using .Net remoting. New development projects should refrain from using .Net remoting capabilities whenever possible.

.NET remoting provides the capability to build widely distributed applications. The application components may reside all on one computer or they may be spread out across the enclave. .NET client applications can make remoting calls to use objects in other processes on the same computer or on any other computer that is reachable over the network. .NET remoting can also be used to communicate with other application domains within the same process. Remoting is achieved via the exposure of endpoints that can be used to establish remote connectivity.

Normally when application code attempts to access a protected resource, a stack walk is performed to ensure that all stack frames have permission to access the resource. However, with .Net 4.0, when a call is made on a remote object, this stack walk is not performed across the remoting boundary. The .Net remoting infrastructure requires FullTrust permission to execute on either the client or the server.

Due to the fact that FullTrust permission is required, Remoting endpoints should be authenticated and encrypted in order to protect the system and the data.

Microsoft provides 3 different 'channels' that are used for remoting. They are HTTP, TCP and IPC.

Any unauthorized use of a remoting application provides unauthorized access with FullTrust permissions to the system. This can potentially result in a loss of system integrity or confidentiality.

NOTE: Nessus has provided the target output to assist in reviewing the benchmark to ensure target compliance.


Ensure encryption and message integrity are used for HTTP remoting channels.

The HTTP Channel only supports encryption and message integrity when the remote object is hosted in Internet Information Services (IIS) using TLS.

HTTP channels are protected via TLS (HTTPS).
<channel ref='http server' port='443'/>

Change the channel ref parameter to utilize a TLS port and leverage TLS on the remote IIS server.

See Also

Item Details


References: 800-53|SC-23, CAT|II, CCI|CCI-001184, Rule-ID|SV-225228r615940_rule, STIG-ID|APPNET0060, STIG-Legacy|SV-7453, STIG-Legacy|V-7070, Vuln-ID|V-225228

Plugin: Windows

Control ID: 26c4b0641f306ba6827d242e107ff762cd7570fc4563097a600174893e79c41d