17.8.13.C.01.
ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:2853]
Agencies SHOULD use a security association lifetime of four hours or 14400 seconds, or less.
17.8.14. HMAC algorithms
17.8.14.R.01. Rationale
MD5 and SHA-1 are no longer approved Cryptographic Protocols. The approved algorithms that can be used with HMAC are HMAC-SHA256,
HMAC-SHA384 and HMAC-SHA512.
17.8.14.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:2856]
Agencies SHOULD use HMAC-SHA256, HMAC-SHA384 or HMAC-SHA512 as the HMAC algorithm.
17.8.15. DH groups
17.8.15.R.01. Rationale
Using a larger DH group provides more entropy for the key exchange.
17.8.15.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:2859]
Agencies SHOULD use the largest modulus size available for the DH exchange.
17.8.16. Perfect Forward Secrecy
17.8.16.R.01. Rationale
Using Perfect Forward Secrecy reduces the impact of the compromise of a security association.
17.8.16.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:2862]
Agencies SHOULD use Perfect Forward Secrecy for IPSec connections.
17.8.17. IKE Extended Authentication
17.8.17.R.01. Rationale
XAUTH using IKEv1 has documented vulnerabilities associated with its use.
17.8.17.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:2865]
Agencies SHOULD disable the use of XAUTH for IPSec connections using IKEv1.
17.9. Key Management
Objective
17.9.1. Cryptographic keying material is protected by key management procedures.
Context
Scope
17.9.2. This section covers information relating to the general management of cryptographic system material. Because there is a wide variety of
cryptographic systems and technologies available, and there are varied security risks for each, detailed key management guidance is not provided in
this manual.
17.9.3. If HGCP or HGCE is being used, agencies are advised to consult the respective NZCSI national standards for the respective equipment.
17.9.4. In a cloud enviroment it is possible to outsource the control of cryptographic key to the cloud service provider, Hold Your Own Keys (HYOK) and Bring
Your Own Keys (BYOK). It is important to note that there is little distinction between HYOK and BYOK.
17.9.5. Hold Your Own Keys (HYOK) generally refers to the management of keys by the agency or organisation where keys may be generated by the agency or
by a third party such as a National Authority or a Certificate Authority. The agency retains full control of the management of keys.
17.9.6. Bring Your Own Keys (BYOK) also refers to the management of keys by the agency or organisation. In this case keys are provided to the cloud service
(or other service) providers for use on outsourced services related to that agency. In such cases, the agency relinquishes some elements of control of
the use, storage and protection of the keys.
Applicability for cryptographic systems
17.9.7. In general, the requirements specified in this manual for systems apply equally to cryptographic systems. Where the requirements for cryptographic
systems are different, the variations are contained in this section, and take precedence over requirements specified elsewhere in this manual.
Background
17.9.8. Encryption is an unparalleled technology for the protection of information but it relies on the strength of the algorithm, the strength of the key and,
most importantly, strong key management.
17.9.9. All encryption has four important characteristics:
The data to be protected;
The algorithm used to encrypt the data;
The protocol used to apply the algorithm; and
The encryption key.
17.9.10. In almost all cases the algorithm is in the public domain and is not a secret. When an encryption algorithm is publically available, security rests entirely
on the secrecy of the encryption key. It is also true that the effectiveness of most encryption systems depends on the secrecy of the encryption key.
249
Version_3.5__January-2022
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents