Knowledge Base

KB #240111: Encryptionizer for SQL FIPS 140-2 Release Notes for FIPS 801.1 upgrades

Type:

Tip

Summary:

Below are the enhancements and fixes available in Encryptionizer for SQL FIPS 140-2 Validated (v16.311.23.14, build 1225). Changes are those that can be expected by customers who are upgrading from the original FIPS 140-2 Validated version (nlSetup64.sql.FIPS.8.8011.0.1a.prod.exe)

Additional Information:

Release Notes – nlfsetup.2014.0516.20136.3.exe (v36.3, build 516)

• FIPS 140-2 Validated modules
• Support for Windows 2016, Windows 10
• Support for SQL 2016
• Support for Advanced Format drives, including Windows Storage Spaces
• Support for Encryption of non-database files and logs using FIPS 140-2 validated algorithms
• Supports Log Shipping with shipping logs encrypted using FIPS 140-2 validated algorithms
• Support for Encryptionizer’s Enterprise Manager
• Support for custom plugins for Key Management
• Support for up to 32 cores (x86) or 64 cores (x64) (based on cores purchased)
• Different default method of Encryptionizer securing SQL which results in fewer issues on SQL start, as well as more independence from MS SQL Management Applications. (now using NetLib’s Key Management Service – KMS)
• Support for Windows Server 2008, 2008 R2, 2012, 2012 R2, 2016 and SQL Server 2008, 2008 R2, 2012, 2014, 2016
• single installer for x86 and x64 operating systems
• Improved resource management
• Enhanced: ability to encrypt all backups regardless of extension
• Enhanced: ability to select UNC alternate location for key storage
• Enhanced: New SQL API’s to tell if specific databases are encrypted
• Enhanced: Improved Encryptionizer logging – consolidation of logs
• Encryption key profile can be stored in the registry (as opposed to a key file)
• Fixed: Better memory allocation to avoid 1181 errors (insufficient resources)
• Fixed: Possible race condition when calling sp_n_enumfiles API
• Fixed: small memory leak when calling fn_n_freekey
• Fixed: Occasional error message after running an API: “A page that should have been constant has changed”
• Fixed: Could not specify a key containing all binary zeros
• Fixed: Rare BSOD on Windows 2012 R2, Windows 2003, Windows XP

Last modified: 4/3/2017