[role="xpack"]
[[security-clients-integrations]]
== Securing clients and integrations

You will need to update the configuration for several <<http-clients,clients>>
to work with a secured {es} cluster.

The {es} {security-features} enable you to secure your {es} cluster. But
{es} itself is only one product within the {stack}. It is often the case that
other products in the {stack} are connected to the cluster and therefore need to
be secured as well, or at least communicate with the cluster in a secured way:

* <<hadoop, Apache Hadoop>>
* {auditbeat-ref}/securing-auditbeat.html[Auditbeat]
* {filebeat-ref}/securing-filebeat.html[Filebeat]
* {heartbeat-ref}/securing-heartbeat.html[Heartbeat]
* {kibana-ref}/using-kibana-with-security.html[{kib}]
* {logstash-ref}/ls-security.html[Logstash]
* {metricbeat-ref}/securing-metricbeat.html[Metricbeat]
* <<secure-monitoring>>
* {packetbeat-ref}/securing-packetbeat.html[Packetbeat]
* {kibana-ref}/secure-reporting.html[Reporting]
* {winlogbeat-ref}/securing-winlogbeat.html[Winlogbeat]

include::http.asciidoc[]

include::java.asciidoc[]

include::hadoop.asciidoc[]

include::monitoring.asciidoc[]
