Bring-your-own-key is table stakes for regulated data — except in agentic AI, where most platforms still hold the keys for you. Reframe Harness is built BYOK-first.
How the KMS integration works
At boot the harness reads a customer-supplied KMS configuration: provider (AWS KMS, GCP KMS, Azure Key Vault, on-prem HSM), key arn, IAM identity. The harness never stores keys, never imports keys, and never falls back to a Reframe-managed key on failure.
- Envelope encryption — every piece of regulated data is wrapped in a per-row data encryption key (DEK) encrypted by your KMS root.
- Just-in-time decryption — DEKs are decrypted only inside the harness process, in memory, for the lifetime of a single call.
- Audit attribution — every decrypt is recorded with the KMS key id, the IAM identity, the user, the agent, and the prompt fingerprint. The audit bundle goes to your audit store, not ours.
- Plaintext guarantees — plaintext never written to disk, never written to logs, never sent over a wire without TLS to a customer-controlled endpoint.
What this means in practice
Your CISO can answer "where do the keys live?" with one word: here. Your auditor can answer "who decrypted what?" with one query against your own KMS audit log. Your legal team can answer data-residency obligations because the key material literally cannot leave your region.
Compliance mappings
BYOK in this configuration satisfies the cryptographic-control requirements of SOC 2 CC6.7, ISO 27001 Annex A 8.24, NIST AI RMF GOVERN-1.6, EU AI Act Article 15 (cybersecurity), and the data-residency commitments most regulated firms have made to their own customers.