Elastic Security requirements

The Support Matrix page lists officially supported operating systems, platforms, and browsers on which components such as Beats, Elastic Agent, Elastic Defend, and Elastic Endpoint have been tested.

Elastic Stack

Elastic Security is an inbuilt part of Kibana. To use Elastic Security, you only need an Elastic Stack deployment (an Elasticsearch cluster and Kibana). Review the Elastic Stack subscriptions page to understand the required subscription plans for all features.

Elastic Cloud offers all of the features of Elasticsearch, Kibana, and Elastic Security as a hosted service available on AWS, GCP, and Azure. To get started, sign up for a free Elastic Cloud trial.

For information about installing and managing the Elastic Stack yourself, see Installing the Elastic Stack.

Elastic Stack

To use Elastic Security, at least one node in your Elasticsearch cluster must have the transform role. Nodes are automatically given this role when they’re created, so changes are not required if default role settings remain the same. This applies to on-premise and cloud deployments.

Changes might be required if your nodes have customized roles. When updating node roles, nodes are only assigned the roles you specify, and default roles are removed. If you need to reassign the transform role to a node, create a dedicated transform node.

To use Elastic Security, your role must have at least:

• Read privilege for the Security feature in the space. This grants you Read access to all features in Elastic Security except cases. You need additional minimum privileges to use cases.
• Read and view_index_metadata privileges for all Elastic Security indices, such as filebeat-*, packetbeat-*, logs-*, and endgame-* indices.

For more information about index privileges, refer to Elasticsearch security privileges.

There are some additional requirements for specific features:

• Detections requirements
• Cases requirements
• Entity risk scoring requirements
• Machine learning job and rule requirements
• Elastic Defend requirements
• Configure network map data

Configure advanced settings describes how to modify advanced settings, such as the Elastic Security indices, default time intervals used in filters, and IP reputation links.

The Elastic Common Schema (ECS) defines a common set of fields to be used for storing event data in Elasticsearch. ECS helps users normalize their event data to better analyze, visualize, and correlate the data represented in their events. Elastic Security can ingest and normalize events from any ECS-compliant data source.

Elastic Stack

For information on how to perform cross-cluster searches on Elastic Security indices, see:

• Search across cluster (for self-managed Elastic Stack deployments)
• Enable cross-cluster search (for hosted deployments)