- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-05-2020 05:45 AM
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
Solved! Go to Solution.
- Labels:
-
Vulnerability Response
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-21-2021 12:13 PM
I haven't tested it yet but happy so see this feature as a part of new release which was missing in previous versions..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-07-2021 04:32 AM
Thanks for the response.
So If I understand correctly once an unmatched discovered item is created there is no OOTB process/automation which in the future tries to find that maybe there is a matching CI exists now?
Or it will keep in unmatched state until someone manually reclassify it?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-07-2021 05:23 AM
Hi,
In the latest release check out how unmatched hosts' are now created in the CMDB:
https://docs.servicenow.com/bundle/paris-security-management/page/product/vulnerability-response/concept/ci-creation-using-IRE.html
This is an important advancement because the IRE is how ServiceNow Discovery works with the CMDB by creating the unmatched host in one of the two new classes:
Unclassed Hardware (cmdb_unclassed_hardware_ci
)
Incomplete IP Identified Device (cmdb_ci_incomplete_ip
)
So because VR now uses the IRE and ServiceNow Discovery uses the IRE.... IF that same host is now detected by ServiceNow Discovery it can be automatically reclassified based on the more specific data identified by ServiceNow Discovery.
The key here is to have a plan that involved the ServiceNow Discovery team, the CMDB team, and the asset management team.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-21-2021 12:13 PM
I haven't tested it yet but happy so see this feature as a part of new release which was missing in previous versions..