The product provides or relies on use of HTTP communications when HTTPS is available.
Because HTTP communications are not encrypted, HTTP is subject to various attacks against confidentiality, integrity, and authenticity. However, unlike many other protocols, HTTPS is widely available as a more secure alternative, because it uses encryption.
Threat Mapped score: 0.0
Industry: Finiancial
Threat priority: Unclassified
N/A
N/A
| Phase | Note |
|---|---|
| Architecture and Design | The product might be designed in a way that assumes that HTTP will be used, e.g., by excluding considerations of encrypted communications between client and server. |
| Requirements | Product requirements might not include encrypted communications, which could make it easier for designers and developers to choose HTTP. |
| Implementation | Developers might choose to use unencrypted protocols such as HTTP because they would not require development of additional mechanisms to support encryption, e.g., key or certificate management. |
| Implementation | When generating content that references web sites such as email messages, ensure that the https:// prefix is included. If a domain name is presented without such a prefix, then clients might automatically treat the link as if it had an "http" prefix. For example, referencing a domain like "mysite.example.com" could cause it to be treated like "http://mysite.example.com", thereby sending unencrypted HTTP requests. |
| Operation | Designers might assume that the responsibility for encrypted communications might belong to operators and/or network administrators. |
N/A