mirror of
https://github.com/hashicorp/vault.git
synced 2025-08-24 08:01:07 +02:00
5c5586759f
* Adding new guides * Replaced backend with engine * Grammar for the encryption guide * Grammar and Markdown style for the Transite Rewrap guide See https://github.com/hashicorp/engineering-docs/blob/master/writing/markdown.md for notes on numbered Markdown lists. * grammar and wording updates for ref arch guide * Updating replication diagram * Removing multi-tenant pattern guide * Added a note 'Enterprise Only' * Removing multi-tenant pattern guide * Modified the topic order * Grammar and Markdown formatting * Grammar, Markdown syntax, and phrasing * Grammar and Markdown syntax * Replaced 'backend' with appropriate terms * Added a note clarifying that replication is an enterprise-only feature * Updated the diagram & added additional resource links * update some grammar and ordering * Removed the inaccurate text in index for EaaS
858 B
858 B
layout, page_title, sidebar_current, description
| layout | page_title | sidebar_current | description |
|---|---|---|---|
| guides | Encryption as a Service - Guides | guides-encryption | The transit secrets engine handles cryptographic functions on data in-transit. Vault doesn't store the data sent to the secrets engine. It can also be viewed as "cryptography as a service" or "encryption as a service". |
Encryption as a Service
Vault provides Encryption as a Service (EaaS) to enables security teams to fortify data during transit and at rest. So even if an intrusion occurs, your data is encrypted and the attacker would never get a hold of the raw data.
This guide walks you through Encryption as a Service topics.
- Transit Secrets Re-wrapping guide demonstrates one possible way to re-wrap data after rotating an encryption key in the transit engine in Vault.