Apply CI Lookup Rules to unmatched discovered items

[Syed14]

Hi, 

We have some discovered items which are unmatched but we noticed that they could be matched if we either update CI Lookup Rules or the unmatched CI itself. We know that we can reclassify a discovered item to some specific CI class which is good but still a manual process. So the question we have:

a) How can we manually apply/trigger CI matching rules (CI Lookup Rules) to some of the unmatched discovered items? 

b) If we modify an unmatched discovered item / or CI Lookup Rules is there any chance that it could be consider as a candidate to become a matched discovered item for a future integration run? in simple words is there any chance that an unmatched item can become a matched?

Thanks

[Ashutosh Munot1]

HI,

This is important: CI lookup rules are available only for the Qualys and Rapid7 vulnerability integrations.

So if the scanner is different then CI lookup rules wont work.

How are you importing the CIs?

Thanks,
Ashutosh

[Syed14]

Thanks for the response Ashutosh.

Yes I do know about that and we are using Rapid7 vulnerability integrations. Any idea on the 2 points that I asked?

Thanks

Syed

[SM6]

Hi Ashutosh, 

What rules are applied for Tenable? Does Tenable use CI Matching rules or Both?

Thank you.

[Chris McDevitt]

There two flavors of Tenable connector now. There is a Tenable connector developed by ServiceNow. There is also a Tenable connector developed by Tenable. 

The SN developed on used the standard VR framework and use CI Lookup Rules.

The Tenable developed once uses their own flavor called CI Matching Rules.