Cryptographic Protection
System and Communications Protection
NIST Control Text
Implement cryptographic mechanisms to [Selection (one or more): prevent unauthorized disclosure of information; detect changes to information] during transmission.
NIST Discussion
Encryption protects information from unauthorized disclosure and modification during transmission. Cryptographic mechanisms that protect the confidentiality and integrity of information during transmission include TLS and IPSec. Cryptographic mechanisms used to protect information integrity include cryptographic hash functions that have applications in digital signatures, checksums, and message authentication codes.
Parameter Values
- Selection: Prevent unauthorized disclosure; detect changes
SL5 Supplemental Guidance
Accelerator Interconnect Encryption: AI accelerators within Weight Enclaves cryptographically protect all data transmitted over chip-to-chip interconnects (e.g., NVLink, UALink, custom fabrics). Hardware-level encryption prevents interception from physical interconnects during distributed operation.
Interconnect encryption protects data between accelerators; end-to-end encryption (where data arrives encrypted from origin and is re-encrypted before host-accessible export) protects data from host access at trust boundary crossings. Both are required. The accelerator must revoke host memory access before decrypting incoming data and complete encryption before restoring host access.
Inter-Facility Encryption: The organization implements cryptographic protection for all inter-facility network traffic within the SL5 Network using inline network encryptors deployed at facility boundaries. Inline network encryptors must implement post-quantum (quantum-resistant) cryptographic algorithms. The organization selects specific algorithms and parameters in accordance with current guidance from a recognized national cryptographic authority (e.g., NIST post-quantum cryptography standards or the NSA CNSA 2.0 suite [25], [26]); this standard does not mandate a specific algorithm. Whether or not FIPS-validated, each inline network encryptor must implement protections equivalent to the non-algorithm requirements of FIPS 140-3 Security Level 3 [28], including tamper-resistant and tamper-evident physical protection, identity-based operator authentication, self-tests, and secure management and zeroization of sensitive security parameters. Key management procedures must securely provision, synchronize where applicable, rotate, recover, revoke, and zeroize keys across corresponding endpoints; plaintext secret or private key entry or output requires a trusted channel and split knowledge. The organization deploys at least two inline network encryptors from different suppliers in series at each inter-facility connection per SC-29.