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
45 lines
2.2 KiB
Markdown
45 lines
2.2 KiB
Markdown
---
|
|
layout: "docs"
|
|
page_title: "Vault vs. Keywhiz"
|
|
sidebar_title: "Keywhiz"
|
|
sidebar_current: "vs-other-keywhiz"
|
|
description: |-
|
|
Comparison between Vault and Keywhiz.
|
|
---
|
|
|
|
# Vault vs. Keywhiz
|
|
|
|
Keywhiz is a secret management solution built by Square. Keywhiz has a
|
|
client/server architecture based on a RESTful API. Clients of Keywhiz access
|
|
secrets through the API by authenticating with a client certificate or cookie.
|
|
To allow for flexible consumption of secrets by arbitrary software, clients may
|
|
also make use of a FUSE filesystem to expose secrets as files on disk, and use
|
|
Unix file permissions for access control. Human operators may authenticate
|
|
using a cookie-based authentication either via command line utilities or
|
|
through a management web interface.
|
|
|
|
Vault similarly is designed as a comprehensive secret management solution. The
|
|
client interaction with Vault is flexible both for authentication and usage of
|
|
secrets. Vault supports [mTLS authentication](/docs/auth/cert.html) along with
|
|
many [other mechanisms](/docs/auth/index.html). The goal is to make it easy
|
|
to authenticate as a machine for programmatic access and as a human for
|
|
operator usage.
|
|
|
|
Vault and Keywhiz expose secrets via an API. The Vault [ACL
|
|
system](/docs/concepts/policies.html) is used to protect secrets and gate
|
|
access, similarly to the Keywhiz ACL system. With Vault, all auditing is done
|
|
server side using [audit devices](/docs/audit/index.html).
|
|
|
|
Keywhiz focuses on storage and distribution of secrets and supports rotation
|
|
through secret versioning, which is possible in the Keywhiz UI and command-line
|
|
utilities. Vault also supports dynamic secrets and generating credentials
|
|
on-demand for fine-grained security controls, but adds first class support for
|
|
non-repudiation. Key rotation is a first class concern for Keywhiz and Vault,
|
|
so that no external systems need to be used.
|
|
|
|
Lastly, Vault forces a mandatory lease contract with clients. All secrets read
|
|
from Vault have an associated lease which enables operators to audit key usage,
|
|
perform key rolling, and ensure automatic revocation. Vault provides multiple
|
|
revocation mechanisms to give operators a clear "break glass" procedure after a
|
|
potential compromise.
|