# Elastic's Tenable Vulnerability Management Integration - Re-injesting Lost Data
**URL:** https://discuss.elastic.co/t/elastics-tenable-vulnerability-management-integration-re-injesting-lost-data/349131
**Category:** Elasticsearch
**Tags:** painless
**Created:** [December 12, 2023, 9:55am UTC](https://discuss.elastic.co/t/elastics-tenable-vulnerability-management-integration-re-injesting-lost-data/349131 "2023-12-12T09:55:42Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@longansoju](https://discuss.elastic.co/u/longansoju)
#### Post date: [December 12, 2023, 9:55am UTC](https://discuss.elastic.co/t/elastics-tenable-vulnerability-management-integration-re-injesting-lost-data/349131/1 "2023-12-12T09:55:42Z")
TDLR: is there a way to force elastic to injest all existing data for the past month from my tenable source?
For those that prefer an in-depth explaination:
I was tasked with coming out with a Tenable Dashboard that shows asset and vulnerability info. Since both are in seperate data streams, I decided to create a custom pipeline that enriches my vulnerability datastream with asset information. This custom pipeline is executed in the last time of tenable's vulnerability pipeline.
logs-tenable\_io.vulnerability@custom (processors for my custom pipeline)
```auto
{
"enrich": {
"field": "host.id",
"policy_name": "enrich_tenable_vulnerability",
"target_field": "asset-data",
"ignore_missing": true
}
},
{
"script": {
"lang": "painless",
"source": "for (def tag : ctx['asset-data']['tenable_io']['asset']['tags']) {\n if(tag[\"key\"] == \"Location\") {\n ctx[\"Region\"] = tag['value']\n }\n ctx[tag[\"key\"]] = tag['value'];\n }"
}
}
]
```
The issue here was that initially, I reindexed my existing asset index and created my enrich policy based on it.
```auto
PUT /_enrich/policy/enrich_tenable_vulnerability
{
"match": {
"indices": "ds-logs-tenable_io.asset-tenable",
"match_field": "host.id",
"enrich_fields": ["tenable_io.asset.tags.key","tenable_io.asset.tags.value"]
}
}
```
I only found out today that the reindexed index doesn't injest data like the original one does. Therefore my enrich preprocessor has only been enriching my vulnerability dataset based on old asset data, resulting in a loss in data.
I've already changed my match index to the correct asset index
```auto
PUT /_enrich/policy/enrich_tenable_vulnerability
{
"match": {
"indices": ".ds-logs-tenable_io.asset-tenable-*",
"match_field": "host.id",
"enrich_fields": ["tenable_io.asset.tags.key","tenable_io.asset.tags.value"]
}
}
```
My question here is, since I lost so much data due my flawed enrich policy logic, is there a way i could re-injest all existing data from my tenable source for the past month?
Would really appreciate some guidance and support since I'm still relatively new to elastic!
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [January 9, 2024, 9:56am UTC](https://discuss.elastic.co/t/elastics-tenable-vulnerability-management-integration-re-injesting-lost-data/349131/2 "2024-01-09T09:56:07Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.