Release Date: September 2026
Release Type: Data Protection & Lifecycle Enhancement
Branch: 3.9.0
OneDB v3.9.0 introduces Protection Lineage and Protection Lifecycle, helping data-protection policies remain consistent as protected data is copied or database structures change.
The release also includes compatibility improvements for IBM Db2 and Oracle Database.
What’s New in v3.9.0
Protection Lineage
OneDB can now preserve protection policies when protected data is copied between supported database objects.
For supported database operations, protection settings can automatically follow the data from source fields to destination fields, helping reduce the need to manually recreate protection policies after database-side copy operations.
Protection Lineage supports:
- Tokenize
- Detokenize
- Direct Masking
- Source and destination columns with different names
- Supported direct and derived data mappings
When protected source data is transformed into a derived value where the original protection policy cannot be safely inherited, OneDB can apply Direct Masking to help prevent the resulting data from being exposed without protection.
Protection Lineage updates OneDB protection metadata without changing the database’s native query execution or rewriting copied database values.
Protection Lifecycle
OneDB v3.9.0 improves how protection policies are maintained when database structures change.
For supported schema operations, existing Field Settings can automatically follow renamed columns or be removed when the corresponding protected column or database object is removed.
This helps administrators keep protection policies synchronized with changes to the underlying database structure.
Existing administrator-defined protection settings are preserved and are not automatically overwritten when conflicts are detected.
PostgreSQL
Added Protection Lineage for supported INSERT ... SELECT operations.
Protection policies can follow protected data copied between PostgreSQL tables, including supported scenarios where source and destination column names differ.
Protection Lifecycle also supports selected column rename and removal operations.
MySQL
Added Protection Lineage for supported INSERT ... SELECT operations, including supported prepared statements.
Protection policies can follow direct or derived protected data across supported MySQL table-to-table copy operations.
Protection Lifecycle also supports selected column rename and removal operations.
Microsoft SQL Server
Added Protection Lineage for supported INSERT ... SELECT operations across supported SQL Server execution methods.
Protection policies can follow protected data across supported table-to-table copy operations while preserving existing administrator-defined destination settings.
Protection Lifecycle also supports selected column rename and removal operations.
Oracle Database
Added Protection Lineage for supported INSERT ... SELECT operations.
Protection policies can follow protected data across supported Oracle table-to-table copy operations, including supported schema-qualified objects, aliases, and renamed destination columns.
Protection Lifecycle also supports selected column rename and removal operations.
Oracle compatibility has also been improved for SQL Developer and JDBC clients, protected query results, empty result sets, transaction handling, and supported schema operations.
IBM Db2
Added Protection Lineage for supported INSERT ... SELECT operations across supported Db2 execution methods.
Protection policies can follow protected data between supported Db2 database objects while maintaining existing protection behavior.
Protection Lifecycle also supports selected column rename and removal operations.
Db2 compatibility has also been improved for JDBC clients, protected result processing, and database metadata handling.
MongoDB
Added Protection Lineage for supported MongoDB aggregation pipelines using $out.
Protection policies can follow direct or renamed fields into destination collections. Derived values based on protected source data can be handled using Direct Masking where direct protection inheritance is not appropriate.
OneDB also improves protection metadata management when $out replaces a destination collection or when supported collections are removed.
Protection That Follows Your Data
With OneDB v3.9.0, protection is no longer limited to the original location where a policy was configured.
Protection Lineage helps protection follow supported data movement, while Protection Lifecycle helps protection remain aligned as database structures evolve.
Together, these capabilities reduce administrative effort and help maintain consistent protection for sensitive database data.