Qlik Cloud’s customer managed encryption keys offers a valuable layer of security and control and fulfills stringent compliance requirements like HIPAA.
In today's data-driven world, ensuring the privacy and security of sensitive information is paramount. That's where Customer Managed Keys (CMK), often referred to as Bring Your Own Key (BYOK), come into play. These advanced data encryption controls allow organizations to manage and leverage their own encryption keys versus using Qlik’s.
Through this enhancement in CMK, we can now support the following scenarios of converting a tenant with existing data:
From Qlik Internal KMS to AWS KMS
From AWS KMS to Qlik Internal KMS
From one AWS KMS Key to another AWS KMS Key ( Key Rotation)
Public APIs and CMK connectors are also available in Qlik Cloud Application Automation to simplify deployment and lifecycle management.
By implementing Customer Managed Keys, organizations can encrypt their data ensuring that only authorized parties can access it. This robust encryption strategy not only fortifies data privacy but also helps companies meet regulatory obligations, HIPAA, or industry-specific standards when designing new solutions or products. In the age of ever-increasing data breaches and cyber threats, CMK empowers businesses to adopt cloud technology with confidence that their data is well-protected and in compliance with the most stringent data privacy regulations.
To learn more, watch the video below and for a more technical blog, see link here.
Hi. Is this feature the reason there is no need to continue with Qlik Forts? Are we at a point where client security teams will accept owning the encryption will open Qlik Cloud to use in cases where they would rather consider Qlik Forts or Client-managed?
