17.1.57. Encrypting NZEO information in transit
17.1.57.R.01. Rationale
NZEO information is particularly sensitive and requires additional protection. It must be encrypted when in transit.
17.1.57.C.01. ControlSystem Classification(s): All Classifications; Compliance: MUST
[CID:2100]
In addition to any encryption already in place for communication mediums, agencies MUST use an Approved Cryptographic Protocol and
Algorithm to protect NZEO information when in transit.
17.1.58. Key Refresh and Retirement
17.1.58.R.01. Rationale
All cryptographic keys have a limited useful life after which the key should be replaced or retired. Typically the useful life of the cryptographic
key (cryptoperiod) is use, product and situation dependant. Product guidance is the best source of information on establishing cryptoperiods
for individual products. A more practical control is the use of data, disk or volume encryption where key changes are more easily managed.
Selection of cryptoperiods should be based on a risk assessment. Refer also to section 17.9 – Key Management.
17.1.58.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:2103]
Agencies SHOULD establish cryptoperiods for all keys and cryptographic implementations in their systems and operations.
17.1.58.C.02. ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:2104]
Agencies SHOULD use risk assessment techniques and guidance to establish cryptoperiods.
17.1.58.C.03. ControlSystem Classification(s): All Classifications; Compliance: MUST
[CID:2105]
Agencies using HACE MUST consult the GCSB for key management requirements.
17.2. Approved Cryptographic Algorithms
Objective
17.2.1. Information is protected by a properly implemented, Approved Cryptographic Algorithm.
Context
Scope
17.2.2. This section covers cryptographic algorithms that the GCSB recognises as being approved for use within government. Implementations of the
algorithms in this section need to have successfully completed an approved cryptographic evaluation before they can be approved to protect
information. Correct implementations of cryptographic protocols are checked during system certification.
17.2.3. High assurance cryptographic are not covered in this section.
Approved cryptographic algorithms
17.2.4. There is no guarantee or proof of security of an algorithm against presently unknown attacks. However, the algorithms listed in this section have been
extensively scrutinised by government, industry and academic communities in a practical and theoretical setting and have not been found to be
susceptible to any feasible attacks. There have been some cases where theoretically impressive vulnerabilities have been found, however these
results are not considered to be feasible with current technologies and capabilities.
17.2.5. Where there is a range of possible key sizes for an algorithm, some of the smaller key sizes do not provide an adequate safety margin against attacks
that might be found in the future. For example, future advances in number factorisation could render the use of smaller RSA moduli a security
vulnerability.
17.2.6. The approved cryptographic algorithms fall into three categories: asymmetric/public key algorithms, hashing algorithms and symmetric encryption
algorithms. Collectively these were known as SUITE B and were first promulgated in 2006.
17.2.7. Suite B was superseded by the Commercial National Security Algorithm Suite in August 2015 and later supplemented by the Commercial Solutions for
Classified (CSFC) Programme.
17.2.8. Some algorithms that were previously approved in earlier versions of the NZISM are now deprecated. These are still permitted to be used to decrypt or
verify previously encrypted or signed files. These algorithms are described as ‘for legacy use only’ in the NZISM.
17.2.9. The approved asymmetric/public key algorithms are:
ECDH for agreeing on encryption session keys.
ECDSA for digital signatures.
DH for agreeing on encryption session keys. This should only be used for interoperability with third parties where ECDH is not supported.
RSA for digital signatures and passing encryption session keys or similar keys.
DSA for digital signatures for legacy use only.
17.2.10. The approved hashing algorithms are:
Secure Hashing Algorithm 2; and
Secure Hashing Algorithm 1 for legacy use only.
17.2.11. The approved symmetric encryption algorithms are:
AES; and
3DES for legacy use only.
17.2.12. SHA-1, 3DES and DSA MUST NOT be used for new implementations but are approved only for processing already protected information. These are
237
Version_3.5__January-2022
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents