Tenable Integration creating a new CI in Unclassed Hardware
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-01-2023 01:17 AM - edited 12-01-2023 04:21 AM
Hi All,
I ran the Tenable integration and it created around 7 Vulnerable Item records against the configuration item - sv118883.zit.xyz.com.
Problem: The configuration item - sv118883.zit.xyz.com is having the IP Address - 140.8.2.11 and the same IP address is mapped to 5 other Configuration items from Different classes of CMDB.
Question: Even though there are 5 different CIs with the same IP address already existing in the instance, the CI lookup rule didn't pick any, and rather the IRE created a new CI in unclassed Hardware, why?
What should I fix to pick the Already Existing CI? I have already tried rearranging the order of the CI lookup rules but it didn't work. I think the one highlighted in the below picture should be the correct one for my understanding.
Regards,
Maloy Banerjee