BaselineWatch
Desk

6.2.1.3 Confidentiality

NIST platform security: roots of trust, firmware and secure enclaves SP 800-57 Part 1 Rev. 5 against SP 800-57 Part 1 Rev. 4
All changes in this version
removed 6 Training: If the new system requires that new or different tasks (e.g., key part of 6.2.1

Title changed

Before · SP 800-57 Part 1 Rev. 4

Confidentiality

After · SP 800-57 Part 1 Rev. 5

Confidentiality

Control changed

Before · SP 800-57 Part 1 Rev. 4

Keying material may require confidentiality protection during transit. If confidentiality protection is required, the keying material shall be protected using one or more of the following mechanisms: 1. Manual method: (a) The keying material is encrypted (e.g., wrapped) using an approved technique that provides protection at a security strength that meets or exceeds the security strength required of the keying material. -OR- (b) The keying material is separated into key components, with each key component being generated at a security strength that meets or exceeds the security strength required of the keying material. Each key component is handled, using split- knowledge procedures (see Sections 8.1.5.2.1 and 8.1.5.2.2.1 ), so that no single individual can acquire access to all key components. -OR- (c) Appropriate physical and procedural protection is provided (e.g., by using a trusted courier).

After · SP 800-57 Part 1 Rev. 5

Keying material may require confidentiality protection during transit. If confidentiality protection is required, the keying material shall be protected using one or more of the following mechanisms: 1. Manual method: (a) The keying material is encrypted (e.g., wrapped) using an approved technique that provides protection at a security strength that meets or exceeds the security strength required of the keying material. -OR- (b) The keying material is separated into key components, with each key component being generated at a security strength that meets or exceeds the security strength required of the keying material. Each key component is handled, using split- knowledge procedures (see Sections 8.1.5.2.1 and 8.1.5.2.2.1 ), so that no single individual can acquire access to all key components. -OR- (c) Appropriate physical and procedural protection is provided (e.g., by using a trusted courier).