# Network Beaconing Identification Integration

**URL:** <https://discuss.elastic.co/t/network-beaconing-identification-integration/376031>\
**Category:** Elastic Security\
**Created:** [March 17, 2025, 8:01pm UTC](https://discuss.elastic.co/t/network-beaconing-identification-integration/376031 "2025-03-17T20:01:15Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Akodo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/akodo/32/141073_2.png) [@Akodo](https://discuss.elastic.co/u/Akodo)\
**Post date:** [March 17, 2025, 8:01pm UTC](https://discuss.elastic.co/t/network-beaconing-identification-integration/376031/1 "2025-03-17T20:01:16Z")

</div>

I'm currently setting up Network Beaconing Identification, and I'm fairly new to how Elastic has Agent Policies and where would one need to install an integration to correlate said logs. My thinking is, I should install Network Beaconing Identification on an AD or some server that has ample communications? Or is it better to spread this integration throughout the infrastructure to gather the information that I would need for tracking beacons? Any help would be appreciated!

---

<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:** [April 14, 2025, 8:01pm UTC](https://discuss.elastic.co/t/network-beaconing-identification-integration/376031/2 "2025-04-14T20:01:20Z")

</div>

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