What are the risks associated with HTTP? How can we resolve these risks by using HTTPS?
HTTP sends information over the network exactly as it is. It does not scramble the data to be transmitted, which leaves it vulnerable to attacks from hackers. This makes it unsuitable for transmitting sensitive details like banking credentials or passwords.
These risks can be resolved by using HTTPS, which encrypts the data before transmission. This ensures that the information is scrambled and secure during transfer. At the receiver end, HTTPS decrypts the data to recover the original message. Additionally, HTTPS-based websites require an SSL Digital Certificate to facilitate this secure communication.
Explanation
The answer is derived directly from section 12.5 of the provided text. It identifies the primary risk of HTTP as sending data 'as it is' without scrambling, leading to vulnerability to hackers. It then explains the resolution provided by HTTPS: encryption before transmission and decryption at the receiver's end, along with the requirement of an SSL Digital Certificate.