DADP is a data-protection platform that separates policy control from runtime execution. Hub manages policy and operational state, while Engine processes cryptographic requests. Wrapper, Direct API, and DB UDF connect application and database execution paths to the runtime layer.
| Layer |
Primary Components |
Role |
| Control Plane |
Hub |
policy, key metadata, integration mapping, and operations |
| Data Plane |
Engine, Aggregator |
cryptographic execution and optional analytics |
| Integration Layer |
Wrapper, Direct API, DB UDF |
path-specific integration into applications and databases |
Operating Principles
- Policy is authored in the control plane.
- Cryptographic execution is handled in the data plane.
- Integration methods change the entry point, not the execution owner.
Official Integration Paths
| Method |
Entry Point |
Best Fit |
| Wrapper |
JDBC boundary |
application-side database access protection |
| Direct API |
application service code |
explicit runtime invocation from code |
| DB UDF |
database SQL path |
database-side execution through SQL |
Next Reading