Skip to content

secure-your-cluster-deployment.md

Latest commit

 

History

History
79 lines (57 loc) · 2.77 KB

secure-your-cluster-deployment.md

File metadata and controls

79 lines (57 loc) · 2.77 KB
Raw
applies_to
deployment serverless
self eck ece ess
ga
all
all
all
all
products
id
elasticsearch
id
kibana
id
cloud-hosted
id
cloud-enterprise
id
cloud-kubernetes
id
cloud-serverless
id
elastic-stack

Secure your cluster, deployment, or project

It's important to protect your {{es}} cluster and the data it contains. Implementing an in-depth defense strategy provides multiple layers of security to help safeguard your system.

:::{include} /deploy-manage/security/_snippets/complete-security.md :::

:::{important}

  • Never run an {{es}} cluster without security enabled. This principle cannot be overstated. Running {{es}} without security leaves your cluster exposed to anyone who can send network traffic to {{es}}, permitting these individuals to download, modify, or delete any data in your cluster.
  • Never try to run {{es}} as the root user, which would invalidate any defense strategy and permit a malicious user to do anything on your server. You must create a dedicated, unprivileged user to run {{es}}. By default, the rpm, deb, docker, and Windows packages of {{es}} contain an elasticsearch user with this scope. :::

:::{tip} You must secure other {{stack}} components, as well as client and integration communications, separately. :::

You can configure the following aspects of your Elastic cluster, deployment, or project to maintain and enhance security:

Initial security setup [manually-configure-security]

:::{include} /deploy-manage/security/_snippets/enable-security.md :::

Communication and network security

:::{include} /deploy-manage/security/_snippets/cluster-communication-network.md :::

Data security

:::{include} /deploy-manage/security/_snippets/cluster-data.md :::

User session security

:::{include} /deploy-manage/security/_snippets/cluster-user-session.md :::

Security event audit logging

:::{include} /deploy-manage/security/_snippets/audit-logging.md :::

FIPS 140-2 compliant mode

deployment:
  self:
  eck:

The Federal Information Processing Standard (FIPS) Publication 140-2, (FIPS PUB 140-2), titled "Security Requirements for Cryptographic Modules" is a U.S. government computer security standard used to approve cryptographic modules. You can run a self-managed cluster or {{eck}} cluster in FIPS-compliant mode:

% we need to refine this table, but the idea is awesome IMO

Security features by deployment type [comparison-table]

:::{include} /deploy-manage/security/_snippets/cluster-comparison.md :::