Data Protection
KurrentDB Connectors use envelope encryption to protect sensitive configuration fields such as passwords, access tokens and private keys.
When you configure a connector, the system encrypts sensitive data using Data Encryption Keys (DEKs). It then wraps those keys with a master key based on the token you provide. KurrentDB stores the encrypted data, never the plaintext.
Data protection applies to both sinks and sources. Each connector type declares its own sensitive keys. The Kafka source protects its SASL credentials and its SSL certificates. The webhook source protects its signature secret. To see which fields a connector protects, open that connector’s page from the Connectors overview.
Configuring Data Protection
Section titled “Configuring Data Protection”Provide the encryption token either in a token file or directly in the configuration.
Using a Token File
Section titled “Using a Token File”KurrentDB: DataProtection: TokenFile: "/path/to/token/file"Using a Token Directly
Section titled “Using a Token Directly”KurrentDB: DataProtection: Token: "<your-secret-token>"The root section name is the server’s own configuration root. The default root is KurrentDB. The
server also accepts Kurrent and EventStore for compatibility with earlier versions.
Key Vault
Section titled “Key Vault”KurrentDB Connectors use the Surge key vault internally to manage encryption keys. Surge is KurrentDB’s native key storage mechanism, and it stores encrypted keys in internal system streams. The Surge vault is the default and the only key vault currently available. The data protection framework uses it automatically, with no configuration from you.
Support for additional key vault options, including external key management systems, is planned for future releases.