# Kibana credential exposure (ESA-2018-17) fix clarification **URL:** \ **Category:** Kibana\ **Created:** [June 4, 2019, 9:12am UTC](https://discuss.elastic.co/t/kibana-credential-exposure-esa-2018-17-fix-clarification/184130 "2019-06-04T09:12:11Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Mohanraj](https://avatars.discourse-cdn.com/v4/letter/m/bbe5ce/32.png) [@Mohanraj](https://discuss.elastic.co/u/Mohanraj)\ **Post date:** [June 4, 2019, 9:12am UTC](https://discuss.elastic.co/t/kibana-credential-exposure-esa-2018-17-fix-clarification/184130/1 "2019-06-04T09:12:11Z")
Hi, do we need to stop the kibana service before updating the kibana.yml file ? we have 3 node cluster ? how can plan for the update ? update all 3 nodes and then restart the kibana service ? ---
**Author:** ![jen-huang](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jen-huang/32/74327_2.png) [@jen-huang](https://discuss.elastic.co/u/jen-huang)\ **Post date:** [June 4, 2019, 6:10pm UTC](https://discuss.elastic.co/t/kibana-credential-exposure-esa-2018-17-fix-clarification/184130/2 "2019-06-04T18:10:04Z")
If you are unable to upgrade, yes stop Kibana service, apply `xpack.reporting.enabled: false` to kibana.yml, and restart Kibana. You can reference our [Upgrade documentation](https://www.elastic.co/guide/en/elastic-stack/7.1/upgrading-elastic-stack.html) when you're ready to upgrade your stack. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 2, 2019, 6:10pm UTC](https://discuss.elastic.co/t/kibana-credential-exposure-esa-2018-17-fix-clarification/184130/3 "2019-07-02T18:10:20Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.