Tenant encryption
Last updated: 2026-11-20Qlik Cloud encrypts all tenant data by default, and you can optionally use your own customer-managed keys (CMK) to control the encryption key.
When a tenant is created, Qlik Cloud uses multiple layers of security to protect your data. By default, each tenant is separated from other tenants by a uniquely generated set of encryption keys that are managed by the Qlik Cloud encryption service to encrypt content in the tenant. Each tenant’s keys are separate from the keys that Qlik Cloud uses to secure service-to-service communication.
Encryption standards
Qlik Cloud uses the following encryption standards:
-
In transit: TLS 1.2 encryption
-
At rest: AES-256-GCM encryption
-
Within the platform (after authentication with a designated IdP): Signed JSON Web Tokens (JWTs) to ensure integrity, authenticity, and non-repudiation
Key providers
Tenant admins choose which key provider encrypts the tenant data at rest. Qlik Cloud supports the following key providers:
-
Qlik Internal KMS (default): keys managed by Qlik
-
AWS KMS: a customer-managed key that you create and control in your own AWS Key Management Service (AWS KMS) account
Customer-managed keys
Use a customer-managed key (CMK) if you want control over the key that encrypts your tenant data at rest. With CMK, you are responsible for managing the key life cycle. Disabling or deleting the key affects access to your tenant.
CMK is required for tenants that process protected health information (PHI) under HIPAA. For details, see Customer-managed keys and HIPAA.
For responsibilities, regions and disaster recovery, and limitations, see Customer-managed keys. To set it up, see Setting up AWS KMS for customer-managed keys and Configuring customer-managed keys.