17.2.19.C.01. ControlSystem Classification(s): All Classifications; Compliance: MUST [CID:2134] Agencies using DH, for the approved use of agreeing on encryption session keys, MUST use a modulus of at least 3072 bits. 17.2.20. Equipment using DH 17.2.20.R.01. Rationale If a network device is NOT able to support the required cryptographic protocol, algorithm and key length, the system will be at risk of a cryptographic compromise. In such cases, the longest feasible key length must be implemented and the device scheduled for replacement as a matter of urgency. 17.2.20.C.01. ControlSystem Classification(s): All Classifications; Compliance: MUST [CID:2137] Devices which are NOT capable of implementing required key lengths MUST be reconfigured with the longest feasible key length as a matter of urgency. 17.2.20.C.02. ControlSystem Classification(s): All Classifications; Compliance: MUST [CID:2138] Devices which are NOT capable of implementing required key lengths MUST be scheduled for replacement as a matter of urgency. 17.2.21. Using DSA (for legacy use only) 17.2.21.R.01. Rationale A modulus of at least 1024 bits for DSA is considered good practice by the cryptographic community. 17.2.21.C.01. ControlSystem Classification(s): All Classifications; Compliance: MUST [CID:7189] Agencies using DSA, for the approved use of digital signatures, MUST use a modulus of at least 1024 bits. 17.2.22. Using ECDH 17.2.22.R.01. Rationale A field/key size of at least 384 bits for ECDH is now considered good practice by the cryptographic community. 17.2.22.C.01. ControlSystem Classification(s): All Classifications; Compliance: MUST [CID:2144] Agencies using ECDH, for the approved use of agreeing on encryption session keys, MUST implement the curve P-384 (prime moduli). 17.2.22.C.02. ControlSystem Classification(s): All Classifications; Compliance: MUST [CID:2145] All VPN’s using an ECDH key length less than 384 MUST replace all Pre-Shared Keys with keys of at least 384 bits, as soon as possible. 17.2.23. Using ECDSA 17.2.23.R.01. Rationale An equivalent symmetric key security strength of at least 160 bits for ECDSA is considered good practice by the cryptographic community. Not all legacy systems support a modulus of this length, in which case significant risk is being carried. 17.2.23.C.01. ControlSystem Classification(s): All Classifications; Compliance: MUST [CID:2148] Agencies using ECDSA, for the approved use of digital signatures, MUST implement the curve P-384 (prime moduli). 17.2.24. Using RSA 17.2.24.R.01. Rationale A modulus of at least 3072 bits for RSA is considered good practice by the cryptographic community. 17.2.24.C.01. ControlSystem Classification(s): All Classifications; Compliance: MUST [CID:2151] Agencies using RSA, for the approved use of digital signatures and passing encryption session keys or similar keys, MUST use a modulus of at least 3072 bits. 17.2.24.C.02. ControlSystem Classification(s): All Classifications; Compliance: MUST [CID:2152] Agencies using RSA, for the approved use of digital signatures and passing encryption session keys or similar keys, MUST ensure that the public keys used for passing encrypted session keys are different to the keys used for digital signatures. 17.2.24.C.03. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:7181] Agencies using RSA, for the approved use of digital signatures and passing encryption session keys or similar keys, SHOULD use a modulus of at least 4096 bits. 17.2.25. Public key infrastructure using RSA 17.2.25.R.01. Rationale A modulus of at least 2048 bits for RSA is considered good practice by the cryptographic community for use within X.509 based Public Key Infrastructure (PKI) systems. 17.2.25.C.01. ControlSystem Classification(s): All Classifications; Compliance: MUST [CID:7186] Agencies using RSA keys within internet X.509 Public Key Infrastructure certificates MUST use a modulus of at least 2048 bits. 17.2.26. Approved hashing algorithms 17.2.26.R.01. Rationale Recent research conducted by cryptographic community suggests that SHA-1 may be susceptible to collision attacks. While no practical 241 Version_3.5__January-2022

Select target paragraph3

Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents