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
70 lines
2.8 KiB
Markdown
70 lines
2.8 KiB
Markdown
---
|
|
layout: "docs"
|
|
page_title: "Namespaces - Vault Enterprise"
|
|
sidebar_title: "Namespaces"
|
|
sidebar_current: "docs-vault-enterprise-namespaces"
|
|
description: |-
|
|
Vault Enterprise has support for Namespaces, a feature to enable Secure Multi-tenancy (SMT) and self-management.
|
|
|
|
---
|
|
|
|
# Vault Enterprise Namespaces
|
|
|
|
## Overview
|
|
|
|
Many organizations implement Vault as a "service", providing centralized
|
|
management for teams within an organization while ensuring that those teams
|
|
operate within isolated environments known as *tenants*.
|
|
|
|
There are two common challenges when implementing this architecture in Vault:
|
|
|
|
**Tenant Isolation**
|
|
|
|
Frequently teams within a VaaS environment require strong isolation from other
|
|
users in their policies, secrets, and identities. Tenant isolation is typically a
|
|
result of compliance regulations such as [GDPR](https://www.eugdpr.org/), though it may
|
|
be necessitated by corporate or organizational infosec requirements.
|
|
|
|
**Self-Management**
|
|
|
|
As new tenants are added, there is an additional human cost in the management
|
|
overhead for teams. Given that tenants will likely have different policies and
|
|
request changes at a different rate, managing a multi-tenant environment can
|
|
become very difficult for a single team as the number of tenants within that
|
|
organization grow.
|
|
|
|
'Namespaces' is a set of features within Vault Enterprise that allows Vault
|
|
environments to support *Secure Multi-tenancy* (or *SMT*) within a single Vault
|
|
infrastructure. Through namespaces, Vault administrators can support tenant isolation
|
|
for teams and individuals as well as empower delegated administrators to manage their
|
|
own tenant environment.
|
|
|
|
## Architecture
|
|
|
|
Namespaces are isolated environments that functionally exist as "Vaults within a Vault."
|
|
They have separate login paths and support creating and managing data isolated to their
|
|
namespace. This data includes the following:
|
|
|
|
- Secret Engines
|
|
- Auth Methods
|
|
- Policies
|
|
- Identities (Entities, Groups)
|
|
- Tokens
|
|
|
|
Rather than rely on Vault system admins, namespaces can be managed by delegated admins who
|
|
can be prescribed administration rights for their namespace. These delegated admins can also
|
|
create their own child namespaces, thereby prescribing admin rights on a subordinate group
|
|
of delegate admins.
|
|
|
|
Child namespaces can share policies from their parent namespaces. For example, a child namespace
|
|
may refer to parent identities (entities and groups) when writing policies that function only
|
|
within that child namespace. Similarly, a parent namespace can have policies asserted on child
|
|
identities.
|
|
|
|
## Setup and Best Practices
|
|
|
|
A [deployment guide](/guides/operations/multi-tenant.html) is available to help guide you
|
|
through the deployment and administration of namespaces, and contains examples on architecture
|
|
for using namespaces to implement SMT across your organization.
|
|
|