docs: add CipherStash vs HashiCorp Vault comparison#34
Draft
coderdan wants to merge 2 commits into
Draft
Conversation
Adds a Transit-scoped comparison built around the trilemma: no single Vault Transit configuration delivers plaintext-stays-client-side + per-record keys + bulk amortization at once, while ZeroKMS does. Covers Transit's direct vs envelope (datakey) modes, the scattered-read reuse collapse (explained inline), and the trust/capability differences. Performance section is qualitative pending the in-region vault-transit benchmark. Claude-Session: https://claude.ai/code/session_018ag38k33yzmVZhLkVx7CPQ
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Vault's transit/decrypt is batched, so a scattered read unwraps all distinct data keys in one round-trip — it does NOT collapse the way AWS KMS does. The real cost of per-record keys in Vault envelope mode lands on WRITES (datakey has no batch API = one round-trip per record), and the cost of reuse is the security model (shared key, lost per-record audit/revocation). Retitle 'Why the reuse row collapses' -> 'Reading the table' and rewrite accordingly; fix the plaintext and performance notes to match. Claude-Session: https://claude.ai/code/session_018ag38k33yzmVZhLkVx7CPQ
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of CIP-3290 (issue stays open until the doc, backend, and in-region run all land)
Adds a new comparison page: CipherStash vs HashiCorp Vault, scoped to Vault's Transit secrets engine (the encryption-as-a-service analog to ZeroKMS).
What it adds
comparisons/hashicorp-vault.mdx— the doc, registered inmeta.jsonand the overviewindex.mdxcards.datakeymode (plaintext client-side, one key per call), and the scattered-read reuse collapse (explained inline, so the page is self-contained).Draft status
TODOmarks where in-region numbers go once thevault-transitbackend lands incipherstash/benches(kms-app).Notes
main; the AWS KMS data-key-caching/cost sections referenced conceptually live in the separate open PR docs: add ZeroKMS vs HSM comparison + merge Cloud KMS into AWS KMS #31, so this page does not depend on that anchor.https://claude.ai/code/session_018ag38k33yzmVZhLkVx7CPQ