Security
Customer-managed encryption keys
Tested with:Databasezy API v1 · zb CLI 0.1
An organization owner manages configured key profiles under Compliance > Customer-managed encryption keys. A recent second factor is required to activate or revoke a binding. Provider profiles are configured with your operator; this form does not upload cloud credentials or change the provider’s key policy.
The settings show covered and unsupported stores. Covered secret envelopes include organization webhook URLs and signing secrets, SSO client secrets, and support tickets and assistant chats when the support key broker is enabled. An AWS KMS binding can also protect secure object storage. Database backups do not yet use your registered binding. Full customer-managed backup and volume coverage remains in development.
Rotation and existing data
Section titled “Rotation and existing data”Activating another binding retires the previous one. New covered secret values use the active binding; old envelopes retain their original binding until an authorized rewrap. A retired binding remains available for decryption. Keep its provider profile and decrypt permission until that migration is complete. Activating a binding does not rotate the provider’s key material or re-encrypt every stored object.
Secure volumes keep the key they were created with. Moving an existing volume to a new key requires a controlled copy; it does not happen when you activate another binding. See Amazon EBS encryption.
Before revoking a binding
Section titled “Before revoking a binding”Review the binding you selected, including retired bindings. The currently active provider’s coverage does not describe data written under an older provider.
- Covered secret envelopes under the revoked binding become unavailable to their service readers. Affected webhook deliveries fail, SSO connections stop working, and affected support messages and attachments become unavailable.
- Revoking the active binding also blocks new covered secret writes until another usable binding is activated. It cannot fall back to the platform key.
- A revoked binding cannot be reactivated. Rewrap supported values while the old binding and its provider permission still work.
- This action does not disable or delete the provider’s key or revoke its grants. AWS-encrypted objects and secure volumes can have separate dependencies on that key. Removing provider access can prevent future reads, decryption or volume attachment.
- Provider changes do not recall plaintext or data keys already in use. Immediate erasure of an attached volume is not guaranteed by a binding or provider-key revocation.
AWS documents that an unusable KMS key can leave already-decrypted data keys usable until the service needs KMS again. Review the provider’s key and data-key behavior before changing grants or key state. Unsupported stores retain their existing protection; revoking this binding does not establish that they have been erased.