# Security Hardening Parameters for Elastic stack

**URL:** <https://discuss.elastic.co/t/security-hardening-parameters-for-elastic-stack/161189>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-security\
**Created:** [December 17, 2018, 4:21pm UTC](https://discuss.elastic.co/t/security-hardening-parameters-for-elastic-stack/161189 "2018-12-17T16:21:13Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![DineshTripathi](https://avatars.discourse-cdn.com/v4/letter/d/ce7236/32.png) [@DineshTripathi](https://discuss.elastic.co/u/DineshTripathi)\
**Post date:** [December 17, 2018, 4:21pm UTC](https://discuss.elastic.co/t/security-hardening-parameters-for-elastic-stack/161189/1 "2018-12-17T16:21:13Z")

</div>

I am working on operational readiness of Elastic stack and one of the key requirement is to ensure Elastic stack is hardened.  
Did anyone already have the recommended security parameters? Please help me with that.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [December 17, 2018, 9:42pm UTC](https://discuss.elastic.co/t/security-hardening-parameters-for-elastic-stack/161189/2 "2018-12-17T21:42:41Z")

</div>

You should definitely be using [https://www.elastic.co/products/stack/security](https://www.elastic.co/products/stack/security) then.

---

<div class="post-metadata">

**Author:** ![DineshTripathi](https://avatars.discourse-cdn.com/v4/letter/d/ce7236/32.png) [@DineshTripathi](https://discuss.elastic.co/u/DineshTripathi)\
**Post date:** [December 25, 2018, 1:54am UTC](https://discuss.elastic.co/t/security-hardening-parameters-for-elastic-stack/161189/3 "2018-12-25T01:54:19Z")

</div>

Thank you. I will review this

---

<div class="post-metadata">

**Author:** ![DineshTripathi](https://avatars.discourse-cdn.com/v4/letter/d/ce7236/32.png) [@DineshTripathi](https://discuss.elastic.co/u/DineshTripathi)\
**Post date:** [January 3, 2019, 12:02pm UTC](https://discuss.elastic.co/t/security-hardening-parameters-for-elastic-stack/161189/4 "2019-01-03T12:02:45Z")

</div>

I have reviewed all of this but I feel there are few more point which needs to be covered.  
Let say I am deploying Elastic stack on RHEL, and config files, execuatables etc are stored on some directories like /etc/elasticsearch etc.

Now, what are the recommended permissions to protect those directories and it should also not break elastic components?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [January 3, 2019, 7:42pm UTC](https://discuss.elastic.co/t/security-hardening-parameters-for-elastic-stack/161189/5 "2019-01-03T19:42:57Z")

</div>

The recommended permissions are the ones we ship with. Changing them will not be supported.

---

<div class="post-metadata">

**Author:** ![DineshTripathi](https://avatars.discourse-cdn.com/v4/letter/d/ce7236/32.png) [@DineshTripathi](https://discuss.elastic.co/u/DineshTripathi)\
**Post date:** [January 4, 2019, 3:02am UTC](https://discuss.elastic.co/t/security-hardening-parameters-for-elastic-stack/161189/6 "2019-01-04T03:02:17Z")

</div>

@warkolm do you mean when we install Elastic stack on a VM, it will create required files and folders, also there will be ownership and permission associated with them. Just e.g. /etc/elasticsearch will be owned by elasticsearch and chmod is 644 .

So we should not make any change with that. Is that you are saying?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [January 4, 2019, 5:24am UTC](https://discuss.elastic.co/t/security-hardening-parameters-for-elastic-stack/161189/7 "2019-01-04T05:24:50Z")

</div>

> [@DineshTripathi](#):
>
> So we should not make any change with that. Is that you are saying?

That is right. If you do, then you are on your own with any problems.

---

<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:** [February 1, 2019, 5:24am UTC](https://discuss.elastic.co/t/security-hardening-parameters-for-elastic-stack/161189/8 "2019-02-01T05:24:50Z")

</div>

Closed on February 1, 2019, 5:24am UTC

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