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
44 lines
1.8 KiB
Markdown
44 lines
1.8 KiB
Markdown
---
|
|
layout: "docs"
|
|
page_title: "HSM Integration - Vault Enterprise"
|
|
sidebar_title: "HSM Support"
|
|
sidebar_current: "docs-vault-enterprise-hsm"
|
|
description: |-
|
|
Vault Enterprise has HSM support, allowing for external master key storage and automatic unsealing.
|
|
|
|
---
|
|
|
|
# Vault Enterprise HSM Support
|
|
|
|
HSM support is a feature of [Vault
|
|
Enterprise](https://www.hashicorp.com/vault.html) that takes advantage of HSMs
|
|
to provide three pieces of special functionality:
|
|
|
|
* Master Key Wrapping: Vault protects its master key by transiting it through
|
|
the HSM for encryption rather than splitting into key shares
|
|
* Automatic Unsealing: Vault stores its HSM-wrapped master key in storage,
|
|
allowing for automatic unsealing
|
|
* [Seal Wrapping](/docs/enterprise/sealwrap/index.html) to provide FIPS
|
|
KeyStorage-conforming functionality for Critical Security Parameters
|
|
|
|
HSM support is available for devices that support PKCS#11 version 2.20+
|
|
interfaces and provide integration libraries, and is currently available for
|
|
linux/amd64 platforms only. It has successfully been tested against many
|
|
different vendor HSMs; HSMs that provide only subsets of the full PKCS#11
|
|
specification can usually be supported but it depends on available
|
|
cryptographic mechanisms.
|
|
|
|
Please note however that configuration details, flags, and supported features
|
|
within PKCS#11 vary depending on HSM model and configuration. Consult your
|
|
HSM's documentation for more details.
|
|
|
|
Some parts of Vault work differently when using an HSM. Please see the
|
|
[Behavioral Changes](/docs/enterprise/hsm/behavior.html) page for
|
|
important information on these differences.
|
|
|
|
The [Configuration](/docs/configuration/seal/pkcs11.html) page contains
|
|
configuration information.
|
|
|
|
Finally, the [Security](/docs/enterprise/hsm/security.html) page contains
|
|
information about deploying Vault's HSM support in a secure fashion.
|