Release Notes

Product Description

CipherTrust Vaulted Tokenization (CT-V) supplements Thales encryption solutions by facilitating smooth application performance and transparent end-user operation while keeping encrypted information secure in one central location. For countries with data privacy laws that require sensitive data remain in country, tokenization offers the flexibility to offshore storage without compromising compliance. CT-V also helps simplify audit compliance by reducing the number of auditable systems.

Release Description

This release includes the resolved issue CADP-17019.

Notes for MySQL Database

• If a token vault contains multiple entries of the same plaintext with different custom data, CT-V 8.12.4 cannot be used with these token vaults.

• Upgrade the existing token vaults to make them compatible with CT-V 8.12.4.

• Non-idempotent token vaults are not supported for MySQL database.

Supported Databases

CT-V 8.12.4 is the next standard release over the previous release. This version is explicitly validated on the following platforms:

Advisory Notes

• Enable SSL communications between CT-V and Microsoft SQL Server

  To enable SSL communications between CT-V and Microsoft SQL Server, edit the SafeNetToken.properties and set the DatabaseType=SQLServerSSL. If using the Web service, restart Tomcat so that the CT-V jar file will be reloaded with the new property value. The JDBC driver will use SQL Server's self-signed certificate.

• Multi-threading

  By default, CT-V automatically splits insert, get, and getToken batches larger than 2000 into multiple threads and executes them in parallel. In these scenarios, adding multithreading to your application may not be necessary.

  When using CT-V in a multithreaded application, it is recommended to use use no more than 10 threads per single CPU machine.

• Oracle Batch Jobs

  It is recommended to execute the analyze table command after running the first batch job on a token vault in an Oracle database.

  For example:

  analyze table <your_token_vault_table> compute statistics;
  

  If this command is not used, performance will degrade after running batches between 5000 and 10000 rows. When using the CT-V Web service, this performance degradation will cause a Read Timeout Exception.

Issues Severity and Classification

The following table serves as a key to the severity and classification of the issues listed in the Known Issues table:

Resolved Issues

Known Issues

while (true) {
for (int loop = 0; loop < 10000; loop++)
{  data_toTokenize = data_toTokenize + loop;
try {
token = ts.insert(data_toTokenize,dbTable,format, true);
System.out.println("Token #"+loop+" Original Data "+data_toTokenize+" in newformat: " + token);
}
catch (Exception e) {
System.out.println("Token #"+loop+" Original Data "+data_toTokenize+" in new format: " + token+" FAILED");
e.printStackTrace();
//For retrying for the same input value
loop--;
}
}
}

Compatibility and Upgrade Information

CT-V 8.12.4 is compatible with CipherTrust Manager 2.2 and higher versions.

Installation and Upgrade Instructions

Refer to CipherTrust Manager User Guide for complete installation and upgrade instructions for the server, and CipherTrust Vaulted Tokenization User Guide for the client and token vault details.

Installation Prerequisites for Client

• Supported Java versions are 8 (minimum 1.8.0_111), 10, 11, 17.

• Installing CT-V in the .NET environment, requires the following:

  • A recent version of .NET Framework is installed. It is recommended to use .NET version 4.0.

  • A token vault is already created.

    Note

    • The InstallShield Wizard first deletes the existing version of CipherTrust Vaulted Tokenization, and then installs the latest version.

    • Before installing the latest version of CT-V in the .NET environment, manually uninstall SafeNet Tokenization 8.4.0 or lower versions, otherwise the installation will fail.