Search filters this STIG's checks locally. Separate terms must all match (use quotes for an exact phrase). A search you ran on the Search page carries over here.
Assessment Title
Rule Text
The application must use FIPS-validated cryptographic algorithms defined in CNSSP 15 Annex B for authentication to a cryptographic module.
Description
Discussion Text
A software-based cryptographic module is a program or library that performs cryptographic operations—such as encryption, decryption, hashing, and key generation—entirely in software on a general-purpose processor. It operates within a defined "cryptographic boundary" separating the security functions from the rest of the operating system.
To protect the integrity of the authenticator and authentication mechanism used for the cryptographic module used by the network device, the application, operating system, or protocol must be configured to use one of the following hash functions for hashing the password or other authenticator in accordance with SP 800-131Ar1: SHA-1, SHA-224, SHA-256, SHA-384, SHA-512, SHA-512/224, SHA-512/256, SHA3-224, SHA3-256, SHA3-384, and SHA3-512.
Applications also include HMAC, KDFs, Random Bit Generation, and hash-only applications (e.g., hashing passwords and computing checksums).
Separate requirements for configuring applications and protocols used by each product (e.g., SNMPv3, SSH, NTP, and other protocols and applications that require server/client authentication) are required to implement this requirement.
To protect the integrity of the authenticator and authentication mechanism used for the cryptographic module used by the network device, the application, operating system, or protocol must be configured to use one of the following hash functions for hashing the password or other authenticator in accordance with SP 800-131Ar1: SHA-1, SHA-224, SHA-256, SHA-384, SHA-512, SHA-512/224, SHA-512/256, SHA3-224, SHA3-256, SHA3-384, and SHA3-512.
Applications also include HMAC, KDFs, Random Bit Generation, and hash-only applications (e.g., hashing passwords and computing checksums).
Separate requirements for configuring applications and protocols used by each product (e.g., SNMPv3, SSH, NTP, and other protocols and applications that require server/client authentication) are required to implement this requirement.
New to STIG checklists? Read What is a STIG checklist? and CKL vs CKLB.