Transport security mechanisms in WCF depend on the binding and subsequent transport being used. Below lists the transport securities in WCF pre-defined bindings, including default security mode and clientCredentialType I mentioned in last topic which is the key conception of security mechanism in WCF. On common use, the pre-defined bindings WCF has are suitable for almost all the usage senario, so it's important to understand them first.

1. BasicHttpBinding

By default, the BasicHttpBindingclass does not provide security. This binding is designed for interoperability with Web service providers that do not implement security. However, security can be switched on by setting the Mode property to any value except None. To enable transport security, set the property to Transport. The BasicHttpBinding class is primarily used to interoperate with existing Web services and a great number of those services are hosted by Internet Information Services (IIS). Consequently, the transport security for this binding is designed for seamless interoperation with IIS sites. This is done by setting the security mode to Transport and then setting the client credential type. The credential type values correspond to IIS directory security mechanisms.

2. WSHttpBinding

The WSHttpBinding class is designed for interoperation with services that implement WS-* specifications. The transport security for this binding is HTTPS. To create an WCF application that uses SSL, use IIS to host the application. Alternatively, if you are creating a self-hosted application, use the HttpCfg.exe tool to bind an X.509 certificate to a specific port on a computer. The port number is specified as part of the WCF application as an endpoint address. For client authentication, set the ClientCredentialType property of the HttpTransport Security class to one of the HttpClientCredentialType enumeration values.

3. WSDualHttpBinding

This binding does not provide transport level security, only message level security.

4. NetTcpBinding

The NetTcpBinding class uses the TCP for message transport. Security for the transport mode is provided by implementing TLS over TCP. The TLS implementation is provided by the operating system.

5. NetNamedPipeBinding

The NetNamedPipeBinding class is designed for efficient intra-machine communication. That is, for processes running on the same computer, although named-pipe channels can be created between two computers on the same network. This binding provides only transport-level security. When creating applications using this binding, the endpoint addresses must include "net.pipe" as the protocol of the endpoint address.

6. WSFederationHttpBinding

When using transport security, this binding uses SSL over HTTP, known as HTTPS with an issued token

7. NetPeerTcpBinding

The NetPeerTcpBinding is a secure transport that is designed for efficient communication using the peer-to-peer networking feature. As indicated by the name of the class and binding, TCP is the protocol. When the security mode is set to Transport, the binding implements TLS over TCP.