The DBMS must implement NIST FIPS 140-2 or 140-3 validated cryptographic modules to generate and validate cryptographic hashes.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-206640 | SRG-APP-000514-DB-000382 | SV-206640r961857_rule | CCI-002450 | medium |
| Description | ||||
| Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The application must implement cryptographic modules adhering to the higher standards approved by the federal government since this provides assurance they have been tested and validated. For detailed information, refer to NIST FIPS Publication 140-3, Security Requirements For Cryptographic Modules. Note that the product's cryptographic modules must be validated and certified by NIST as FIPS-compliant. | ||||
| STIG | Date | |||
| Database Security Requirements Guide | 2024-12-04 | |||
Related Frameworks
3 paths across 3 frameworks
Related Frameworks
NIST 800-531 mapping
SC-13
1.00
- DISA · 4 · disa_xccdf · related
- DISA · 2025-01-23 · disa_cci_list · equivalent
NIST 800-1711 mapping
3.13.11
1.00
- DISA · 4 · disa_xccdf · related
- DISA · 2025-01-23 · disa_cci_list · equivalent
- NIST · Rev 2 (Feb 2020, errata Jan 2021) · nist_800_171_app_d · equivalent
CCI1 mapping
CCI-002450
1.00
- DISA · 4 · disa_xccdf · related
Details
Check Text (C-206640r961857_chk)
If the DBMS does not employ NIST FIPS 140-2 or 140-3 validated cryptographic modules to generate and verify cryptographic hashes, this is a finding.
Fix Text (F-6900r860654_fix)
Implement a NIST FIPS 140-2 or 140-3 validated cryptographic module in the DBMS for generation and verification of cryptographic hashes.