# Kibana down during Nessus scanning **URL:** \ **Category:** Kibana\ **Created:** [April 8, 2019, 11:26am UTC](https://discuss.elastic.co/t/kibana-down-during-nessus-scanning/175823 "2019-04-08T11:26:00Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![sstest](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sstest/32/43659_2.png) [@sstest](https://discuss.elastic.co/u/sstest)\ **Post date:** [April 8, 2019, 11:26am UTC](https://discuss.elastic.co/t/kibana-down-during-nessus-scanning/175823/1 "2019-04-08T11:26:00Z")
We recently implemented Nessus vulnerability scanning on top of Kibana ports [80, 8080] and found Kibana going down during scanning automatically. Looks like Nessus performing Soap API checks on 8080 port and if Kibana runs with Soap API then there might be a chance that Kibana can go down. My question is whether kibana uses soap APIs in-built? If so, any recommendations to tackle this. I am using Kibana3. ---
**Author:** ![tsullivan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tsullivan/32/31077_2.png) [@tsullivan](https://discuss.elastic.co/u/tsullivan)\ **Post date:** [April 8, 2019, 8:27pm UTC](https://discuss.elastic.co/t/kibana-down-during-nessus-scanning/175823/2 "2019-04-08T20:27:50Z")
Hi, Kibana doesn't use SOAP or XML transmission of data at all. Kibana server is NodeJS and speaks JSON. My suggestion would be to make sure the scanner is making direct TCP connections to Kibana, rather than a load balancer or proxy. ---
**Author:** ![tsullivan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tsullivan/32/31077_2.png) [@tsullivan](https://discuss.elastic.co/u/tsullivan)\ **Post date:** [April 8, 2019, 8:29pm UTC](https://discuss.elastic.co/t/kibana-down-during-nessus-scanning/175823/3 "2019-04-08T20:29:22Z")
> [@sstest](#): > > Kibana ports [80, 8080] Sorry, just another note. By default, Kibana listens on port 5601 on the localhost interface. Unless server settings were changed in Kibana, there will be no regard to port 80 or 8080. That looks to me more like what a reverse proxy listens on. ---
**Author:** ![sstest](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sstest/32/43659_2.png) [@sstest](https://discuss.elastic.co/u/sstest)\ **Post date:** [April 11, 2019, 9:57am UTC](https://discuss.elastic.co/t/kibana-down-during-nessus-scanning/175823/4 "2019-04-11T09:57:27Z")
Yes, we set it explicitly to 8080. ---
**Author:** ![sstest](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sstest/32/43659_2.png) [@sstest](https://discuss.elastic.co/u/sstest)\ **Post date:** [April 11, 2019, 9:57am UTC](https://discuss.elastic.co/t/kibana-down-during-nessus-scanning/175823/5 "2019-04-11T09:57:48Z")
Thanks @tsullivan. ---
**Author:** ![waidesteve](https://avatars.discourse-cdn.com/v4/letter/w/779978/32.png) [@waidesteve](https://discuss.elastic.co/u/waidesteve)\ **Post date:** [April 11, 2019, 10:38am UTC](https://discuss.elastic.co/t/kibana-down-during-nessus-scanning/175823/6 "2019-04-11T10:38:33Z")
The following part where the user will need the overall information which will be going to find the better work for it so [logitech h111 mic not working](https://uaetechnician.ae/logitech-h111-mic-not-working-resolve-this-problem-quickly-just-in-few-easy-steps) will provide the better way. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [May 9, 2019, 10:38am UTC](https://discuss.elastic.co/t/kibana-down-during-nessus-scanning/175823/7 "2019-05-09T10:38:33Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.