Title: The DBMS must use NIST validated FIPS 140-2 compliant cryptography for authentication mechanisms.
Vulnerability ID: V-32480
IA Controls: None
Description: Encryption is only as good as the encryption modules utilized. Unapproved cryptographic module algorithms cannot be verified, and cannot be relied upon to provide confidentiality or integrity and DoD data may be compromised due to weak algorithms.
Applications utilizing encryption are required to use approved encryption modules that meet the requirements of applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance.
FIPS 140-2 is the current standard for validating cryptographic modules and NSA Type-X (where X=1, 2, 3, 4) products are NSA certified hardware based encryption modules.
Authentication modules with weak encryption could allow an attacker to gain access to data stored in the database and to the administration settings of the DBMS.
Check Text: Review DBMS configuration to verify the DBMS is using NIST validated FIPS 140-2 compliant cryptography for all authentication mechanisms. If NIST validated FIPS 140-2 compliant cryptography is not being used for all authenticated mechanisms, this is a finding.
Fix Text: Utilize NIST validated FIPS 140-2 compliant cryptography for all authentication mechanisms.[divider]
The make this real easy, MS SQL Server is FIPS 140-2 complaint.
Microsoft works very hard to ensure that their products and cryptographic modules comply with the U.S. Federal government standard, Federal Information Processing Standard (FIPS) 140 – Security Requirements for Cryptographic Modules [FIPS 140].
Rather than list out a LOT of documentation here, I’m going tMicrosoft FIPS 140 Validation page which contains documents, maps and FAQs ensuring complaince with Microsoft products, including SQL Server.