| applies_to | mapped_pages | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
An Elastic implementation comprises many moving parts: {{es}} nodes forming the cluster, {{kib}} instances, additional stack components such as Logstash and Beats, and various clients and integrations, all communicating with your cluster.
To keep your data secured, Elastic offers security features that prevent bad actors from tampering with your data, and encrypt communications to, from, and within your cluster. Regardless of your deployment type, Elastic sets up certain security features for you automatically.
The availability and configurability of security features vary by deployment type. On every page, you'll see deployment type indicators that show which content applies to specific deployment types. Focus on sections tagged with your deployment type and look for subsections specifically addressing your deployment model. You can also review a comparison table showing feature availability and configurability by deployment type.
:::{include} /deploy-manage/security/_snippets/complete-security.md :::
deployment:
ess: all
serverless: all:::{include} /deploy-manage/_snippets/ecloud-security.md :::
::::{note} Serverless projects are fully managed and secured by Elastic, and do not have any configurable Security features at the project level. ::::
deployment:
ece: all
eck: allWhen running {{stack}} applications on {{ece}} or {{eck}}, you must also secure the orchestration layer responsible for deploying and managing your Elastic products.
Learn about securing the following components:
:::{tip} Elastic secures your {{ecloud}} orchestrator for you. :::
deployment:
ece: all
eck: all
ess: all
self: allYou can configure the following aspects of your Elastic cluster or deployment to maintain and enhance security:
:::{include} /deploy-manage/security/_snippets/enable-security.md :::
:::{include} /deploy-manage/security/_snippets/cluster-communication-network.md :::
:::{include} /deploy-manage/security/_snippets/cluster-data.md :::
:::{include} /deploy-manage/security/_snippets/cluster-user-session.md :::
:::{include} /deploy-manage/security/_snippets/audit-logging.md :::
% missing: fips mode, manual config
% we need to refine this table, but the idea is awesome IMO
:::{include} /deploy-manage/security/_snippets/cluster-comparison.md :::
The {{es}} security features enable you to secure your {{es}} cluster. However, for a complete security strategy, you must secure other applications in the {{stack}}, as well as communications between {{es}} and other {{stack}} components.
Review security topics for other {{stack}} components.
If you use HTTP clients or integrations to communicate with {{es}}, then you also need to secure communications between the clients or integrations and {{es}}.
There are security limitations that apply to the usage of some {{es}} features or resources. Depending on your organization's security requirements, you might want to restrict, adjust, or find workaround or alternatives for some of these features and resources.