/docs/security
This commit is contained in:
parent
b560dbefd5
commit
6d0f7c2857
|
@ -1,10 +1,8 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Encryption
|
||||
page_title: Encryption Systems
|
||||
description: >-
|
||||
The Consul agent supports encrypting all of its network traffic. The exact
|
||||
method of encryption is described on the encryption internals page. There are
|
||||
two separate encryption systems, one for gossip traffic and one for RPC.
|
||||
Two encryption systems protect Consul’s network communications. Learn how keys secure gossip between agents and how RPC with TLS certificates verifies the authenticity of servers and clients.
|
||||
---
|
||||
|
||||
# Encryption
|
||||
|
|
|
@ -1,12 +1,8 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Security
|
||||
page_title: Security: Overview
|
||||
description: >-
|
||||
Consul relies on both a lightweight gossip mechanism and an RPC system to
|
||||
provide various features. Both of the systems have different security
|
||||
mechanisms that stem from their designs. However, the security mechanisms of
|
||||
Consul have a common goal: to provide confidentiality, integrity, and
|
||||
authentication.
|
||||
Security requirements and recommendations for Consul vary depending on workloads and environments. Learn how ACLs and encryption can protect access to and communication within your datacenter.
|
||||
---
|
||||
|
||||
## Security Models
|
||||
|
|
Loading…
Reference in a new issue