# Open source parsers

**URL:** <https://discuss.elastic.co/t/open-source-parsers/214914>\
**Category:** Logstash\
**Tags:** ecs-elastic-common-schema\
**Created:** [January 13, 2020, 11:02pm UTC](https://discuss.elastic.co/t/open-source-parsers/214914 "2020-01-13T23:02:24Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ramicoh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ramicoh/32/61017_2.png) [@Ramicoh](https://discuss.elastic.co/u/Ramicoh)\
**Post date:** [January 13, 2020, 11:02pm UTC](https://discuss.elastic.co/t/open-source-parsers/214914/1 "2020-01-13T23:02:25Z")

</div>

Hey,

We created some open source parsers for Logstash, customized for some common software products (Symantec, CarbonBlack etc.): [https://github.com/empow/logstash-parsers/](https://github.com/empow/logstash-parsers/)

**I would love to hear your opinions** - how useful could these be for security analysts?

The intent here is to save time-consuming and tricky work of "deciphering" the data in log chunks. The logic uses Grok, MITRE and maps to ECS.

Thanks 🙂

---

<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:** [February 10, 2020, 11:02pm UTC](https://discuss.elastic.co/t/open-source-parsers/214914/2 "2020-02-10T23:02:26Z")

</div>

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