# MetricBeat Binary Signed

**URL:** <https://discuss.elastic.co/t/metricbeat-binary-signed/246349>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [August 25, 2020, 7:08pm UTC](https://discuss.elastic.co/t/metricbeat-binary-signed/246349 "2020-08-25T19:08:40Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Questions](https://avatars.discourse-cdn.com/v4/letter/q/dec6dc/32.png) [@Questions](https://discuss.elastic.co/u/Questions)\
**Post date:** [August 25, 2020, 7:08pm UTC](https://discuss.elastic.co/t/metricbeat-binary-signed/246349/1 "2020-08-25T19:08:40Z")

</div>

On investigating the MetricBeat client binary, I noticed that it was not properly signed with the Elastic publisher certificate (the Endgame sensor binary is signed). Am I missing something or is there a reason why MetricBeat is not signed?

This is a requirement for a federal client.

---

<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:** [September 22, 2020, 9:08pm UTC](https://discuss.elastic.co/t/metricbeat-binary-signed/246349/2 "2020-09-22T21:08:42Z")

</div>

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