# Is there any way of restricting access to Kibana based on IP address/subnets?

**URL:** <https://discuss.elastic.co/t/is-there-any-way-of-restricting-access-to-kibana-based-on-ip-address-subnets/279810>\
**Category:** Kibana\
**Tags:** elastic-stack-security\
**Created:** [July 28, 2021, 7:07am UTC](https://discuss.elastic.co/t/is-there-any-way-of-restricting-access-to-kibana-based-on-ip-address-subnets/279810 "2021-07-28T07:07:04Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![neil6323](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/neil6323/32/92234_2.png) [@neil6323](https://discuss.elastic.co/u/neil6323)\
**Post date:** [July 28, 2021, 7:07am UTC](https://discuss.elastic.co/t/is-there-any-way-of-restricting-access-to-kibana-based-on-ip-address-subnets/279810/1 "2021-07-28T07:07:04Z")

</div>

Hi all,  
I know you can restrict access to Elasticsearch nodes using IP filtering. But I believe this does not restrict access to Kibana. Is there a similar mechanism to IP filters for Kibana?

The end result we are looking for is to allow access on port 5601 to hosts located on certain subnets and deny all other connectivity as a layer of security (and then apply other security measures).

Thanks  
Neil

---

<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:** [July 28, 2021, 11:47pm UTC](https://discuss.elastic.co/t/is-there-any-way-of-restricting-access-to-kibana-based-on-ip-address-subnets/279810/2 "2021-07-28T23:47:25Z")

</div>

Welcome to our community! 😃

There's not for Kibana no. I would encourage you to create a Feature Request for this in GitHub though!

---

<div class="post-metadata">

**Author:** ![legoguy1000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/legoguy1000/32/54301_2.png) [@legoguy1000](https://discuss.elastic.co/u/legoguy1000)\
**Post date:** [July 28, 2021, 11:59pm UTC](https://discuss.elastic.co/t/is-there-any-way-of-restricting-access-to-kibana-based-on-ip-address-subnets/279810/3 "2021-07-28T23:59:48Z")

</div>

You could put kibana behind a reverse proxy like Nginx where u can do filtering.

---

<div class="post-metadata">

**Author:** ![neil6323](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/neil6323/32/92234_2.png) [@neil6323](https://discuss.elastic.co/u/neil6323)\
**Post date:** [July 29, 2021, 4:44am UTC](https://discuss.elastic.co/t/is-there-any-way-of-restricting-access-to-kibana-based-on-ip-address-subnets/279810/4 "2021-07-29T04:44:54Z")

</div>

Thanks Mark, both for the welcome and the comments. Much appreciated.

---

<div class="post-metadata">

**Author:** ![neil6323](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/neil6323/32/92234_2.png) [@neil6323](https://discuss.elastic.co/u/neil6323)\
**Post date:** [July 29, 2021, 4:45am UTC](https://discuss.elastic.co/t/is-there-any-way-of-restricting-access-to-kibana-based-on-ip-address-subnets/279810/5 "2021-07-29T04:45:34Z")

</div>

Thanks Alex. Appreciate the suggestion

---

<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:** [August 26, 2021, 4:46am UTC](https://discuss.elastic.co/t/is-there-any-way-of-restricting-access-to-kibana-based-on-ip-address-subnets/279810/6 "2021-08-26T04:46:29Z")

</div>

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