Approved Cryptographic Algorithms are described in Section 17.2. and Approved Cryptographic Protocols (applying the algorithms) are described in
Section 17.3. These sections also specify key strengths to resist attempts to compromise the key through cryptanalysis.
17.9.11. While any algorithm can, theoretically, be broken through cryptanalysis, this may require the use of vast computing power and other resources, making
this approach infeasible. If, however, the encryption key is compromised, there is no need to attack the algorithm itself. Attacks on encryption systems
will always target the weakest point, the protection of the key. Attempts to compromise keys and key management are more likely and more efficient
than attacks on the algorithm itself. This is why strong key management is vital in order to protect the encryption key and keep the key secure and
secret. When key management fails, cryptographic security is compromised.
17.9.12. In today’s Internet-connected world, almost all Internet security protocols use cryptography for authentication, integrity, confidentiality and nonrepudiation. It is vital that good key management is implemented if these security protocols are to be protected, considered reliable and provide
required levels of assurance to organisations and users.
17.9.13. In some cases, trusted third-party key management service providers furnish assistance to agencies in the generation, storage, operation,
management and retirement (disposal) of keys associated with the agency.
Key Management
17.9.14. For encryption to be used effectively, the encryption keys must be managed with the same care and security as the data encrypted by those keys for
the entire lifetime of those keys.
17.9.15. Key Management encompasses the operations and tasks necessary to create, protect and control the use of cryptographic keys. The process from
creation to destruction of the encryption key is described as the key management life cycle.
Key Management Life Cycle
17.9.16. The key management lifecycle covers:
Key generation;
Key registration;
Secure key storage;
Key distribution and installation;
Key use;
Key rotation;
Key backup (operational, backup and archive);
Key replacement and reissue;
Key recovery;
Key revocation;
Key suspension;
Key retirement; and
Key destruction.
Open Networks
17.9.17. Open networks, by definition, seek to establish arbitrary connections without there necessarily being a pre-existing relationship. Protocols have been
developed to manage this requirement through key exchange protocols and through trusted agents, most often a National Authority or Certificate
Authority. Again it is important that approved protocols and algorithms, as specified in this document, are used. Refer to sections 17.2 Approved
Cryptographic Algorithms and 17.3 Approved Cryptographic Protocols.
Public Key Infrastructure
17.9.18. Public Key Infrastructure was first publically discussed in the early 1970's with some of the first PKI standards from the IETF published in the 1990's. PKI
is the system to create, issue, manage and revoke digital certificates and their associated cryptographic keys. PKI has many different applications but
typically is used primarily for encrypting and digitally signing data in order to authenticate and protect data in transmission, supporting confidentiality
and privacy. It is used extensively in ecommerce, internet banking and secure email as well as being a key element in protecting website traffic.
Risks
17.9.19. There are a number of specific risks related to the management of cryptographic keys. These include:
Keys exposed to unauthorised persons or applications, potentially compromising the keys or data the encryption is protecting;
Data breaches;
Lost or unrecoverable cryptographic keys;
Software based key management, which provides only limited protection;
Fragmented key management as new systems are introduced; and
Poorly documented and understood key management processes and activities increasing the possibility of compromise and potentially increasing
compliance costs.
Prioritisation
17.9.20. Prioritisation helps identify and manage requirements for the use and management of cryptography and key management systems. This will determine
the extent and complexity of the key management programme. Important aspects to consider are:
Sensitivity and value of the data. This is summarised by the classification of the data but may not always reflect the values of aggregation, cost of
compliance breaches or reputation damage from a breach.
The volume of data and keys.
The variety of key types, data formats, algorithms, protocols and sources.
The speed and frequency of transactions, requirements for data access and availability.
References
250
Version_3.5__January-2022
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents