We’re excited to announce Keyper v0.0.2 release and a step by step tutorial for data vulnerability remediation. Read more about the tutorial here.
We've added several important features in this release to make Keyper a cloud and production ready library.
We’ve added support for Terraform remote backend in Google Cloud Storage (GCS). This allows you to store and manage Terraform state remotely and share across CI/CD pipelines. With this update, you can embed Keyper in your infrastructure as code workflows.
Our platform now supports reading and writing files, making it easier to manage your data workflows. Whether you need to read configurations or write out processed data, these new capabilities streamline your data management processes.
We’ve fixed a bug that affected retrieving keys by both ID and name. This fix ensures that you can now reliably access your keys, whether you’re using their unique ID or their assigned name. Check out our docs here.
We’ve released a free step-by-step tutorial that walks you through setting up the GCP service account and Terraform, creating and managing your encryption keys with Keyper, and encrypting a sample file with sensitive data on GCS identified by data vulnerability scans.
In our upcoming release, we’re introducing a custom vault for advanced crypto key management. This feature leverages the latest encryption techniques, allowing you to secure your data while still being able to leverage your data in analytics and AI/ML processes with minimal decryption overhead.
We’re also adding file metadata tracking, so you can easily track which keys were used to encrypt specific files. This will help you manage access and key rotation more efficiently.
At Jarrid, we aim to make data security more than just vulnerability scans or technical jargon — we want to make data security actionable. By simplifying complex encryption techniques, we empower non-security engineers to effectively protect their data.