This FAQ is about the keys used with cryptographic algorithms employed during communications and/or storage that are used, for example, to encrypt and decrypt data (providing confidentiality protection for that data) or to detect any modifications to the data,

Cryptographic key management involves the handling of cryptographic keys and other related security parameters during the entire lifecycle of the keys, including their generation, storage, distribution/establishment, use and destruction. CKM also includes the policies for selecting appropriate cryptographic algorithms and key sizes, the key-establishment schemes and protocols to utilize and support the generation or distribution of keys, the protection and maintenance of keys and related data, and the integration of key management with cryptographic technology to provide the required type and level of protection required by an organization. 

The proper management of cryptographic keys is essential to the effective use of cryptography for security. A cryptographic key is analogous to the combination of a safe. If an adversary knows the combination, the strongest safe provides no security against penetration. Similarly, poor key management may easily compromise strong algorithms.

U.S. policy documents have made NIST responsible for developing Standards and Guidelines for the protection of sensitive, but unclassified, U.S. Federal information and for assisting national or international standards bodies in producing a range of standards, including those for protecting information and its processing. In fulfilling its responsibilities, NIST has established working relationships with security system developers, academic researchers, commercial vendors, government and public sector computer users, and network operators in developing and utilizing effective information security Standards and Guidelines.

General Key-Management Guidance:

• NIST SP 800-57, Recommendation for Key Management, is a three-part series of publications. Part 1 (General) provides general guidance for the management of cryptographic keying material. Part 2 (Best Practices for Key-Management Organizations) provides guidance on policy and security planning requirements for U.S. government agencies. Part 3 (Application-Specific Key-Management Guidance) provides guidance when using the cryptographic features of current systems.
• NIST SP 800-130, A Framework for Designing Cryptographic Key Management Systems, contains topics that should be considered by a Cryptographic key Management System (CKMS) designer when developing a CKMS design specification.
• NIST SP 800-131A Revision 1, Transitions: Recommendations for Transitioning the Use of Cryptographic Algorithms and Key Lengths, provides specific guidance for transitions to the use of stronger cryptographic keys and more robust algorithms.
• NIST SP 800-152, A Profile for U.S. Federal Cryptographic Key Management Systems, contains requirements for the design, implementation, procurement, installation, configuration, management, operation and use of CKMSs by U.S. federal organizations. The profile is based on SP 800-130.

Key Generation: The generation of keys using random bit generators.

• NIST SP 800-133, Recommendation for Cryptographic Key Generation, discusses the generation of the keys to be managed and used by the approved cryptographic algorithms.

Key Establishment: The agreement and/or transport of cryptographic keys using automated protocols (e.g., TLS and SSH):

• NIST SP 800-56A Revision 2 , Recommendation for Pair-Wise Key Establishment Using Discrete Logarithm Cryptography, specifies several variations of the Diffie-Hellman and MQV key-establishment schemes that may be used during automated communication protocols.
• NIST SP 800-56B Revision 1, Recommendation for Pair-Wise Key Establishment Using Integer Factorization Cryptography, specifies key-establishment schemes that may be used during automated communication protocols.

Key Wrapping:

• NIST SP 800-38F, Recommendation for Block Cipher Modes of Operation: Methods for Key Wrapping, specifies methods for providing confidentiality and integrity protection for cryptographic keys using block cipher algorithms (i.e., AES and the Triple Data Encryption Algorithm (TDEA))

Key Derivation: The derivation of a cryptographic key from an already available key and other information.

• NIST SP 800-56C, Recommendation for Key Derivation Methods in Key Establishment Schemes, specifies key derivation methods to derive a key from a shared secret established through a scheme specified in SP 800-56A and SP 800-56B. 
• NIST SP 800-108, Recommendations for Key Derivation Using Pseudorandom Functions, specifies techniques for the derivation of additional keying material from a secret key that was either established from the use of a key-establishment scheme or shared in some other manner.
• NIST SP 800-132, Recommendations for Password-Based Key Derivation: Part 1: Storage Applications, specifies techniques for the derivation of master keys from passwords or passphrases to protect stored electronic data or data-protection keys.
• NIST SP 800-135 Revision 1, Recommendation for Existing Application-Specific Key-Derivation Functions, provides security requirements for the key-derivation functions employed in widely used internet security protocols.

Cryptographic algorithms are executed within cryptographic modules (see FIPS 140-2, Security Requirements for Cryptographic Modules ). The Cryptographic Algorithm Validation Program (CAVP) and Cryptographic Module Validation Program (CMVP) are responsible for testing against many of the publications listed above. Visit  the CAVP and CMVP for information on algorithms currently being tested