# Encrypted Indices?

**URL:** <https://discuss.elastic.co/t/encrypted-indices/16341>\
**Category:** Elasticsearch\
**Created:** [March 13, 2014, 12:18am UTC](https://discuss.elastic.co/t/encrypted-indices/16341 "2014-03-13T00:18:04Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Parag\_Shah](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/parag_shah/32/44836_2.png) [@Parag\_Shah](https://discuss.elastic.co/u/Parag_Shah)\
**Post date:** [March 13, 2014, 12:18am UTC](https://discuss.elastic.co/t/encrypted-indices/16341/1 "2014-03-13T00:18:04Z")

</div>

Hi all,

```
I know ElasticSearch does not support encrypting indices. Has anyone 

```

built something on top of ElasticSearch or modified ElasticSearch to  
achieve encrypted indices? Would like to hear stories of how it went and  
how the performance is.

Thanks in advance  
Parag

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/7ae652b8-50aa-4e6c-8621-ab0e867068c3%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/7ae652b8-50aa-4e6c-8621-ab0e867068c3%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![andrew](https://avatars.discourse-cdn.com/v4/letter/a/f19dbf/32.png) [@andrew](https://discuss.elastic.co/u/andrew)\
**Post date:** [March 13, 2014, 2:19am UTC](https://discuss.elastic.co/t/encrypted-indices/16341/2 "2014-03-13T02:19:35Z")

</div>

Hi Parag,

I have seen a few implementations of encrypted Lucene indices, but they are largely experimental from what I can tell. There are no Elasticsearch implementations as far as I know.

If you require strong encryption your best bet is to store your Elasticsearch indices on an encrypted filesystem.

Best,  
Andrew

On Mar 12, 2014, at 5:18 PM, Parag Shah [parags@gmail.com](mailto:parags@gmail.com) wrote:

> Hi all,
> 
> ```
> I know ElasticSearch does not support encrypting indices. Has anyone built something on top of ElasticSearch or modified ElasticSearch to achieve encrypted indices? Would like to hear stories of how it went and how the performance is.
> 
> ```
> 
> Thanks in advance  
> Parag
> 
> --  
> You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
> To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/7ae652b8-50aa-4e6c-8621-ab0e867068c3%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/7ae652b8-50aa-4e6c-8621-ab0e867068c3%40googlegroups.com).  
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/5EE4D14D-38EB-4745-8904-38A65DC819CB%40elasticsearch.com](https://groups.google.com/d/msgid/elasticsearch/5EE4D14D-38EB-4745-8904-38A65DC819CB%40elasticsearch.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![Ivan](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@Ivan](https://discuss.elastic.co/u/Ivan)\
**Post date:** [March 13, 2014, 5:03am UTC](https://discuss.elastic.co/t/encrypted-indices/16341/3 "2014-03-13T05:03:10Z")

</div>

If you stick to non-analyzed term queries, you can always encrypt your data  
before it is index and then encrypt the query terms that are to be matched.  
The hashes of the terms will match, but if you use one-way hashing, the  
original data representation cannot be recovered. Somewhat kludgy and the  
burden of maintaining the hash key is now simply at another layer.

--  
Ivan

On Wed, Mar 12, 2014 at 7:19 PM, Andrew Selden \<  
[andrew.selden@elasticsearch.com](mailto:andrew.selden@elasticsearch.com)\> wrote:

> Hi Parag,
> 
> I have seen a few implementations of encrypted Lucene indices, but they  
> are largely experimental from what I can tell. There are no Elasticsearch  
> implementations as far as I know.
> 
> If you require strong encryption your best bet is to store your  
> Elasticsearch indices on an encrypted filesystem.
> 
> Best,  
> Andrew
> 
> On Mar 12, 2014, at 5:18 PM, Parag Shah [parags@gmail.com](mailto:parags@gmail.com) wrote:
> 
> Hi all,
> 
> ```
> I know ElasticSearch does not support encrypting indices. Has anyone
> 
> ```
> 
> built something on top of Elasticsearch or modified Elasticsearch to  
> achieve encrypted indices? Would like to hear stories of how it went and  
> how the performance is.
> 
> Thanks in advance  
> Parag
> 
> --  
> You received this message because you are subscribed to the Google Groups  
> "elasticsearch" group.  
> To unsubscribe from this group and stop receiving emails from it, send an  
> email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> To view this discussion on the web visit  
> [https://groups.google.com/d/msgid/elasticsearch/7ae652b8-50aa-4e6c-8621-ab0e867068c3%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/7ae652b8-50aa-4e6c-8621-ab0e867068c3%40googlegroups.com)[https://groups.google.com/d/msgid/elasticsearch/7ae652b8-50aa-4e6c-8621-ab0e867068c3%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/7ae652b8-50aa-4e6c-8621-ab0e867068c3%40googlegroups.com?utm_medium=email&utm_source=footer)  
> .  
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
> 
> --  
> You received this message because you are subscribed to the Google Groups  
> "elasticsearch" group.  
> To unsubscribe from this group and stop receiving emails from it, send an  
> email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> To view this discussion on the web visit  
> [https://groups.google.com/d/msgid/elasticsearch/5EE4D14D-38EB-4745-8904-38A65DC819CB%40elasticsearch.com](https://groups.google.com/d/msgid/elasticsearch/5EE4D14D-38EB-4745-8904-38A65DC819CB%40elasticsearch.com)[https://groups.google.com/d/msgid/elasticsearch/5EE4D14D-38EB-4745-8904-38A65DC819CB%40elasticsearch.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/5EE4D14D-38EB-4745-8904-38A65DC819CB%40elasticsearch.com?utm_medium=email&utm_source=footer)  
> .
> 
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQBz\_9%2B5pYjEP1S\_nx8nGgOr\_KTMUMwMjQ5vW4RdEqPaJQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQBz_9%2B5pYjEP1S_nx8nGgOr_KTMUMwMjQ5vW4RdEqPaJQ%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\
**Post date:** [March 13, 2014, 7:09am UTC](https://discuss.elastic.co/t/encrypted-indices/16341/4 "2014-03-13T07:09:30Z")

</div>

Use Linux Disk encryption (LUKS) and trusted computers for encrypting files.

Block device encryption is outside the scope of Lucene.

Jörg

On Thu, Mar 13, 2014 at 6:03 AM, Ivan Brusic [ivan@brusic.com](mailto:ivan@brusic.com) wrote:

> If you stick to non-analyzed term queries, you can always encrypt your  
> data before it is index and then encrypt the query terms that are to be  
> matched. The hashes of the terms will match, but if you use one-way  
> hashing, the original data representation cannot be recovered. Somewhat  
> kludgy and the burden of maintaining the hash key is now simply at another  
> layer.
> 
> --  
> Ivan
> 
> On Wed, Mar 12, 2014 at 7:19 PM, Andrew Selden \<  
> [andrew.selden@elasticsearch.com](mailto:andrew.selden@elasticsearch.com)\> wrote:
> 
> > Hi Parag,
> > 
> > I have seen a few implementations of encrypted Lucene indices, but they  
> > are largely experimental from what I can tell. There are no Elasticsearch  
> > implementations as far as I know.
> > 
> > If you require strong encryption your best bet is to store your  
> > Elasticsearch indices on an encrypted filesystem.
> > 
> > Best,  
> > Andrew
> > 
> > On Mar 12, 2014, at 5:18 PM, Parag Shah [parags@gmail.com](mailto:parags@gmail.com) wrote:
> > 
> > Hi all,
> > 
> > ```
> > I know ElasticSearch does not support encrypting indices. Has anyone
> > 
> > ```
> > 
> > built something on top of Elasticsearch or modified Elasticsearch to  
> > achieve encrypted indices? Would like to hear stories of how it went and  
> > how the performance is.
> > 
> > Thanks in advance  
> > Parag
> > 
> > --  
> > You received this message because you are subscribed to the Google Groups  
> > "elasticsearch" group.  
> > To unsubscribe from this group and stop receiving emails from it, send an  
> > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> > To view this discussion on the web visit  
> > [https://groups.google.com/d/msgid/elasticsearch/7ae652b8-50aa-4e6c-8621-ab0e867068c3%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/7ae652b8-50aa-4e6c-8621-ab0e867068c3%40googlegroups.com)[https://groups.google.com/d/msgid/elasticsearch/7ae652b8-50aa-4e6c-8621-ab0e867068c3%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/7ae652b8-50aa-4e6c-8621-ab0e867068c3%40googlegroups.com?utm_medium=email&utm_source=footer)  
> > .  
> > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
> > 
> > --  
> > You received this message because you are subscribed to the Google Groups  
> > "elasticsearch" group.  
> > To unsubscribe from this group and stop receiving emails from it, send an  
> > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> > To view this discussion on the web visit  
> > [https://groups.google.com/d/msgid/elasticsearch/5EE4D14D-38EB-4745-8904-38A65DC819CB%40elasticsearch.com](https://groups.google.com/d/msgid/elasticsearch/5EE4D14D-38EB-4745-8904-38A65DC819CB%40elasticsearch.com)[https://groups.google.com/d/msgid/elasticsearch/5EE4D14D-38EB-4745-8904-38A65DC819CB%40elasticsearch.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/5EE4D14D-38EB-4745-8904-38A65DC819CB%40elasticsearch.com?utm_medium=email&utm_source=footer)  
> > .
> > 
> > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
> 
> --  
> You received this message because you are subscribed to the Google Groups  
> "elasticsearch" group.  
> To unsubscribe from this group and stop receiving emails from it, send an  
> email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> To view this discussion on the web visit  
> [https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQBz\_9%2B5pYjEP1S\_nx8nGgOr\_KTMUMwMjQ5vW4RdEqPaJQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQBz_9%2B5pYjEP1S_nx8nGgOr_KTMUMwMjQ5vW4RdEqPaJQ%40mail.gmail.com)[https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQBz\_9%2B5pYjEP1S\_nx8nGgOr\_KTMUMwMjQ5vW4RdEqPaJQ%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQBz_9%2B5pYjEP1S_nx8nGgOr_KTMUMwMjQ5vW4RdEqPaJQ%40mail.gmail.com?utm_medium=email&utm_source=footer)  
> .
> 
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAKdsXoHFS2HaOM31%3DO2F6jXFDG%3DjhobzYhFU3LBNRwOox3eGVQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoHFS2HaOM31%3DO2F6jXFDG%3DjhobzYhFU3LBNRwOox3eGVQ%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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:** [July 6, 2017, 1:43am UTC](https://discuss.elastic.co/t/encrypted-indices/16341/5 "2017-07-06T01:43:35Z")

</div>


