# Loose cluster security config

**URL:** <https://discuss.elastic.co/t/loose-cluster-security-config/51153>\
**Category:** Elasticsearch\
**Created:** [May 27, 2016, 11:29am UTC](https://discuss.elastic.co/t/loose-cluster-security-config/51153 "2016-05-27T11:29:22Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Andreea\_Hazi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andreea_hazi/32/9994_2.png) [@Andreea\_Hazi](https://discuss.elastic.co/u/Andreea_Hazi)\
**Post date:** [May 27, 2016, 11:29am UTC](https://discuss.elastic.co/t/loose-cluster-security-config/51153/1 "2016-05-27T11:29:22Z")

</div>

I use elasticsearch 1.4 for 3 node cluster, and I have a basic cluster configuration:

discovery.zen.ping.multicast.enabled: false  
discovery.zen.ping.unicast.hosts: ['node1', 'node2', 'node3']  
http.cors.enabled: true  
http.cors.allow-origin: '/.\*/'

Is there a way to configure our cluster to be able to prohibit other applications from discovering our cluster, and create indices in our cluster. Maybe prohibit a specific index name like 'system\_logs' to be created.

Thank you

---

<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:** [May 29, 2016, 1:09am UTC](https://discuss.elastic.co/t/loose-cluster-security-config/51153/2 "2016-05-29T01:09:46Z")

</div>

A firewall or something like the Shield plugin would work.

---

<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 5, 2017, 10:48pm UTC](https://discuss.elastic.co/t/loose-cluster-security-config/51153/3 "2017-07-05T22:48:19Z")

</div>