HyperText Transfer Protocol (HTTP)
HTTP header
response and request formats are defined in an HTTP header
HTTP payload
usually used to serve HTML web pages, which are plain text files with coded tags (HyperText Markup Language) describing how the page should be formatted
HTTP (POST)
features a forms mechanism (POST) whereby a user can submit data from the client to the server. HTTP is a stateless protocol; this means that the server preserves no information about the client during a session
web servers
Secure Sockets Layer (SSL)
developed by Netscape in the 1990s to address the problems with the lack of security in HTTP. SSL proved very popular with the industry
Transport Layer Security (TLS)
developed from SSL and ratified as a standard by IETF. SSL/TLS works as a layer between the application and transport layers of the TCP/IP stack. It is usually used to encrypt TCP connections. It is typically used with the HTTP application (referred to as HTTPS or HTTP Over SSL or HTTP Secure) but can also be used to secure other TCP application protocols, such as Telnet, FTP, NNTP, SMTP, or LDAP
HTTPS
to implement HTTPS, a server is assigned a digital certificate signed by some trusted certificate authority (CA). The certificate proves the identity of the server (assuming that the client trusts the Certificate Authority). The server uses the digital certificate and the SSL/TLS protocol to encrypt communications between it and the client. This means that the communications cannot be read or changed by a third party
SSL/TLS Handshake sub-protocol
asymmetric ciphers (key exchange and authentication)
RSA, DSA/DSS, and Diffie-Hellmann
symmetric ciphers (confidentiality)
RC4, RC2, DES, 3DES, IDEA, AES
Hashed Message Authentication Code (HMAC) function
MD5 or SHA
SSL
- not interoperable like TLS
Transport Layer Security
- not interoperable like SSL
SSL/TLS accelerator
hardware device with a specialist chipset—Application Specific Integrated Circuit (ASIC)—dedicated to performing these calculations
SSL decryptor, inspector, or interceptor
subscription services
File Transfer Protocol (FTP)
Trivial File Transfer Protocol (TFTP)
SSH FTP (SFTP)
addresses the privacy and integrity issues of FTP by encrypting the authentication and data transfer between client and server. In SFTP, a secure link is created between the client and server using Secure Shell (SSH) over TCP port 22. Ordinary FTP commands and data transfer can then be sent over the secure link without risk of eavesdropping or Man-in-the-Middle attacks. This solution requires an SSH server that supports SFTP and SFTP client software
two means of securing FTP is to use the connection security protocol SSL/TLS:
Simple Mail Transfer Protocol (SMTP)
specifies how mail is delivered from one system to another. It is a relatively straightforward protocol that makes the connection from the sender’s server to that of the recipient and then transfers the message. The SMTP server of the sender discovers the IP address of the recipient SMTP server using the domain name part of the email address. The SMTP server for the domain is registered in DNS using a Mail Exchanger (MX) record
SMTP configurations use the following ports and secure services
Post Office Protocol v3 (POP3)