a3dfde5cec
* conversion stage 1 * correct image paths * add sidebar title to frontmatter * docs/concepts and docs/internals * configuration docs and multi-level nav corrections * commands docs, index file corrections, small item nav correction * secrets converted * auth * add enterprise and agent docs * add extra dividers * secret section, wip * correct sidebar nav title in front matter for apu section, start working on api items * auth and backend, a couple directory structure fixes * remove old docs * intro side nav converted * reset sidebar styles, add hashi-global-styles * basic styling for nav sidebar * folder collapse functionality * patch up border length on last list item * wip restructure for content component * taking middleman hacking to the extreme, but its working * small css fix * add new mega nav * fix a small mistake from the rebase * fix a content resolution issue with middleman * title a couple missing docs pages * update deps, remove temporary markup * community page * footer to layout, community page css adjustments * wip downloads page * deps updated, downloads page ready * fix community page * homepage progress * add components, adjust spacing * docs and api landing pages * a bunch of fixes, add docs and api landing pages * update deps, add deploy scripts * add readme note * update deploy command * overview page, index title * Update doc fields Note this still requires the link fields to be populated -- this is solely related to copy on the description fields * Update api_basic_categories.yml Updated API category descriptions. Like the document descriptions you'll still need to update the link headers to the proper target pages. * Add bottom hero, adjust CSS, responsive friendly * Add mega nav title * homepage adjustments, asset boosts * small fixes * docs page styling fixes * meganav title * some category link corrections * Update API categories page updated to reflect the second level headings for api categories * Update docs_detailed_categories.yml Updated to represent the existing docs structure * Update docs_detailed_categories.yml * docs page data fix, extra operator page remove * api data fix * fix makefile * update deps, add product subnav to docs and api landing pages * Rearrange non-hands-on guides to _docs_ Since there is no place for these on learn.hashicorp, we'll put them under _docs_. * WIP Redirects for guides to docs * content and component updates * font weight hotfix, redirects * fix guides and intro sidenavs * fix some redirects * small style tweaks * Redirects to learn and internally to docs * Remove redirect to `/vault` * Remove `.html` from destination on redirects * fix incorrect index redirect * final touchups * address feedback from michell for makefile and product downloads
36 lines
1.6 KiB
Markdown
36 lines
1.6 KiB
Markdown
---
|
|
layout: "guides"
|
|
page_title: "Encryption as a Service - Guides"
|
|
sidebar_title: "Encryption as a Service"
|
|
sidebar_current: "guides-encryption"
|
|
description: |-
|
|
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 enable 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.
|
|
|
|
- [Encryption as a Service](/guides/encryption/transit.html) guide walks you
|
|
through the usage of the `transit` secrets engine in Vault.
|
|
Read this guide first before proceeding to the [Transit Secrets
|
|
Re-wrapping](/guides/encryption/transit-rewrap.html) guide or [Java Application
|
|
Demo](/guides/encryption/spring-demo.html) guide.
|
|
|
|
- [Java Application Demo](/guides/encryption/spring-demo.html) guide walks
|
|
through a sample application which relies on Vault to generate database
|
|
credentials as well as encrypting sensitive data. This guide is for anyone who
|
|
wishes to reproduce the demo introduced in
|
|
the [Manage secrets, access, and encryption in the public cloud with Vault](https://www.hashicorp.com/resources/solutions-engineering-webinar-series-episode-2-vault)
|
|
webinar.
|
|
|
|
- [Transit Secrets Re-wrapping](/guides/encryption/transit-rewrap.html) guide
|
|
demonstrates one possible way to re-wrap data after rotating an encryption key
|
|
in the transit engine in Vault.
|