# AES Encryption at rest for winlogbeat.yml

**URL:** https://discuss.elastic.co/t/aes-encryption-at-rest-for-winlogbeat-yml/179387
**Category:** Beats
**Tags:** winlogbeat
**Created:** [May 2, 2019, 2:24pm UTC](https://discuss.elastic.co/t/aes-encryption-at-rest-for-winlogbeat-yml/179387 "2019-05-02T14:24:02Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![magneton](https://avatars.discourse-cdn.com/v4/letter/m/9fc348/32.png) [@magneton](https://discuss.elastic.co/u/magneton)
#### Post date: [May 2, 2019, 2:24pm UTC](https://discuss.elastic.co/t/aes-encryption-at-rest-for-winlogbeat-yml/179387/1 "2019-05-02T14:24:02Z")

</div>

Hi All,

Is there a way to encrypt the winlogbeat.yml file for winlogbeat so that if an attacker lands on a windows box they cant just read the logging configuration?

The idea would be to have it encrypted at rest and decrypted when the winlogbeat service starts or restarts.

Cheers

Magneton

---

<div class="post-metadata">

### Author: ![pierhugues](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pierhugues/32/48383_2.png) [@pierhugues](https://discuss.elastic.co/u/pierhugues)
#### Post date: [May 23, 2019, 7:26pm UTC](https://discuss.elastic.co/t/aes-encryption-at-rest-for-winlogbeat-yml/179387/2 "2019-05-23T19:26:51Z")

</div>

Hello,

its not currently possible for Winlogbeat to encrypt his configuration files, we have a [keystore](https://www.elastic.co/guide/en/beats/winlogbeat/current/keystore.html), but's its more like an obfuscation strategy.

---

<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: [June 20, 2019, 7:26pm UTC](https://discuss.elastic.co/t/aes-encryption-at-rest-for-winlogbeat-yml/179387/3 "2019-06-20T19:26:54Z")

</div>

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