# Obscuring configuration entries **URL:** \ **Category:** Logstash\ **Created:** [September 18, 2015, 12:43pm UTC](https://discuss.elastic.co/t/obscuring-configuration-entries/29572 "2015-09-18T12:43:34Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![kornicameister](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kornicameister/32/4845_2.png) [@kornicameister](https://discuss.elastic.co/u/kornicameister)\ **Post date:** [September 18, 2015, 12:43pm UTC](https://discuss.elastic.co/t/obscuring-configuration-entries/29572/1 "2015-09-18T12:43:34Z")
In Logstash [base plugin](https://github.com/elastic/logstash/blob/9242ae551bacd139ea95ee5e0d036f252134c997/lib/logstash/plugin.rb#L61) there are several places where plugin writes down its current state upon certain events. That's indeed very useful but problematic if such configuration contains vulnerable data. My questions is if that would be possible to obscure certain configuration entries in order for them not to be included in log files ? For now the only reasonable solution would be to override all such methods and use own output message instead of self which evaluates to something similar to object tree. Perhaps there's another approach ? ---
**Author:** ![theuntergeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theuntergeek/32/44961_2.png) [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)\ **Post date:** [September 29, 2015, 9:09am UTC](https://discuss.elastic.co/t/obscuring-configuration-entries/29572/2 "2015-09-29T09:09:46Z")
Please raise an issue for this at [https://github.com/elastic/logstash/issues](https://github.com/elastic/logstash/issues) ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 5:27am UTC](https://discuss.elastic.co/t/obscuring-configuration-entries/29572/3 "2017-07-06T05:27:49Z")