# Security of Keystores

**URL:** https://discuss.elastic.co/t/security-of-keystores/121884
**Category:** Beats
**Created:** [February 28, 2018, 3:58pm UTC](https://discuss.elastic.co/t/security-of-keystores/121884 "2018-02-28T15:58:22Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![Lazarbeam](https://avatars.discourse-cdn.com/v4/letter/l/e0b2c6/32.png) [@Lazarbeam](https://discuss.elastic.co/u/Lazarbeam)
#### Post date: [February 28, 2018, 3:58pm UTC](https://discuss.elastic.co/t/security-of-keystores/121884/1 "2018-02-28T15:58:22Z")

</div>

Team --

I'm running Filebeat and Metricbeat versions 6.2.2 on RHEL 5.11

I've followed the instructions on creating keystores for Filebeat and Metricbeat from the guides listed [here](https://www.elastic.co/guide/en/beats/filebeat/current/keystore.html) and [here](https://www.elastic.co/guide/en/beats/metricbeat/6.2/keystore.html). Everything works dandy - this is a great feature to NOT have passwords stored in plain text. That would never fly with our data security team.

Is it known the algorithm and strength of the key to secure the filebeat.keystore and metricbeat.keystore files? This will be important information for our data security team to understand precisely how secure the .keystore files are.

---

<div class="post-metadata">

### Author: ![adrisr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/adrisr/32/25423_2.png) [@adrisr](https://discuss.elastic.co/u/adrisr)
#### Post date: [February 28, 2018, 7:04pm UTC](https://discuss.elastic.co/t/security-of-keystores/121884/2 "2018-02-28T19:04:11Z")

</div>

Currently, the keystore is encrypted using the AES-256-GCM algorithm.

The key is derived from the password using HMAC-SHA-512 based PBKDF2 with 10000 iterations and a random salt and IV is used for every entry stored in the keystore.

Here's a link to the source code [https://github.com/elastic/beats/blob/master/libbeat/keystore/file\_keystore.go](https://github.com/elastic/beats/blob/master/libbeat/keystore/file_keystore.go)

---

<div class="post-metadata">

### Author: ![Lazarbeam](https://avatars.discourse-cdn.com/v4/letter/l/e0b2c6/32.png) [@Lazarbeam](https://discuss.elastic.co/u/Lazarbeam)
#### Post date: [February 28, 2018, 7:15pm UTC](https://discuss.elastic.co/t/security-of-keystores/121884/3 "2018-02-28T19:15:59Z")

</div>

This is exactly what I'm looking for. Thank you!

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [March 28, 2018, 9:16pm UTC](https://discuss.elastic.co/t/security-of-keystores/121884/4 "2018-03-28T21:16:02Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
