# Warning: 299 Elasticsearch-7.15.1 .... setup minimal security

**URL:** <https://discuss.elastic.co/t/warning-299-elasticsearch-7-15-1-setup-minimal-security/287179>\
**Category:** Kibana\
**Tags:** elastic-stack-security\
**Created:** [October 20, 2021, 9:53am UTC](https://discuss.elastic.co/t/warning-299-elasticsearch-7-15-1-setup-minimal-security/287179 "2021-10-20T09:53:34Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![6NMgfDwZ3](https://avatars.discourse-cdn.com/v4/letter/6/ac91a4/32.png) [@6NMgfDwZ3](https://discuss.elastic.co/u/6NMgfDwZ3)\
**Post date:** [October 20, 2021, 9:53am UTC](https://discuss.elastic.co/t/warning-299-elasticsearch-7-15-1-setup-minimal-security/287179/1 "2021-10-20T09:53:34Z")

</div>

Hi all,

I'm using Elasticsearch-Kibana-Filebeat (all v7.15.1) (Ubuntu 21.04) and I get this message at every Discover refreshing, or query

`Warning: 299 Elasticsearch-7.15.1-83c34f456ae29d60e94d886e455e6a3409bba9ed "Elasticsearch built-in security features are not enabled. Without authentication, your cluster could be accessible to anyone. See https://www.elastic.co/guide/en/elasticsearch/reference/7.15/security-minimal-setup.html to enable security."`

I understand that most of the users or in the most of cases it is common sense to set up a minimal security with user/password ... at least with "admin"/"admin" 🙂

but our case is special one so set up minimal security is pointless and it would _absolute_ "pain in ...."

My question is how can I terminally mute this warning?

Thanks!

---

<div class="post-metadata">

**Author:** ![Yang\_Wang](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yang_wang/32/48857_2.png) [@Yang\_Wang](https://discuss.elastic.co/u/Yang_Wang)\
**Post date:** [October 20, 2021, 10:33am UTC](https://discuss.elastic.co/t/warning-299-elasticsearch-7-15-1-setup-minimal-security/287179/2 "2021-10-20T10:33:28Z")

</div>

We have a public issue for it [Spectacularly Annoying: Warning: 299 Elasticsearch-7.15.0-79d65f6e357953a5b3cbcc5e2c7c21073d89aa29 · Issue #78500 · elastic/elasticsearch · GitHub](https://github.com/elastic/elasticsearch/issues/78500)

The current solution is to explicitly disable security (though our normal recommendation is to enable it) with `xpack.security.enabled: false`. Again, please use this as a last resort because your cluster might benefit from having security enabled without you knowing it in advance.

---

<div class="post-metadata">

**Author:** ![6NMgfDwZ3](https://avatars.discourse-cdn.com/v4/letter/6/ac91a4/32.png) [@6NMgfDwZ3](https://discuss.elastic.co/u/6NMgfDwZ3)\
**Post date:** [October 20, 2021, 11:16am UTC](https://discuss.elastic.co/t/warning-299-elasticsearch-7-15-1-setup-minimal-security/287179/3 "2021-10-20T11:16:34Z")

</div>

Thank you very much!

I definitely have to improve my googling skills. 🙂

---

<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:** [November 17, 2021, 11:17am UTC](https://discuss.elastic.co/t/warning-299-elasticsearch-7-15-1-setup-minimal-security/287179/4 "2021-11-17T11:17:08Z")

</div>

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