The VPN Gateway must use FIPS-validated SHA-2 or higher hash function to protect the integrity of hash message authentication code (HMAC), Key Derivation Functions (KDFs), Random Bit Generation, hash-only applications, and digital signature verification.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-207218 | SRG-NET-000168-VPN-000600 | SV-207218r803427_rule | CCI-000803 | medium |
| Description | ||||
| Without cryptographic integrity protections, information can be altered by unauthorized users without detection. Although allowed by SP800-131Ar2 for some applications, SHA-1 is considered a compromised hashing standard and is being phased out of use by industry and Government standards. Unless required for legacy use, DoD systems should not be configured to use SHA-2 for integrity of remote access sessions. | ||||
| STIG | Date | |||
| Virtual Private Network (VPN) Security Requirements Guide | 2024-12-19 | |||
Related Frameworks
2 paths across 2 frameworks
Related Frameworks
NIST 800-531 mapping
IA-7
1.00
- DISA · 3 · disa_xccdf · related
- DISA · 2025-01-23 · disa_cci_list · equivalent
CCI1 mapping
CCI-000803
1.00
- DISA · 3 · disa_xccdf · related
Details
Check Text (C-207218r803427_chk)
Verify the VPN Gateway uses FIPS-validated SHA-2 or higher.
If the VPN Gateway does not use FIPS-validated SHA-2 or higher hash function to protect the integrity of hash message authentication code (HMAC), Key Derivation Functions (KDFs), Random Bit Generation, hash-only applications, and digital signature verification, this is a finding.
Fix Text (F-7478r803426_fix)
Configure the VPN Gateway to use FIPS-validated SHA-2 or higher hash function to protect the integrity of hash message authentication code (HMAC), Key Derivation Functions (KDFs), Random Bit Generation, hash-only applications, and digital signature verification.