Suite B Implementer’s Guide to NIST NSA http://docplayer.net/204368-Suite-b- SP 800-56A, July 28, 2009 implementer-s-guide-to-nist-sp-80056a-july-28-2009.html EPC342-08 Version 7.0 4 Guidelines on Cryptographic November 2017 Algorithms Usage and Key Management European Payments Council https://www.europeanpaymentscoun cil.eu/document-library/guidancedocuments/guidelines-cryptographicalgorithms-usage-and-keymanagement Choose an Encryption Algorithm Microsoft https://docs.microsoft.com/enus/sql/relationaldatabases/security/encryption/choos e-an-encryption-algorithm?view=sqlserver-2017 Transport Layer Protection Cheat OWASP Sheet https://www.owasp.org/index.php/Tr ansport_Layer_Protection_Cheat_She et Guide to Cryptography OWASP https://www.owasp.org/index.php/Gu ide_to_Cryptography New Directions in Cryptography - Diffie, Hellman IEEE Transactions on Information https://ee.stanford.edu/~hellman/pu blications/24.pdf Theory Vol IT22 November 1976 Rationale & Controls 17.1.51. Using cryptographic products 17.1.51.R.01. Rationale No real-world product can ever be guaranteed to be free of vulnerabilities. The best that can be done is to increase the level of assurance in a product to a point that represents satisfactory risk management. 17.1.51.R.02. Rationale Refer to Chapter 12 - Product Security for a discussion on product evaluation and assurance. 17.1.51.C.01. ControlSystem Classification(s): All Classifications; Compliance: MUST [CID:2070] Agencies using cryptographic functionality within a product to protect the confidentiality, authentication, non-repudiation or integrity of information, MUST ensure that the product has completed a cryptographic evaluation recognised by the GCSB. 17.1.52. Data recovery 17.1.52.R.01. Rationale It is important for continuity and operational stability that cryptographic products provide a means of data recovery to allow for the recovery of data in circumstances such as where the encryption key is unavailable due to loss, damage or failure. This includes production, storage, backup and virtual systems. This is sometimes described as “key escrow”. 17.1.52.C.01. ControlSystem Classification(s): Confidential, Secret, Top Secret; Compliance: MUST [CID:2074] Cryptographic products MUST provide a means of data recovery to allow for recovery of data in circumstances where the encryption key is unavailable due to loss, damage or failure. 17.1.52.C.02. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:2075] Cryptographic products SHOULD provide a means of data recovery to allow for recovery of data in circumstances where the encryption key is unavailable due to loss, damage or failure. 17.1.53. Reducing storage and physical transfer requirements 17.1.53.R.01. Rationale When encryption is applied to storage media (whether portable or residing within IT equipment or systems) it provides an additional layer of defence. Whilst such measures do not reduce or alter the classification of the information itself, physical storage, handling and transfer requirements may be reduced to those of a lesser classification for the media or equipment (but not the data itself). 17.1.53.R.02. Rationale Approved Cryptographic Algorithms are discussed in section 17.2. 17.1.53.C.01. ControlSystem Classification(s): All Classifications; Compliance: MUST [CID:2079] Encryption used to reduce storage or physical handling protection requirements MUST be an approved cryptographic algorithm in an EAL2 (or higher) encryption product. 17.1.53.C.02. ControlSystem Classification(s): Confidential, Secret, Top Secret; Compliance: MUST [CID:2080] If an agency wishes to reduce the storage or physical transfer requirements for IT equipment or media that contains classified information, they 235 Version_3.5__January-2022

Select target paragraph3

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