Skip to content

Commit aa74f02

Browse files
schavisschavis
authored
suggested edits (#1121)
1 parent 90aae38 commit aa74f02

File tree

7 files changed

+109
-100
lines changed

7 files changed

+109
-100
lines changed

‎content/vault/v1.19.x/content/docs/deploy/secure-cluster-with-tls.mdx‎

Lines changed: 0 additions & 41 deletions
This file was deleted.

‎content/vault/v1.19.x/content/docs/deploy/why-use-tls.mdx‎

Lines changed: 50 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,50 @@
1+
---
2+
layout: docs
3+
page_title: Why use TLS?
4+
description: >-
5+
Understand the benefits of securing your Vault clusters with end-to-end TLS.
6+
---
7+
8+
# Why use TLS?
9+
10+
You can enhance the overall security posture of your Vault cluster when you
11+
secure communications with TLS to ensure that data transmitted between Vault
12+
nodes and clients remains confidential and tamper-proof.
13+
14+
@include 'ld-images/deploy/secure-vault-tls.mdx'
15+
16+
Use mutual TLS with your Vault cluster deployments to protect sensitive data and
17+
prevent unauthorized access with enhanced compliance, governance, auditing
18+
capabilities, and incident response.
19+
20+
## TLS benefits
21+
22+
- **Improved data protection**.
23+
TLS prevents unauthorized access or communication with the Vault cluster to
24+
ensure data availability based on your security policies. TLS also protects
25+
sensitive data in transit to prevent interception or tampering.
26+
27+
- **Strong identity verification**.
28+
Vault cluster nodes and clients verify identities from TLS certificates before
29+
communicating to enable trusted operations and prevent impersonation.
30+
31+
- **Improved compliance and governance**.
32+
Implementing mutual TLS in your Vault clusters aligns your deployments with
33+
industry best practices and regulatory requirements like HIPAA, PCI-DSS, and
34+
others.
35+
36+
- **Reduce risk of data leaks**.
37+
When you operate Vault clusters with mutual TLS enabled, you minimize the risk
38+
of data leaks and unauthorized access to sensitive information.
39+
40+
- **Improved incident response**.
41+
Mutual TLS helps to limit the exposure or damage from unauthorized access to
42+
sensitive data stored in Vault, which makes incident response more
43+
straightforward.
44+
45+
## TLS resources
46+
47+
- [Default Vault TLS configuration](/vault/docs/configuration/listener/tcp#default-tls-configuration)
48+
- [Configure TLS for your Vault TCP listener](/vault/docs/configuration/listener/tcp/tcp-tls)
49+
- [Vault installation to minikube via Helm with TLS enabled](/vault/tutorials/kubernetes/kubernetes-minikube-tls)
50+
- [Medium blog: Enabling TLS on your Vault cluster on Kubernetes](https://medium.com/@martin.hodges/enabling-tls-on-your-vault-cluster-on-kubernetes-0d20439b13d0)

‎content/vault/v1.19.x/data/docs-nav-data.json‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -667,12 +667,12 @@
667667
"title": "Deploy Vault",
668668
"routes": [
669669
{
670-
"title": "Run as a service",
671-
"path": "deploy/run-as-service"
670+
"title": "Why use TLS?",
671+
"path": "deploy/why-use-tls"
672672
},
673673
{
674-
"title": "Secure cluster with TLS",
675-
"path": "deploy/secure-cluster-with-tls"
674+
"title": "Run as a service",
675+
"path": "deploy/run-as-service"
676676
},
677677
{
678678
"title": "Run on AWS",

‎content/vault/v1.20.x/content/docs/deploy/secure-cluster-with-tls.mdx‎

Lines changed: 0 additions & 41 deletions
This file was deleted.

‎content/vault/v1.20.x/content/docs/deploy/why-use-tls.mdx‎

Lines changed: 50 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,50 @@
1+
---
2+
layout: docs
3+
page_title: Why use TLS?
4+
description: >-
5+
Understand the benefits of securing your Vault clusters with end-to-end TLS.
6+
---
7+
8+
# Why use TLS?
9+
10+
You can enhance the overall security posture of your Vault cluster when you
11+
secure communications with TLS to ensure that data transmitted between Vault
12+
nodes and clients remains confidential and tamper-proof.
13+
14+
@include 'ld-images/deploy/secure-vault-tls.mdx'
15+
16+
Use mutual TLS with your Vault cluster deployments to protect sensitive data and
17+
prevent unauthorized access with enhanced compliance, governance, auditing
18+
capabilities, and incident response.
19+
20+
## TLS benefits
21+
22+
- **Improved data protection**.
23+
TLS prevents unauthorized access or communication with the Vault cluster to
24+
ensure data availability based on your security policies. TLS also protects
25+
sensitive data in transit to prevent interception or tampering.
26+
27+
- **Strong identity verification**.
28+
Vault cluster nodes and clients verify identities from TLS certificates before
29+
communicating to enable trusted operations and prevent impersonation.
30+
31+
- **Improved compliance and governance**.
32+
Implementing mutual TLS in your Vault clusters aligns your deployments with
33+
industry best practices and regulatory requirements like HIPAA, PCI-DSS, and
34+
others.
35+
36+
- **Reduce risk of data leaks**.
37+
When you operate Vault clusters with mutual TLS enabled, you minimize the risk
38+
of data leaks and unauthorized access to sensitive information.
39+
40+
- **Improved incident response**.
41+
Mutual TLS helps to limit the exposure or damage from unauthorized access to
42+
sensitive data stored in Vault, which makes incident response more
43+
straightforward.
44+
45+
## TLS resources
46+
47+
- [Default Vault TLS configuration](/vault/docs/configuration/listener/tcp#default-tls-configuration)
48+
- [Configure TLS for your Vault TCP listener](/vault/docs/configuration/listener/tcp/tcp-tls)
49+
- [Vault installation to minikube via Helm with TLS enabled](/vault/tutorials/kubernetes/kubernetes-minikube-tls)
50+
- [Medium blog: Enabling TLS on your Vault cluster on Kubernetes](https://medium.com/@martin.hodges/enabling-tls-on-your-vault-cluster-on-kubernetes-0d20439b13d0)

‎content/vault/v1.20.x/content/partials/ld-images/deploy/secure-vault-tls.mdx‎

Lines changed: 1 addition & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,2 @@
1-
<ImageConfig hideBorder>
2-
31
![Secure Vault intra-cluster and inter-cluster communications with TLS](/img/diagram-secure-vault-tls-dark.png#dark-theme-only)
4-
5-
</ImageConfig>
6-
7-
<ImageConfig hideBorder>
8-
9-
![Secure Vault intra-cluster and inter-cluster communications with TLS](/img/diagram-secure-vault-tls.png#light-theme-only)
10-
11-
</ImageConfig>
2+
![Secure Vault intra-cluster and inter-cluster communications with TLS](/img/diagram-secure-vault-tls.png#light-theme-only)

‎content/vault/v1.20.x/data/docs-nav-data.json‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -712,12 +712,12 @@
712712
"title": "Deploy Vault",
713713
"routes": [
714714
{
715-
"title": "Run as a service",
716-
"path": "deploy/run-as-service"
715+
"title": "Why use TLS?",
716+
"path": "deploy/why-use-tls"
717717
},
718718
{
719-
"title": "Secure cluster with TLS",
720-
"path": "deploy/secure-cluster-with-tls"
719+
"title": "Run as a service",
720+
"path": "deploy/run-as-service"
721721
},
722722
{
723723
"title": "Run on AWS",

0 commit comments

Comments
 (0)