# Bulk Indexing of signals failed: object mapping for \[host\] tried to parse field \[host\] as object, but found a concrete value name

**URL:** <https://discuss.elastic.co/t/bulk-indexing-of-signals-failed-object-mapping-for-host-tried-to-parse-field-host-as-object-but-found-a-concrete-value-name/334705>\
**Category:** SIEM\
**Created:** [May 30, 2023, 4:59pm UTC](https://discuss.elastic.co/t/bulk-indexing-of-signals-failed-object-mapping-for-host-tried-to-parse-field-host-as-object-but-found-a-concrete-value-name/334705 "2023-05-30T16:59:18Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![UP\_NEWS](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/up_news/32/121369_2.png) [@UP\_NEWS](https://discuss.elastic.co/u/UP_NEWS)\
**Post date:** [May 30, 2023, 4:59pm UTC](https://discuss.elastic.co/t/bulk-indexing-of-signals-failed-object-mapping-for-host-tried-to-parse-field-host-as-object-but-found-a-concrete-value-name/334705/1 "2023-05-30T16:59:18Z")

</div>

Hi team,

the parser used for Kaspersky, more precisely in the host field, does not allow the triggering of the rule relating to the detection of malicious files once the conditions are met.

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/c/6/c6077f043aff83fdd5077fe51ee1d35a13e11c2d.png)

---

<div class="post-metadata">

**Author:** ![vitaliidm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vitaliidm/32/101610_2.png) [@vitaliidm](https://discuss.elastic.co/u/vitaliidm)\
**Post date:** [June 2, 2023, 3:53pm UTC](https://discuss.elastic.co/t/bulk-indexing-of-signals-failed-object-mapping-for-host-tried-to-parse-field-host-as-object-but-found-a-concrete-value-name/334705/2 "2023-06-02T15:53:18Z")

</div>

Hi @UP_NEWS

Can you please tell which version of ES/Kibana are you using?  
Looking at error, it seems like host property is not ECS compliant.  
It should be object: [Host Fields | Elastic Common Schema (ECS) Reference [8.8] | Elastic](https://www.elastic.co/guide/en/ecs/current/ecs-host.html), not a string.

There are 2 ways to proceed:

1. In 8.7, we implemented removing from alert source document ECS non compliant data: [[Security Solution][Alerts] Strip ECS-incompatible fields before writing alerts · Issue #146848 · elastic/kibana · GitHub](https://github.com/elastic/kibana/issues/146848). It will allow to trigger alert, but string type host, will be removed from alert. It will be logged though
2. Reindex data, so it will be compliant. I.e. host can become compliant "host.name" [Host Fields | Elastic Common Schema (ECS) Reference [8.8] | Elastic](https://www.elastic.co/guide/en/ecs/current/ecs-host.html#field-host-name)

Thanks, Vitalii

---

<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 30, 2023, 3:54pm UTC](https://discuss.elastic.co/t/bulk-indexing-of-signals-failed-object-mapping-for-host-tried-to-parse-field-host-as-object-but-found-a-concrete-value-name/334705/3 "2023-06-30T15:54:00Z")

</div>

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