Skip to main content
Back to all releases
// November 13, 2026v1.52.1

Platform

Security and Policy

Organizations can bring their own encryption keys for data at rest

Organizations entitled to customer-managed encryption keys can now register and manage their own key in Google Cloud KMS, so data the platform stores for new features is encrypted under a key the organization controls rather than one Speakeasy manages alone. This is rolling out to entitled organizations; contact Speakeasy to turn it on.

Features

  • Manage a customer-managed encryption key from a new management API #8699 - Organizations entitled to customer-managed keys can register a GCP KMS symmetric key, verify it with a live encrypt-and-decrypt check, switch to it, roll a switch back, rotate a data key, and resume after a suspension. A key still protecting data can't be deleted, and a Speakeasy-managed key can never be deleted. Reads need org:read; changes need org:admin. (Author: @disintegrator)
  • New data gets its own per-organization encryption #8698 - Each organization now gets its own key-encryption key in KMS, wrapping a separate data-encryption key per feature that opts in. An hourly check suspends an organization whose key stops working and rolls back a key switch that failed, so a problem with an organization's own key fails closed instead of silently falling back to the platform's key. No existing data moves to this automatically. (Author: @disintegrator)
Sagar Batchu
Sagar Batchu
View on GitHub