Using Authenticated RPC

While previous versions of Microsoft RPC depended on the security built into the named-pipe transport, this version also implements the transport-independent security functions from OSF-DCE RPC, using the Windows NT Security Service as the default security provider. This higher-level security enables servers to filter client requests based on an authenticated identity associated with each request.