17.3.6.
Using Approved Cryptographic Protocols
17.3.6.R.01.
Rationale
If a product implementing an Approved Cryptographic Protocol has been inappropriately configured, it is possible that relatively weak
cryptographic algorithms or implementations could be inadvertently selected. In combination with an assumed level of security confidence,
this can represent a significant level of security risk.
17.3.6.R.02.
Rationale
When configuring unevaluated products that implement an Approved Cryptographic Protocol, agencies can ensure that only the Approved
Cryptographic Algorithm can be used by disabling the unapproved algorithms within the products (which is preferred). Alternatively a policy
can be put in place to advise system users not to use the non-approved algorithms.
17.3.6.R.03.
Rationale
While many Approved Cryptographic Protocols support authentication, agencies should be aware that these authentication mechanisms are not
foolproof. To be effective, these mechanisms MUST be securely implemented and protected.
This can be achieved by:
providing an assurance of private key protection;
ensuring the correct management of certificate authentication processes including certificate revocation checking; and
using a legitimate identity registration scheme.
17.3.6.C.01.
ControlSystem Classification(s): All Classifications; Compliance: MUST
[CID:2520]
Agencies using a product that implements an Approved Cryptographic Protocol MUST ensure that only Approved Cryptographic Protocols can
be used.
17.4. Transport Layer Security
Objective
17.4.1. Transport Layer Security is implemented correctly as an approved protocol.
Context
Scope
17.4.2. This section covers the conditions under which TLS can be used as an approved cryptographic protocols. Additionally, as File Transfer Protocol over
SSL is built on SSL/TLS, it is also considered within scope.
17.4.3. When using a product that implements TLS, requirements for using approved cryptographic protocols will also need to be referenced in theSection
17.3 - Approved Cryptographic Protocols.
17.4.4. Further information on handling TLS traffic through gateways can be found inSection 14.3 - Web Applications.
Background
17.4.5. Secure Sockets Layer (SSL), and Transport Layer Security (TLS) are cryptographic protocols designed to provide communication security when
using the Internet. They use X.509 certificates and asymmetric cryptography for authentication purposes. This generates a session key. This session
key is then used to encrypt data between the parties.
17.4.6. Encryption with the session key provides data and message confidentiality, and message authentication codes for message integrity.
17.4.7. Several versions of the SSL and TLS protocols are in widespread use in applications such as web browsing, electronic mail, Internet faxing, instant
messaging, and voice-over-IP (VoIP).
17.4.8. Although common usage has been to use the terms TLS and SSL interchangeably, they are distinct protocols.
17.4.9. TLS is an Internet Engineering Task Force (IETF) protocol, first defined in 1999, updated in RFC 5246 (August 2008) and RFC 6176 (March 2011). It is
based on the earlier SSL specifications (1994, 1995, 1996) developed by Netscape Communications for adding the HTTPS protocol to their Navigator
web browser. A draft of TLS 1.3 was released in October 2014, with a definitive version issued in 2018.
17.4.10. Microsoft announced in October 2014 that that it will disable Secure Sockets Layer (SSL) 3.0 support in its Internet Explorer browser and in its Online
Services, from Dec. 1, 2014.
SSL 3.0 Vulnerability
17.4.11. A design vulnerability has been found in the way SSL 3.0 handles block cipher mode padding. The Padding Oracle On Downgraded Legacy Encryption
(POODLE) attack demonstrates how an attacker can exploit this vulnerability to decrypt and extract information from an encrypted transaction.
17.4.12. The POODLE attack demonstrates this vulnerability using web browsers and web servers, which is one of the most likely exploitation scenarios. All
systems and applications utilizing the Secure Socket Layer (SSL) 3.0 with cipher-block chaining (CBC) mode ciphers may be vulnerable.
SSL Superseded
17.4.13. SSL is now superseded by TLS, with the latest version being TLS 1.3 which was released in August 2018. This is largely because of security flaws in the
older SSL protocols.
17.4.14. Accordingly SSL is no longer an approved cryptographic protocol and it SHOULD be replaced by TLS.
References
17.4.15. Further information on SSL and TLS can be found at:
Reference
243
Title
Publisher
Source
Version_3.5__January-2022
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents