# Secure access to logstash

**URL:** <https://discuss.elastic.co/t/secure-access-to-logstash/229585>\
**Category:** Beats\
**Created:** [April 24, 2020, 7:01am UTC](https://discuss.elastic.co/t/secure-access-to-logstash/229585 "2020-04-24T07:01:32Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![probson](https://avatars.discourse-cdn.com/v4/letter/p/e47c2d/32.png) [@probson](https://discuss.elastic.co/u/probson)\
**Post date:** [April 24, 2020, 7:01am UTC](https://discuss.elastic.co/t/secure-access-to-logstash/229585/1 "2020-04-24T07:01:33Z")

</div>

Hi,

We currently use winlogbeats on a WEF server, logstash behind a firewall with allow rules for the source of the WEF server, using SSL on top of that.

We need to plan for a more mobile workforce without vpn back to the WEF server.

Exposing logstash to the outside isn't something I feel great about, certificate authentication seems as though it will be a headache to manage with expiry etc.

I add a field using the processor with an ID so I could drop all events without an ID which would help with rogue data coming in.

It looks as though kafka could accept a username and password which may tick the box to better secure winlogbeats to logstash.

Reaching out for any recommendations/suggestions.

Thanks  
Phil

---

<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:** [May 22, 2020, 9:01am UTC](https://discuss.elastic.co/t/secure-access-to-logstash/229585/2 "2020-05-22T09:01:34Z")

</div>

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