SP 800-38A Recommendation for Block Cipher NIST Modes of Operation: Methods and https://csrc.nist.gov/publications/det ail/sp/800-38a/final Techniques December 2001 This publication is under review (May 2021) FIPS 180-4 Secure Hash Standard (SHS) NIST August 2015 https://csrc.nist.gov/publications/det ail/fips/180/4/final SP 800-63 Digital Identity Guidelines NIST https://pages.nist.gov/800-63-3/ SP 800-106 Randomized Hashing for Digital NIST https://csrc.nist.gov/publications/det Signatures ail/sp/800-106/final February 2009 SP 800-107 Rev. 1 Recommendation for Applications NIST Using Approved Hash Algorithms https://csrc.nist.gov/publications/det ail/sp/800-107/rev-1/final August 2012 This publication is under review (6 August 2021) SP 800-132 Recommendation for Password- NIST Based Key Derivation: Part 1: Storage Applications https://csrc.nist.gov/publications/det ail/sp/800-132/final December 2021 Commercial National Security NSA Algorithm (CNSA) Suite https://www.iad.gov/iad/programs/ia d-initiatives/cnsa-suite.cfm January 2016 Commercial National Security NSA Algorithm (CNSA) Suite Factsheet https://www.iad.gov/iad/library/iaguidance/ia-solutions-forclassified/algorithmguidance/commercial-nationalsecurity-algorithm-suitefactsheet.cfm Commercial Solutions for Classified NSA (CSfC) FAQ 2018 https://www.nsa.gov/Portals/70/d ocuments/resources/everyone/csfc/c sfc-faqs.pdf Rationale & Controls 17.2.17. Using Approved Cryptographic Algorithms 17.2.17.R.01. Rationale Inappropriate configuration of a product using an Approved Cryptographic Algorithm can inadvertently select relatively weak implementations of the cryptographic algorithms. In combination with an assumed level of security confidence, this can represent a significant security risk. 17.2.17.R.02. Rationale When configuring unevaluated products that implement an Approved Cryptographic Algorithm, agencies should disable any non-approved algorithms. Correct implementation of cryptographic protocols and disabling of non-approved algorithms is checked during system certification. A less effective control is to advise system users not to use them via a written policy. 17.2.17.C.01. ControlSystem Classification(s): All Classifications; Compliance: MUST [CID:2128] Agencies MUST ensure that only Approved Cryptographic Algorithms can be used when using an unevaluated product that implements a combination of approved and non-approved Cryptographic Algorithms. 17.2.18. Approved asymmetric/public key algorithms 17.2.18.R.01. Rationale Over the last decade DSA and DH cryptosystems have been subject to increasingly successful sub-exponential factorisation and index-calculus based attacks. ECDH and ECDSA offer more security per bit increase in key size than either DH or DSA and are considered more secure alternatives. 17.2.18.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:2131] Agencies SHOULD use ECDH and ECDSA for all new systems, version upgrades and major system modifications. 17.2.19. Using DH 17.2.19.R.01. Rationale While ECDH should be used in preference to DH, there are instances where DH is still in use. A modulus of at least 3072 bits for DH is now considered good practice by the cryptographic community. 240 Version_3.5__January-2022

Select target paragraph3

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