Release Notes
Product Description
CipherTrust Database Protection for MSSQL (formerly known as ProtectDB for MSSQL) delivers powerful protection for the sensitive corporate and customer information stored in databases. With CDP, you have the flexibility to encrypt data at the column-level within databases, at the application layer, and during batch-driven data transformation and transaction processes.
This document may at times abbreviate CipherTrust Database Protection for MSSQL to CDP and CipherTrust Manager to Key Manager.
Release Description
This release includes new feature, enhancements, and bug fixes. It also provides information on deprecated support.
Features and Enhancements
When CDP performs crypto operations in local mode, the error replacement values also get cached.
SafeNet protectDB for MSSQL has been rebranded to CipherTrust Database Protection for MSSQL.
Deprecated Support
SQL Server 2005 is no longer supported in CDP.
Resolved and Known Issues
This section lists the issues that have been resolved in this release and that are known to exist in this release. The following table defines the severity of the issues listed in this section.
Resolved Issues
This section lists the fixed issues.
| Reference | Synopsis |
|---|---|
| PDB-3794 | When you upgrade PDB versions (prior to 8.9.0) to 8.11.0, and you perform select operation, Null is displayed instead of an empty record. |
| PDB-3630 | An AD group database user is not able to get the right access when its userPrincipalName is different from the samAccountName. |
Known Issue and Workaround
The following issue is known to exist in the product at the time of release.
| Issue | Severity | Synopsis |
|---|---|---|
| CADP-10441 | H | Unable to map users with metadata only install. Workaround: — Download and copy the CDPmetaUpdate.sql to a location that is accessible by SQL Server. — In the CDPmetaUpdate.sqlfile, update the following parameters with their actual values:— <MetaDatabaseName>: meta database name used for meta only install. — <MetaUser>: meta user name used for meta only install — <Full path of IngIntegratedCore.dll>: path of IngIntegratedCore.dll which will be there in the meta only installation directory. For example: C:\Program Files (x86)\CipherTrust\CDP_MSSQLServer\MSSQLSERVER_<MetaDatabaseName>\IngIntegratedCore.dll.— Make a connection on the SQL Server Management Studio with the database user that was used for meta only installation. — Execute the CDPmetaUpdate.sql script.— Add user mapping. |
Compatibility Information
CDP is compatible with:
CipherTrust Manager 2.4 or higher versions.
KeySecure Classic 8.12.3 or higher versions.
Upgrade Path
CDP can be upgraded from:
| Upgrade Path | Upgrade Path |
|---|---|
| 8.9.0 | 8.10.0 |
| 8.10.1 | 8.10.2 |
| 8.11.0 |
Note
If you are upgrading from any versions prior to 8.9.0, first upgrade to PDB 8.9.0 and then upgrade to CDP 8.12.0.
Supported Platforms
CDP for MSSQL supports all the versions of Windows operating systems that are supported by the database.
Supported SQL Server Versions
CDP supports the following SQL Server versions:
| Supported Version | Supported Versions |
|---|---|
| SQL Server 2008 | SQL Server 2012 |
| SQL Server 2014 | SQL Server 2016 |
| SQL Server 2017 | SQL Server 2019 |
