SQL6-D0-015600 - SQL Server must implement NIST FIPS 140-2 or 140-3 validated cryptographic modules to provision digital signatures.

Warning! Audit Deprecated

This audit has been deprecated and will be removed in a future update.

View Next Audit Version

Information

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-2 or 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.

Solution

In Windows, open Administrative Tools >> Local Security Policy.

Expand Local Policies >> Security Options.

In the right-side pane, double-click on 'System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing.'

See Also

https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_MS_SQL_Server_2016_Y22M10_STIG.zip

Item Details

References: CAT|I, CCI|CCI-002450, Rule-ID|SV-214022r863340_rule, STIG-ID|SQL6-D0-015600, STIG-Legacy|SV-94011, STIG-Legacy|V-79305, Vuln-ID|V-214022

Plugin: Windows

Control ID: df8d7e73645d2a3550395466b6cbf8fa2564f91e3d7c202ba5f59e815c227aef