# Aggregation support in SIEM

**URL:** <https://discuss.elastic.co/t/aggregation-support-in-siem/237974>\
**Category:** SIEM\
**Created:** [June 21, 2020, 6:16pm UTC](https://discuss.elastic.co/t/aggregation-support-in-siem/237974 "2020-06-21T18:16:12Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![NerdSec](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nerdsec/32/22056_2.png) [@NerdSec](https://discuss.elastic.co/u/NerdSec)\
**Post date:** [June 21, 2020, 6:16pm UTC](https://discuss.elastic.co/t/aggregation-support-in-siem/237974/1 "2020-06-21T18:16:12Z")

</div>

Hi Team,

Are there any plans to add an aggregations support in the SIEM app? Maybe the ability to create a correlation rule by leveraging the Elasticsearch aggregations?

For example, a very simple use case, where you wish to identify more than 10 login failures for a single user in a short amount of time. Something that you would expect from a traditional SIEM?

---

<div class="post-metadata">

**Author:** ![Mike\_Paquette](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mike_paquette/32/119011_2.png) [@Mike\_Paquette](https://discuss.elastic.co/u/Mike_Paquette)\
**Post date:** [June 23, 2020, 12:24pm UTC](https://discuss.elastic.co/t/aggregation-support-in-siem/237974/2 "2020-06-23T12:24:57Z")

</div>

Hi @NerdSec, thanks for the post. The answer is Yes, we do plan to support detection rules that can use Elasticsearch aggregations. We'll likely start with just some simple threshold-based capability, as future rule types will provide more advanced correlation capabilities.

There is a GitHub issue that covers the general idea here: [https://github.com/elastic/kibana/issues/68409](https://github.com/elastic/kibana/issues/68409)

Your example is a good one to help us make sure that the new rule capability meets the needs of SIEM users.

Question please: If you had this capability in the Elastic SIEM app, what are a few more simple rules that you think users might want to create?

Thanks again!

---

<div class="post-metadata">

**Author:** ![NerdSec](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nerdsec/32/22056_2.png) [@NerdSec](https://discuss.elastic.co/u/NerdSec)\
**Post date:** [June 23, 2020, 12:59pm UTC](https://discuss.elastic.co/t/aggregation-support-in-siem/237974/3 "2020-06-23T12:59:40Z")

</div>

Hi Mike,

Thank you for the response! I just commented on the mentioned issue. I think it's a great implementation to leverage the Elastic SQL to enable the user to make these agg calls.

We ended up implementing a interpretation layer, that converts the users request into a `elasticsearch_py_dsl` query. In most of our cases, we never required anything other than terms, date\_histogram, cardinality, and bucket\_selector aggregations. I am actually documenting this in a blog (including some use-cases), that I hope to publish soon. Will post the link here once done! 🙂

---

<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 21, 2020, 12:59pm UTC](https://discuss.elastic.co/t/aggregation-support-in-siem/237974/4 "2020-07-21T12:59:44Z")

</div>

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