# Creating an indicator match Watcher Alert

**URL:** <https://discuss.elastic.co/t/creating-an-indicator-match-watcher-alert/329590>\
**Category:** Elasticsearch\
**Created:** [April 7, 2023, 5:26pm UTC](https://discuss.elastic.co/t/creating-an-indicator-match-watcher-alert/329590 "2023-04-07T17:26:25Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Banderson02](https://avatars.discourse-cdn.com/v4/letter/b/b2d939/32.png) [@Banderson02](https://discuss.elastic.co/u/Banderson02)\
**Post date:** [April 7, 2023, 5:26pm UTC](https://discuss.elastic.co/t/creating-an-indicator-match-watcher-alert/329590/1 "2023-04-07T17:26:25Z")

</div>

Hello,  
Has anyone been able to replicate an indicator match alert like what is provided in Kibana security as an Elasticsearch Watcher alert?

I have a deployment where we do not have access to Kibana Security, so I need to create an indicator match alert using Watcher instead. I found resources saying I should look into chain input, but there aren't a whole lot of examples available to go off of and learn syntax.

Rough logic is:

If source.ip in "Checkpoint.index" matches malicious.ip in "Malicious.ips.index", alert.

---

<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:** [May 5, 2023, 5:26pm UTC](https://discuss.elastic.co/t/creating-an-indicator-match-watcher-alert/329590/2 "2023-05-05T17:26:51Z")

</div>

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