Part 1: General - Computer Security Resource Center - National ...

March, 2007
10 Key Management Specifications for Cryptographic Devices or
Applications
Key management is often an afterthought in the cryptographic development process. As a result,
cryptographic subsystems too often fail to support the key management functionality and
protocols that are necessary to provide adequate security with the minimum necessary reduction
in operational efficiency. All cryptographic development activities should involve key
management planning and specification (see Part 2) by those managers responsible for the secure
implementation of cryptography into an information system. Key management planning should
begin during the initial conceptual/development stages of the cryptographic development
lifecycle, or during the initial discussion stages for the application of existing cryptographic
components into information systems and networks. The specifications that result from the
planning activities shall be consistent with NIST key management guidance.
For cryptographic development efforts, a key specification and acquisition planning process
should begin as soon as the candidate algorithm(s) and, if appropriate, keying material media
and format have been identified. Key management considerations may affect algorithm choice,
due to operational efficiency considerations for anticipated applications. For the application of
existing cryptographic products for which no key management specification exists, the planning
and specification processes should begin during device and source selection and continue
through acquisition and installation.
The types of key management components that are required for a specific cryptographic device
and/or for suites of devices used by organizations should be standardized to the maximum
possible extent, and new cryptographic device development efforts shall comply with NIST key
management recommendations. Accordingly, NIST criteria for the security, accuracy, and utility
of key management components in electronic and physical forms shall be met. Where the criteria
for security, accuracy, and utility can be satisfied with standard key management components
(e.g., PKI), the use of those compliant components is encouraged. A developer may choose to
employ non-compliant key management as a result of security, accuracy, utility, or cost
considerations. However, such developments should conform as closely as possible to
established key management recommendations.
10.1 Key Management Specification Description/Purpose
The Key Management Specification is the document that describes the key management
components that may be required to operate a cryptographic device throughout its lifetime.
Where applicable, the Key Management Specification also describes key management
components that are provided by a cryptographic device. The Key Management Specification
documents the capabilities that the cryptographic application requires from key sources (e.g., the
Key Management Infrastructure (KMI) described in Part 2 of this Recommendation for Key
Management.
119