WARNING: Version 5.1 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.

« Securing Elasticsearch and Kibana How Security Works »

› ›

Getting Started with Security

edit

Getting Started with Security

edit

To secure a cluster, you must install X-Pack on every node in the cluster. Basic authentication is enabled by default—to communicate with the cluster, you must specify a username and password. Unless you enable anonymous access, all requests that don’t include a user name and password are rejected.

X-Pack security provides a built-in elastic superuser you can use to start setting things up. This elastic user has full access to the cluster, including all indices and data, so make sure you change the default password and protect the elastic user credentials accordingly.

To get started with X-Pack security:

Install X-Pack and start Elasticsearch and Kibana.

Change the passwords of the built in kibana and elastic users:

curl -XPUT -u elastic 'localhost:9200/_xpack/security/user/elastic/_password' -d '{
  "password" : "elasticpassword"
}'

curl -XPUT -u elastic 'localhost:9200/_xpack/security/user/kibana/_password' -d '{
  "password" : "kibanapassword"
}'

The default password for the elastic user is changeme.

Set up roles and users to control access to Elasticsearch and Kibana. For example, to grant John Doe full access to all indices that match the pattern events* and enable him to create visualizations and dashboards for those indices in Kibana, you could create an events_admin role and and assign the role to a new johndoe user.

curl -XPOST -u elastic 'localhost:9200/_xpack/security/role/events_admin' -d '{
  "indices" : [
    {
      "names" : [ "events*" ],
      "privileges" : [ "all" ]
    },
    {
      "names" : [ ".kibana*" ],
      "privileges" : [ "manage", "read", "index" ]
    }
  ]
}'

curl -XPOST -u elastic 'localhost:9200/_xpack/security/user/johndoe' -d '{
  "password" : "userpassword",
  "full_name" : "John Doe",
  "email" : "[email protected]",
  "roles" : [ "events_admin" ]
}'

Enable message authentication to verify that messages are not tampered with or corrupted in transit:
1. Run the syskeygen tool from ES_HOME without any options:
```
bin/x-pack/syskeygen
```
  This creates a system key file in CONFIG_DIR/x-pack/system_key.
2. Copy the generated system key to the rest of the nodes in the cluster.
  
  The system key is a symmetric key, so the same key must be on every node in the cluster.

Enable Auditing to keep track of attempted and successful interactions with your Elasticsearch cluster:
1. Add the following setting to elasticsearch.yml on all nodes in your cluster:
```
xpack.security.audit.enabled: true
```
2. Restart Elasticsearch.
By default, events are logged to a dedicated elasticsearch-access.log file in ES_HOME/logs. You can also store the events in an Elasticsearch index for easier analysis and control what events are logged. For more information, see Configuring Auditing.

Once you get these basic security measures in place, we strongly recommend that you secure communications to and from nodes by configuring your cluster to use SSL/TLS encryption. Nodes that do not have encryption enabled send passwords in plain text!

Depending on your security requirements, you might also want to:

Integrate with LDAP or Active Directory, or require certificates for authentication.
Use IP Filtering to allow or deny requests from particular IP addresses or address ranges.

« Securing Elasticsearch and Kibana How Security Works »