Vormetric BDT to CipherTrust BDT
Prerequisites
Data Security Manager (DSM) or KeySecure Classic is up and running at a supported version. Refer to their respective documentation for details.
A supported BDT version is configured with a supported DSM or KeySecure Classic version. Refer to the BDT documentation for details.
If you are using an older version of Vormetric BDT:
1. Save the configuration file at some location.
2. Uninstall Vormetric BDT.
3. Install BDT 2.3.0.
4. Copy the configuration file to the new installation.
5. Re-encrypt passwords in the configuration file.CipherTrust Manager is up and running a supported version. Refer to CipherTrust Manager Deployment for details.
If you are running an unsupported version, upgrade your environment to a supported version before proceeding. Refer to the corresponding product documentation for upgrade instructions.
Supported Versions
Current Setup
Product | Version |
---|---|
Vormetric BDT | 2.3.0 or higher |
DSM | 6.4.5 or higher |
KeySecure Classic | Supported by BDT |
Target Setup
Product | Version |
---|---|
CipherTrust BDT | 2.3.0 or higher |
CipherTrust Manager | 2.4 or higher |
CADP | To be decided |
CT-VL | To be decided |
Migration Steps
Upgrade your existing Key Manager to CipherTrust Manager.
For DSM: Migrate keys on the DSM to CipherTrust Manager. Refer to Migrate from Data Security Manager for details.
For KeySecure Classic: Migrate objects from KeySecure Classic to CipherTrust Manager. Refer to Migrating KeySecure Classic Data to a CipherTrust Manager Appliance for details.
If encrypting using Vormetric Application Encryption (VAE) or ProtectApp JCE (PA-JCE), use the following migration path:
For VAE: Install a supported version of CADP for Java, and configure it with the CipherTrust Manager. Refer to the CADP for Java documentation.
For PA-JCE: Migrate from PA-JCE to CADP for Java. Refer to Migrate from ProtectApp JCE to CADP for Java for details.
Update the BDT configuration file to point the instance of CADP for Java to CipherTrust Manager.
If tokenizing using Vormetric Tokenization Server (VTS), migrate from VTS to CT-VL. Refer to VTS to CT-VL Migration documentation for details.
Resume operations.