---
sourceDocument: Australia Security Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/security-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Security Management

ft:clusterId :

    - security

bundleId :

    - security

workflow :

    - Technology


---

# Reconcile unmatched discovered items

# Reconcile unmatched discovered items {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

Create a scheduled job to reconcile unmatched discovered items.

## Before you begin

Roles required: admin

## About this task

A vulnerable item (VI) consists of a vulnerability and a configuration item (CI). When a VI is created, the CI that is added to it at the time of creation might be an outdated one. Unmatched CI information is not reconciled if
the information in the CMDB changes. To reconcile, apply configuration Item (CI) lookup rules on the items that are in an unmatched state when the CMDB is updated with the latest CIs.

You can run a scheduled job demand to reapply the CI matching rule for the discovered items in an unmatched state. If the CI changes after reapplying the lookup rules, the discovered items are updated with the new CI. Impacted
detections and vulnerable items are also updated. For details, see [CI changes for discovered items](https://servicenow-prod.fluidtopics.net/D4NLUAp0jrLT1oLHbhXSxQ "When a configuration item (CI) on a discovered item (DI) changes, the impacted detections and vulnerable items (VIs) are updated. The risk score, assignment rules, group rules, and remediation target rule are reevaluated.").

## Procedure

1. Navigate to AllSecurity Operations \> Reconcile Unmatched Discovered Items.
2. On the Background Jobs page, click Create reconciliation job.
3. On the form, fill in the fields.  
   Note:  
   You can only edit the Parameters field.
   {#reapply-reconcile-unmatched-discovered-items__table_tqk_fb3_4mb__entry__2}

   | Field | Description |
   |-|-|
   | Number | Unique job number. |
   | Created by | User who created the job. |
   | Parameters | Parameters to reconcile the unmatched discovered items: * limit: Maximum number of discovered items to be reconciled. If you do not enter a value, 10,000 discovered items are reconciled. * firstDiscovereditem: First discovered item that must be reconciled. If you do not enter a value, the reconciliation process starts from the first discovered item. {#reapply-reconcile-unmatched-discovered-items__ul_nhc_glr_h4b} |
   | State | Current state of the background job. |
   | State description | Description of the current state of the background job. |
   | Job type | Type of job. The value is Reconcile unmatched discovered items. |
   | Started at | Time when the job started. |
   | Ended at | Time when the job was completed. |
   | Job duration | Total time taken to complete the job. |
   | Substate | Substate for the selected state. |
   | Notes | Number of records that were processed. |
   [Table 1. Background Job form]

   {#reapply-reconcile-unmatched-discovered-items__table_tqk_fb3_4mb}
4. Click Submit.  
   Note:  
   * To stop running the job, click Cancel.
   * You can't reconcile unmatched CIs or reapply CI lookup rules while you are importing hosts or vulnerable items.
   {#reapply-reconcile-unmatched-discovered-items__ul_ikx_3qp_nsb}
5. Starting with Vulnerability Response v26.0.11, you can "Reapply Look up Rules" for selected or filtered items in the discovered items table view.  
   Note:  
   From the above mentioned version, the reconcile unmatched discovered items scheduled job is retired.
6. **Optional:** Select AllSecurity Operations \>Reapply Look up Rules for selected or filtered items in the discovered items table.  
   Note:  
   If no filter is applied, the reapply option will be disabled.  
   After reapplying, a background job URL or an error message will pop-up, once the integration is running.
* **[Reapply CI lookup rules on selected discovered items](https://servicenow-prod.fluidtopics.net/Vr~wp9jUAL7Diul~tY2wvQ)**   
  Reapply the configuration item (CI) lookup rules on selected discovered items from the discovered item list view select actions. If the CI changes after you reapply the rules, the discovered items are updated with the new CI and impacted detections. Vulnerable items are also updated.
* **[Reapply CI Lookup Rules Enhancements](https://servicenow-prod.fluidtopics.net/QM6c1uxakGOrWAXiix4GRA)**   
  Reapply the configuration item (CI) lookup rules on selected discovered items like os and netbios.

**Related concepts**   

* [Steps to help prevent duplicate or orphaned records after running Vulnerability Response CI lookup rules](https://servicenow-prod.fluidtopics.net/DA2_cEfqqQXs7KYpaBa8GA "Take steps to help prevent duplicate or orphan records resulting from matching (configuration items (CIs) within the CMDB.")
* [De-duplicating existing configuration items](https://servicenow-prod.fluidtopics.net/Ap16VrNatM2VLHqh~E5jyg "Whenever configuration items (CIs) are updated through a deduplication task, the discovered items (DIs) that are related to those CIs are also updated. The vulnerable items (VIs) and detections are also updated with the CI.")  
**Related tasks**   

* [View and reclassify unmatched configuration items](https://servicenow-prod.fluidtopics.net/EaEAOf7Ltyr9QZ_PQwhXPA "Configuration items (CIs) that are not found in the Configuration Management Database (CMDB) are placed in a viewable list of discovered items. This list offers a convenient way to reclassify unmatched CIs.")
* [Resolve remediation tasks](https://servicenow-prod.fluidtopics.net/PiQ4It8j3oikPwb8I01MRA "The flexibility inherent in Vulnerability Response allows you to remediate vulnerabilities in whatever way suits your security organization.")

*[\>]: and then