Transport Layer Security

Transport Layer Security (TLS) is a protocol that ensures privacy between communicating applications and their users on the Internet. When a server and client communicate, TLS ensures that no third party may eavesdrop or tamper with any message. TLSis the successor to the Secure Sockets Layer (SSL).

TLS is composed of two layers: the TLS Record Protocol and the TLS Handshake Protocol. The TLS Record Protocol provides connection security with some encryption method such as the Data Encryption Standard (DES). The TLS Record Protocol can also be used without encryption. The TLS Handshake Protocol allows the server and client to authenticate each other and to negotiate an encryption algorithm and cryptographic keys before data is exchanged.

The TLS protocol is based on Netscape's SSL 3.0 protocol; however, TLS and SSL are not interoperable. The TLS protocol does contain a mechanism that allows TLS implementation to back down to SSL 3.0. The most recent browser versions support TLS. The TLS Working Group, established in 1996, continues to work on the TLS protocol and related applications.

If a company is asking you to set this up and you have to ask what it is. Then you should really seek outside help with this and not try to do it on your own your first time out.

While seans description was helpful in describing the basic function of TLS versus SSL.

Basically what they want is secure communications between your site and theirs. If you have never done this before, then there is a lot of room for error.

If you are still hell bent on doing it your self, You need to determine where your getting to set this up.

Generally this happens between fwl's via a tunnel. It is the easiest method. Basically you a creating a secure connection (or tunnel) between 2 points. Any data that travels between those 2 points are tunneled/secured.

SSL on the other hand is a socket based security method, where it secures the individual connection to the server.

This sounds like an element of VPN, common to some wireless applications. If you are unsure of how to setup any security element, do not be intimidated. Contact a reputable consultant or vendor. They WILL provide you with the best information, and quick education. They may be able to provide alternatives as well.

Meanwhile:
Microsoft's "How-It-Works" overview:
http://www.microsoft.com/windows2000/techinfo/howitworks/security/comsec.asp

MS's SSL/TLS setup documentation for developers:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q288897

IETF's TLS Charter:
http://www.ietf.org/html.charters/tls-charter.html

Netscape's "How-SSL-Works" primer:
http://developer.netscape.com/tech/security/ssl/howitworks.html

Hope this helps...