Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Backport of Potentially Malicious Link into release/1.13.x #20124

Merged
merged 3 commits into from
Apr 12, 2023
Merged

Backport of Potentially Malicious Link into release/1.13.x #20124

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
03f4f2a
backport of commit 070082c2de056bbc03332be2f538af248aa65990
king-jam Apr 12, 2023
1dc4f03
Delete 20114.txt
cipherboy Apr 12, 2023
0b07e5a
Merge branch 'release/1.13.x' into backport/patch-1/conversely-notabl…
cipherboy Apr 12, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion website/content/docs/enterprise/namespaces.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ There are two common challenges when implementing this architecture in Vault:

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
result of compliance regulations such as [GDPR](https://gdpr.eu/), though it may
be necessitated by corporate or organizational infosec requirements.

**Self-Management**
Expand Down