Reliance on HTTP instead of HTTPS

Explicitly require HTTPS or another mechanism that ensures that communication is encrypted [REF-1464].

Avoid using "mixed content," i.e., serving a web page over HTTPS in which the page includes elements that use "http:" URLs [REF-1466] [REF-1467]. This is often done for images or other resources that do not seem to have privacy or security implications.

Perform "HTTPS forcing," that is, redirecting HTTP requests to HTTPS.

If the product supports multiple protocols, ensure that encrypted protocols (such as HTTPS) are required, and remove any unencrypted protocols (such as HTTP).