luxolus
/
open-vault
2
0
Fork 0
Code Issues 1 Pull Requests Releases Activity

Update index.html.md

This commit is contained in:
Andy Manoske 2018-08-15 17:44:36 -07:00 committed by GitHub
parent 9d41d4c407
commit bd4c047713
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
website/source/docs/enterprise/namespaces/index.html.md
View File

@ -18,6 +18,7 @@ organization operate within self-contained environments known as "*tenants*."
There are two common challenges when implementing this architecture in Vault: There are two common challenges when implementing this architecture in Vault:
**Tenant Isolation** **Tenant Isolation**
Frequently teams within a VaaS environment require strong isolation from other Frequently teams within a VaaS environment require strong isolation from other
users in their policies, secrets, and sometimes even their own identity entities users in their policies, secrets, and sometimes even their own identity entities
and groups. Frequently tenant isolation is a result of regulations such as [GDPR](https://www.eugdpr.org/), and groups. Frequently tenant isolation is a result of regulations such as [GDPR](https://www.eugdpr.org/),
@ -25,6 +26,7 @@ though it may be necessitated by corporate or organizational infosec requirement
well. well.
**Self-Management** **Self-Management**
As new tenants are added, there is an additional human cost in the 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 overhead for teams. Given that tenants will likely have different policies and
request changes at a different rate, managing a multi-tenant environment can request changes at a different rate, managing a multi-tenant environment can