# SIEM Parsing

**URL:** <https://discuss.elastic.co/t/siem-parsing/188291>\
**Category:** SIEM\
**Created:** [July 1, 2019, 10:49am UTC](https://discuss.elastic.co/t/siem-parsing/188291 "2019-07-01T10:49:34Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![pinguin](https://avatars.discourse-cdn.com/v4/letter/p/ac8455/32.png) [@pinguin](https://discuss.elastic.co/u/pinguin)\
**Post date:** [July 1, 2019, 10:49am UTC](https://discuss.elastic.co/t/siem-parsing/188291/1 "2019-07-01T10:49:35Z")

</div>

we are trying to send windows event logs using winlogbeat 7.XX version , we are creating severals of dashboards based on the correlation rules of event built on top of event ,sysmon and security logs ex : event.id =1 AND winlog.event\_data.Commandline=ipconfig.exe (this is a visualization).

we observered that events fields are changing across different winlogbetas version , this is impacting our dashboard ( ex 6.71 to 7.1) . This affect all our correlation rules and dashboards.  
(Event\_id ---\> Event.code / Winlog.event\_id is being append to mostly all fields)

We observed that in 7.XX we have ECS format that is being used or supported ,

Since we have many event\_id being received from windows event viewer .

What is the recommended solution in such situation where we have many event\_id being received from windows event viewer?

Should send the winlogbeat to Logstash to parse it based on event\_id , in a continuous development upon any winlogbeat change , in a way the fields on kibana are intact ?

OR we should send automatically to Elastic and relay on Winlogbeat ECS format which might be a standard?

---

<div class="post-metadata">

**Author:** ![cwurm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cwurm/32/34882_2.png) [@cwurm](https://discuss.elastic.co/u/cwurm)\
**Post date:** [July 1, 2019, 9:34pm UTC](https://discuss.elastic.co/t/siem-parsing/188291/2 "2019-07-01T21:34:28Z")

</div>

Hi @pinguin,

For migration from 6.7 to 7.x you can set `migration.6_to_7.enabled: true` before upgrading to 7. This _should_ help with your dashboards, I'm not sure about your correlation rules (the field aliases the setting creates work for queries, but not for the actual document contents in `_source`). See also the [documentation](https://www.elastic.co/guide/en/beats/libbeat/current/upgrading-6-to-7.html#enable-ecs-compatibility).

> [@pinguin](#):
>
> OR we should send automatically to Elastic and relay on Winlogbeat ECS format which might be a standard?

I would recommend keeping the events in ECS. There might be some inconsistency between 6.x and 7.x events (7.0 is the first release that had ECS) - but going forward we will keep ECS in place across data sources.

---

<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:** [July 29, 2019, 9:34pm UTC](https://discuss.elastic.co/t/siem-parsing/188291/3 "2019-07-29T21:34:33Z")

</div>

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