# ThreatIntel Module - missing field \[otx.id\] when calculating fingerprint

**URL:** <https://discuss.elastic.co/t/threatintel-module-missing-field-otx-id-when-calculating-fingerprint/330928>\
**Category:** Elastic Security\
**Created:** [April 27, 2023, 9:05am UTC](https://discuss.elastic.co/t/threatintel-module-missing-field-otx-id-when-calculating-fingerprint/330928 "2023-04-27T09:05:10Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![jlopezsec](https://avatars.discourse-cdn.com/v4/letter/j/0ea827/32.png) [@jlopezsec](https://discuss.elastic.co/u/jlopezsec)\
**Post date:** [April 27, 2023, 9:05am UTC](https://discuss.elastic.co/t/threatintel-module-missing-field-otx-id-when-calculating-fingerprint/330928/1 "2023-04-27T09:05:10Z")

</div>

Dear Elastic community,

I am encountering an error in the Threat Intel module of Elastic where I am receiving the following message: "missing field [otx.id] when calculating fingerprint." After researching the error, I believe that this is occurring because the "otx.id" field is not present in the threat events, which is required to calculate the fingerprint.

I have tried to modify the Threat Intel module's configuration by adding the "otx.id" field to the fingerprint fields in the module's configuration file. However, the error persists and I am unable to generate the fingerprints for the threat events.

I am hoping that someone in the Elastic community can provide guidance on how to fix this issue. Are there any additional steps that I need to take in order to include the "otx.id" field in the threat events? Is there a different approach that I should be taking to generate the fingerprints?

Attached Image:

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/f/b/fbca02cdfd2b5c551c120343a5a6b899b4ebab65.png)

Thank you in advance for your help and guidance.

---

<div class="post-metadata">

**Author:** ![wsouza](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wsouza/32/92547_2.png) [@wsouza](https://discuss.elastic.co/u/wsouza)\
**Post date:** [May 10, 2023, 9:20pm UTC](https://discuss.elastic.co/t/threatintel-module-missing-field-otx-id-when-calculating-fingerprint/330928/2 "2023-05-10T21:20:43Z")

</div>

> [@jlopezsec](#):
>
> and guidance.

Are you using the filebeat threat intel module or Elastic Agent integration? Which version of Stack and beat/agent are you using?

---

<div class="post-metadata">

**Author:** ![jlopezsec](https://avatars.discourse-cdn.com/v4/letter/j/0ea827/32.png) [@jlopezsec](https://discuss.elastic.co/u/jlopezsec)\
**Post date:** [May 11, 2023, 4:16pm UTC](https://discuss.elastic.co/t/threatintel-module-missing-field-otx-id-when-calculating-fingerprint/330928/3 "2023-05-11T16:16:18Z")

</div>

8.5.3 both.

---

<div class="post-metadata">

**Author:** ![wsouza](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wsouza/32/92547_2.png) [@wsouza](https://discuss.elastic.co/u/wsouza)\
**Post date:** [May 16, 2023, 6:15pm UTC](https://discuss.elastic.co/t/threatintel-module-missing-field-otx-id-when-calculating-fingerprint/330928/4 "2023-05-16T18:15:37Z")

</div>

Did you try to do an update on agent/beat?

---

<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:** [June 13, 2023, 6:16pm UTC](https://discuss.elastic.co/t/threatintel-module-missing-field-otx-id-when-calculating-fingerprint/330928/5 "2023-06-13T18:16:31Z")

</div>

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