# Preventing/Detecting web crawlers with the ELK stack or XPack

**URL:** <https://discuss.elastic.co/t/preventing-detecting-web-crawlers-with-the-elk-stack-or-xpack/126884>\
**Category:** Elasticsearch\
**Created:** [April 5, 2018, 9:09am UTC](https://discuss.elastic.co/t/preventing-detecting-web-crawlers-with-the-elk-stack-or-xpack/126884 "2018-04-05T09:09:26Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ChiuWeng](https://avatars.discourse-cdn.com/v4/letter/c/3bc359/32.png) [@ChiuWeng](https://discuss.elastic.co/u/ChiuWeng)\
**Post date:** [April 5, 2018, 9:09am UTC](https://discuss.elastic.co/t/preventing-detecting-web-crawlers-with-the-elk-stack-or-xpack/126884/1 "2018-04-05T09:09:26Z")

</div>

Hi,

I’m still familiarizing myself with the ELK stack, including the Xpack and Beats. My organization is finding ways in detecting and also preventing web crawling activities by competing organizations.

I went through the ELK stack, Xpack and Beats stack to see if there are any offerings to achieve my task. However, I can’t seem to locate any solution with the ELK, Beats stacks and Xpack to prevent or detect/rectify such issues.

Given that Elasticsearch itself is a crawler, current remedies appear to be implemented outside of the ELK, Beats and Xpack stacks like the ones described here:  
[https://blog.hartleybrody.com/prevent-scrapers/](https://blog.hartleybrody.com/prevent-scrapers/)

Can anyone share their thoughts about this subject?

---

<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 3, 2018, 9:09am UTC](https://discuss.elastic.co/t/preventing-detecting-web-crawlers-with-the-elk-stack-or-xpack/126884/2 "2018-05-03T09:09:49Z")

</div>

Closed on May 3, 2018, 9:09am UTC

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