# About this guide and project
================================

This guide was authored and is maintained by:

**Mika Ayenson** <a href="https://twitter.com/@stryker0x"><img src="_static/x_logo.png" width="20" height="20" style="vertical-align:middle"></a> <a href="https://github.com/Mikaayenson"><img src="_static/github_logo.png" width="20" height="20" style="vertical-align:middle"></a> <a href="https://linkedin.com/in/mika-ayenson"><img src="_static/linkedin_logo.png" width="20" height="20" style="vertical-align:middle"></a> - Threat Research and Detection Engineering (TRADE) lead at Elastic

**Eric Forte** <a href="https://twitter.com/EricF0r73"><img src="_static/x_logo.png" width="20" height="20" style="vertical-align:middle"></a> <a href="https://github.com/eric-forte-elastic"><img src="_static/github_logo.png" width="20" height="20" style="vertical-align:middle"></a> - Security Research Engineer at Elastic

**Kseniia Ignatovych** <a href="https://github.com/approksiu"><img src="_static/github_logo.png" width="20" height="20" style="vertical-align:middle"></a> <a href="https://www.linkedin.com/in/kseniiaignatovych"><img src="_static/linkedin_logo.png" width="20" height="20" style="vertical-align:middle"></a> - Security Product Manager at Elastic

This guide is meant to enable the implementation of detections as code in a generic manner, through the application of its use on Elastic detection rules (SIEM). We will continue to maintain and improve this guide, especially in the early stages of the new code and adoption, with the intent that this eventually stabilizes.

If you have any feedback or questions along the way, the best place to reach us is in the public slack channel for [security-rules-dac](https://elasticstack.slack.com/archives/C06TE19EP09).

## Licensing and Use

See the LICENSE file for licensing information. This guide is provided as-is and is not officially supported by Elastic. It is intended to be a community-driven project, and we welcome contributions and feedback.