Feature Differences Between BDT 2.5.2 and 3.0.0
This document outlines the key functional differences between CipherTrust Batch Data Transformation (BDT) versions 2.5.2 and 3.0.0. It is intended for teams planning to transition to BDT 3.0.0, highlighting unsupported features and significant changes in behavior to ensure a smooth transition.
The following table lists functionalities which are supported in BDT 2.5.2 but are either unsupported in BDT 3.0.0 or whose implementation has been significantly modified.
| Feature/Capability | BDT 2.5.2 | BDT 3.0.0 |
|---|---|---|
| CT-VL Transformation | Supported | Not Supported Tokenization, detokenization, and rekey is not supported using CT-VL |
| Rekey Operations | Supported | Supported Added support of Reprotect operation which protects the data with the latest protection policy (keys and policies) |
| Crypto Parity | - | Data encrypted with 2.5.2 cannot be decrypted using BDT 3.0.0 Support for this capability is planned in future releases |
| Cryptographic Algorithms | — FF1 — FF3 — FPE/AES — DESede — AES/CTR — AES/CBC — FF1-luhn — FPE-luhn — Date — Random — Random-luhn | — FPE/AES — FPE/FF1v2 — FPE/FF3 — FPE/FF3-1 — AES/CBC — AES/ECB/NoPadding There are notable differences in algorithm support |
| Case Sensitivity | Case sensitivity is configurable | Always case-sensitive Affects all file and database objects (table, column, schema, and user names) |
| Whitespace Trimming | Supported | Not Supported Cannot trim leading and trailing white spaces from data to be transformed |
| Header Row Configuration | First row can be configured as a header | Always interprets the first row as the header |
| Configuration Source | BDT tile on CipherTrust Manager | Application Data Protection tile on CipherTrust Manager |
| Multiple CipherTrust Manager Instances | Supported | Not supported directly For high availability, a load balancer is recommended |
| Validation Options | Supports skipping validation or validation only mode | Always validates before running the transformation There is no option to skip validation or perform only validation |
| Processing Mode | Supports both remote and local processing | Supports only local processing The keys, policies, and configurations are cached locally during transformation |
| Configurable JDBC driver class name | Supported | Not supported |
| Resume job | Supported | Not Supported Support for this capability is planned in future releases |
| Rollback job | Supported | Not supported Support for this capability is planned in future releases |
| List source and destination tables/columns | Supported | Not supported |
For the complete list of features introduced in BDT 3.0.0, refer to BDT Documentation.
