The National Cryptographic Standards Sharing Notice: White 6 Key Lifecycle Management (KLM( 6.1 Key Protection and Lifetime Accepted key protection lifetime: • Using Hardware cryptographic modules: . Private keys should not be valid for more than 5 years (this does not limit CA certificates’ lifetime) for MODERATE12. . Private keys should not be valid for more than 3 years (this does not limit CA certificates’ lifetime) for ADVANCED12. • Using Software cryptographic modules: . Private keys must not be valid longer than 2 years for MODERATE12. . Not accepted for ADVANCED. 6.2 KLM Processes Table 1 lists the required KLM processes from generation till destruction. Table 1 KLM Processes Requirements KLM processes Requirements Key Generation • Keys (secret and private) must not be vulnerable to prediction or bias. • Weak keys must not be used. • Private and public keys require prime number generation with extra mathematical properties. Key • Keys must be associated with their owner (user) with a certificate. Registration/ • Root certificates must be distributed to relying parties and signatories. Certification • A trusted CA must be used. Key Distribution • Keys must be distributed to their users securely and must be under and Installation the users control. • Keys must be transported securely by protecting their confidentiality and authenticity. • All copies of keys must be securely installed and stored. • Public keys must be transported and authenticity (but not privacy) must be protected by using certificates. • Private keys must be protected and authorized by the owner/ third party or CA. E. Barker, “Recommendation for Key Management: Part 1 - General," NIST, NIST Special Publication 800-57 Part 1 Revision 5, May 2020. https://doi.org/10.6028/NIST.SP.800-57pt1r5. 12 Document Classification: Open 21

Select target paragraph3

Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents