The protocol which is the industry standard for securely transmitting data across the Internet is called HTTPS, which stands for “Hypertext Transfer Protocol Secure,” and is used to create secure web-pages. It works in tandem with and operates the same as any other site created by HTTP, as the same language is used to create the web content. The sole difference is that when data is sent through the Internet it is all encrypted providing it with a level of security.
If you are on a site that begins with the prefix https:// web server is prepared to establish a secure communication path for your transmission. A completely different port is used, number 443, which keeps non-secure data separate from secure data.
The connection path it follows a sequence something like this:
- Your browser verifies the authenticity of the server by inspecting its certificate. These certificates can only be issued by particular governing bodies which charge a fee to the companies who make use of them.
- Once your browser has confirmed the certificate it then locates the encryption types offered by the server.
- Once the encryption type is agreed upon between both the server and your browser they exchange unique encryption keys which only they know (the server and the browser) and use them to encrypt the data.
- Using the keys the browser can then encrypt the data and transmit to the server where it uses the same key to decode the transmission and receive exactly the same thing a person sees (or enters) on their screen.
The process as described is much more complex than communications conducted by simple HTTP. Because of the extra overhead this creates the speed of transmission is generally recognizably slower – as is the decryption on the server that receives the information. Because HTTPS only picks up encrypted data should a packet sniffer steal any packets in transit the data hijacker receives will be encrypted and of no use (or sense) to the person attacking the transmission.




