WARNING: Version 5.6 of the Elastic Stack has passed its EOL date.

This documentation is no longer being maintained and may be removed. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.

« Auditing Security Events Setting Up SSL/TLS on a Cluster »
Elastic Docs ›X-Pack for the Elastic Stack [5.6] ›Securing Elasticsearch and Kibana

Encrypting Communications

edit

Encrypting Communications

edit

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 files storing the data. Securing your nodes with the procedures below helps to reduce risk from network-based attacks.

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.

« Auditing Security Events Setting Up SSL/TLS on a Cluster »