2018-05-14 18:35:02 -04:00
|
|
|
[role="xpack"]
|
2017-04-06 21:29:29 -04:00
|
|
|
[[encrypting-communications]]
|
2018-05-14 18:35:02 -04:00
|
|
|
== Encrypting communications
|
2017-04-06 21:29:29 -04:00
|
|
|
|
|
|
|
Elasticsearch nodes store data that may be confidential. Attacks on the data may
|
|
|
|
come from the network. These attacks could include sniffing of the data,
|
|
|
|
manipulation of the data, and attempts to gain access to the server and thus the
|
2019-05-20 09:06:42 -04:00
|
|
|
files storing the data. Securing your nodes helps reduce the risk from
|
2018-12-19 17:53:37 -05:00
|
|
|
network-based attacks.
|
2017-04-06 21:29:29 -04:00
|
|
|
|
|
|
|
This section shows how to:
|
|
|
|
|
|
|
|
* Encrypt traffic to, from and within an Elasticsearch cluster using SSL/TLS,
|
|
|
|
* Require nodes to authenticate as they join the cluster using SSL certificates, and
|
|
|
|
* Make it more difficult for remote attackers to issue any commands to Elasticsearch.
|
|
|
|
|
|
|
|
The authentication of new nodes helps prevent a rogue node from joining the
|
|
|
|
cluster and receiving data through replication.
|
|
|
|
|
2019-10-04 16:11:05 -04:00
|
|
|
include::setting-up-ssl.asciidoc[]
|
2019-11-19 12:54:40 -05:00
|
|
|
include::securing-elasticsearch.asciidoc[]
|
|
|
|
include::configuring-tls-docker.asciidoc[]
|
|
|
|
include::enabling-cipher-suites.asciidoc[]
|
|
|
|
|