Why security protects sensitive data in Elasticsearch - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to enable security in Elasticsearch.

Elasticsearch

xpack.security.enabled: [1]

Drag options to blanks, or click blank then click option'

Ano

Bfalse

Cyes

Dtrue

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'false' disables security.

Using 'yes' or 'no' are not valid boolean values here.

Setting xpack.security.enabled to true activates security features in Elasticsearch.

2fill in blank

medium

Complete the code to set a password for the built-in user.

Elasticsearch

bin/elasticsearch-setup-passwords [1]

Drag options to blanks, or click blank then click option'

Adefault

Binteractive

Cmanual

Dauto

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'auto' sets random passwords without prompts.

Using 'manual' is not a valid option.

The interactive option lets you set passwords manually for built-in users.

3fill in blank

hard

Fix the error in the role definition to allow reading data.

Elasticsearch

"read_data": {
  "cluster": ["monitor"],
  "indices": [
    {
      "names": ["*"],
      "privileges": ["[1]"]
    }
  ]
}

Drag options to blanks, or click blank then click option'

Awrite

Bdelete

Cread

Dall

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'write' does not allow reading data.

Using 'all' grants too many permissions.

The privilege read allows users to read data from indices.

4fill in blank

hard

Fill both blanks to create a user with the 'read_data' role and a password.

Elasticsearch

POST /_security/user/[1]
{
  "password": "[2]",
  "roles": ["read_data"]
}

Drag options to blanks, or click blank then click option'

Aalice

Bsecret123

Cpassword

Dbob

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'bob' as username but 'password' as password is weak.

Leaving password blank or too simple.

The username is 'alice' and the password is 'secret123' to create a secure user.

5fill in blank

hard

Fill all three blanks to configure TLS for the HTTP layer.

Elasticsearch

xpack.security.http.ssl:
  enabled: [1]
  key: [2]
  certificate: [3]

Drag options to blanks, or click blank then click option'

Afalse

B/etc/elasticsearch/certs/http.key

C/etc/elasticsearch/certs/http.crt

Dtrue

Attempts:

3 left

💡 Hint

Common Mistakes

Setting enabled to false disables TLS.

Using wrong file paths causes errors.

Enable TLS with true, and provide the key and certificate file paths.