# Recorded Future v1.0.1 Not Populating Intel Properly

**URL:** https://discuss.elastic.co/t/recorded-future-v1-0-1-not-populating-intel-properly/309231
**Category:** Kibana
**Tags:** integrations
**Created:** [July 8, 2022, 10:21pm UTC](https://discuss.elastic.co/t/recorded-future-v1-0-1-not-populating-intel-properly/309231 "2022-07-08T22:21:34Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![codewriterguy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/codewriterguy/32/113440_2.png) [@codewriterguy](https://discuss.elastic.co/u/codewriterguy)
#### Post date: [July 8, 2022, 10:21pm UTC](https://discuss.elastic.co/t/recorded-future-v1-0-1-not-populating-intel-properly/309231/1 "2022-07-08T22:21:34Z")

</div>

Hi,

The Recorded Future integration package v1.0.1 appears not to be properly pulling risklists from Recorded Future.

Intel is streaming into the instance (screenshot at 22:15UTC):

 ![Screen Shot 2022-07-08 at 4.16.05 PM](https://us1.discourse-cdn.com/elastic/original/3X/4/b/4b86638a4efb150ba0a81945957bd56127da3c3d.png)

Elastic agent is healthy:

 ![Screen Shot 2022-07-08 at 4.10.21 PM](https://us1.discourse-cdn.com/elastic/original/3X/3/b/3b06b7b68dcb21296a0846f0b60c372d9da70378.png)

I've tagged each entity type to make queries for entity types in `logs-ti_*` easier:  
 ![Screen Shot 2022-07-08 at 4.16.41 PM](https://us1.discourse-cdn.com/elastic/original/3X/3/7/37d8ce57d5fe5044ef0ef2472b29ac5d9d27a670.png)

Seeing incorrect quantities coming in. No hashes, only 1895 IP events, 4385 domain events, and \> 250,000 URL events. Last screenshot is from the \_count endpoint for the data stream.

 ![Screen Shot 2022-07-08 at 4.20.55 PM](https://us1.discourse-cdn.com/elastic/original/3X/b/f/bf2cf8f503b8c30b875ca98efac455540b8834b0.png)  
 ![Screen Shot 2022-07-08 at 4.21.18 PM](https://us1.discourse-cdn.com/elastic/original/3X/9/5/9561db8cd92f4850fd859c4fd1ff91ee16b45e09.png)  
 ![Screen Shot 2022-07-08 at 4.19.23 PM](https://us1.discourse-cdn.com/elastic/original/3X/b/6/b67898a005408580fd26718ae34faaf0694e0ebc.png)  
 ![Screen Shot 2022-07-08 at 4.19.54 PM](https://us1.discourse-cdn.com/elastic/original/3X/e/b/ebb2da8ef033f1bfc213ca36058f7351b1501b4f.png)

---

<div class="post-metadata">

### Author: ![codewriterguy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/codewriterguy/32/113440_2.png) [@codewriterguy](https://discuss.elastic.co/u/codewriterguy)
#### Post date: [July 11, 2022, 9:21pm UTC](https://discuss.elastic.co/t/recorded-future-v1-0-1-not-populating-intel-properly/309231/2 "2022-07-11T21:21:42Z")

</div>

Updated the integration to v1.1.0

Intel is still incomplete. No hash intel and limited for other IOC types.

Ran the following query for tags `ip`, `domain`, `url`, `hash`:

```auto
GET /logs-ti_recordedfuture.threat-default/_search
{
  "query": {
    "bool": {
      "must": [
        {"range": {"@timestamp": {"gte": "now-1d/d"}}},
        {"term": {"tags": {"value": "hash"}}}
      ]
    }
  }
}

```

Yields document counts:  
ip - 2654  
domain - 9975  
url - 8819  
hash - 0

These lists from Recorded Future currently have this many indicators:  
ip - 54677  
domain - 100000  
url - 100000  
hash - 99985

---

<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: [August 8, 2022, 9:21pm UTC](https://discuss.elastic.co/t/recorded-future-v1-0-1-not-populating-intel-properly/309231/3 "2022-08-08T21:21:46Z")

</div>

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