TLS and MTLS protocols provide encrypted communications and endpoint authentication on the Internet. Office Communications Server uses these two protocols to create the network of trusted servers and to ensure that all communications over that network are encrypted. All SIP communications between servers occur over MTLS. SIP communications from client to server occur over TLS.

TLS enables users, through their client software, to authenticate the Office Communications Server 2007 R2 servers to which they connect. On a TLS connection, the client requests a valid certificate from the server. To be valid, the certificate must have been issued by a CA that is also trusted by the client and the DNS name of the server must match the DNS name on the certificate. If the certificate is valid, the client trusts the server and opens the connection. The resulting connection is trusted and from that point is not challenged by other trusted servers or clients. Within this context, Secure Sockets Layer (SSL) as used with Web services can be associated as TLS-based.

Server-to-server connections rely on mutual TLS (MTLS) for mutual authentication. On an MTLS connection, the server originating a message and the server receiving it exchange certificates from a mutually trusted CA. The certificates prove the identity of each server to the other. In Office Communications Server 2007 R2 deployments, certificates issued by the enterprise CA are automatically considered valid by all internal clients and servers. In federated scenarios, the issuing CA must be trusted by both federated partners. Each partner can use a different CA, if desired, so long as that CA is also trusted by the other partner. This trust is most easily accomplished by the Edge Servers having the partner’s root CA certificate in their trusted root CAs, or by use of a third-party CA that is trusted by both parties.

TLS and MTLS help prevent both eavesdropping and man-in-the middle attacks. In a man-in-the-middle attack, the attacker reroutes communications between two network entities through the attacker’s computer without the knowledge of either party. TLS and secure server lists mitigate the risk of a man-in-the middle attack partially on the application layer, but ultimately the networking infrastructure (in this case corporate DNS) must be secured according to best practices. Office Communications Server assumes that the DNS server is trusted in the same way that domain controllers and global catalogs are trusted.

The following figure shows at a high level how Office Communications Server uses MTLS to create a network of trusted servers.

Figure 1. Trusted connections in an Office Communications Server 2007 R2 network