How does iDBQuery manage encryption keys, and can I bring my own?

Encryption keys are only as trustworthy as who holds them, and iDBQuery's architecture is built to keep that control with you.

• Encryption everywhere - data is encrypted in transit with modern TLS and at rest on disk, so it is protected both on the wire and where it sits.
• Keys in your environment - in a VPC or on-prem deployment, keys reside inside your infrastructure, so you own storage, rotation, and revocation.
• Bring your own key - where your setup uses a cloud KMS or a hardware security module, iDBQuery can rely on keys you manage there rather than keys it generates.
• Credential protection - connection secrets for your data sources are stored encrypted, not in plain text.

For example, an on-prem customer can back iDBQuery's at-rest encryption with keys in their own HSM, so even the vendor could not decrypt stored configuration. This matters because key custody is often the real question behind 'is it encrypted' - encryption with vendor-held keys is weaker than encryption with keys you control. iDBQuery's deployment flexibility, including VPC and air-gapped installs, is what makes genuine customer key control possible, alongside RBAC and query-in-place so there is less sensitive data at rest in the first place. Contact us to design key management for your deployment.