# Reporting Windows Security Events in Kibana

**URL:** <https://discuss.elastic.co/t/reporting-windows-security-events-in-kibana/44748>\
**Category:** Beats\
**Tags:** winlogbeat\
**Created:** [March 17, 2016, 5:55pm UTC](https://discuss.elastic.co/t/reporting-windows-security-events-in-kibana/44748 "2016-03-17T17:55:33Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![andrewkroh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrewkroh/32/3784_2.png) [@andrewkroh](https://discuss.elastic.co/u/andrewkroh)\
**Post date:** [March 17, 2016, 7:30pm UTC](https://discuss.elastic.co/t/reporting-windows-security-events-in-kibana/44748/3 "2016-03-17T19:30:01Z")

</div>

Hi Paul, I have been working on an [enhancement](https://github.com/elastic/beats/pull/1153) to Winlogbeat to make data like "Account Name" available as a field within the JSON event. Also Winlogbeat will report additional data like the "Task" contained in the event. This will make Winlogbeat a much more powerful tool. This is going to be released in [v5](https://www.elastic.co/v5), but a development build is available for testing (see [#1053](https://github.com/elastic/beats/pull/1053)).

Here's a screen shot:

 ![](https://us1.discourse-cdn.com/elastic/original/2X/3/30e3d60203864e454e0aa906d6505ff323736a74.png)

---

_[View the full topic](https://discuss.elastic.co/t/reporting-windows-security-events-in-kibana/44748)._
