SP 800-57 Recommendations for Key NIST Management http://csrc.nist.gov/publications/Pub sSPs.html Rationale & Controls 17.6.6. Decommissioning 17.6.6.R.01. Rationale Decommissioning MUST ensure any remanent cryptographic data is destroyed or unrecoverable. 17.6.6.C.01. ControlSystem Classification(s): All Classifications; Compliance: MUST [CID:2769] Decommissioning of faulty or redundant equipment MUST comply with media sanitisation requirements described inChapter 12 – Product Security. 17.6.7. Using S/MIME 17.6.7.R.01. Rationale S/MIME 2.0 used weaker cryptography (40-bit keys) than is approved for use by the government. Version 3.0 was the first version to become an Internet Engineering Taskforce (IETF) standard. 17.6.7.R.02. Rationale Agencies choosing to implement S/MIME should be aware of the inability of many content filters to inspect encrypted messages and any attachments for inappropriate content, and for server-based antivirus software to scan for viruses and other malicious code. 17.6.7.R.03. Rationale Improper decommissioning and sanitisation presents opportunities for harvesting Private Keys. Products that hosted multiple Private Keys for the management of multiple identities should be considered points of aggregation with an increased “target value”. Where cloud based computing services have been employed, media sanitisation may be problematic and require the revocation and re-issue of new keys. 17.6.7.C.01. ControlSystem Classification(s): All Classifications; Compliance: MUST NOT [CID:2780] Agencies MUST NOT allow versions of S/MIME earlier than 3.0 to be used. 17.7. OpenPGP Message Format Objective 17.7.1. OpenPGP Message Format is implemented correctly as an Approved Cryptographic Protocol. Context Scope 17.7.2. This section covers information on the conditions under which the OpenPGP Message Format can be used as an approved cryptographic protocol. It applies to the protocol as specified in IETF’s RFC 2440 and RFC 4880, which supercedes RFC 2440. 17.7.3. When using a product that implements the OpenPGP Message Format, requirements for using approved cryptographic protocols will also need to be referenced from the Section 17.3 - Approved Cryptographic Protocols. 17.7.4. Information relating to the development of password selection policies and password requirements can be found in theSection 16.1 - Identification and Authentication. References 17.7.5. Further information on the OpenPGP Message Format can be found at: Reference RFC 4880 Title Publisher Source IETF https://datatracker.ietf.org/doc/html/ OpenPGP Message Format specification rfc4880 Rationale & Controls 17.7.6. Using OpenPGP Message Format 17.7.6.R.01. Rationale If the private certificate and associated key used for encrypting messages is suspected of being compromised i.e. stolen, lost or transmitted over the Internet, then no assurance can be placed in the integrity of subsequent messages that are signed by that private key. Likewise no assurance can be placed in the confidentiality of a message encrypted using the public key as third parties could intercept the message and decrypt it using the private key. 17.7.6.C.01. ControlSystem Classification(s): All Classifications; Compliance: MUST [CID:2806] Agencies MUST immediately revoke key pairs when a private certificate is suspected of being compromised or leaves the control of the agency. 17.8. Internet Protocol Security (IPSec) Objective 17.8.1. Internet Protocol Security (IPSec) is correctly implemented. Context 247 Version_3.5__January-2022

Select target paragraph3

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