---
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


---

# View and reclassify unmatched configuration items

# View and reclassify unmatched configuration items {#ariaid-title1}

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

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.

## Before you begin

Role required:

sn_vul.read (minimum to view Unmatched CIs)
and

itil or asset (to reclassify)

Persona and granular roles are available to help you manage what users and groups can see and do in the Vulnerability Response application. For an initial assignment of the persona roles in Setup Assistant, see [Assign the Vulnerability Response persona roles using Setup Assistant](https://servicenow-prod.fluidtopics.net/msi8kaFkGNjyRib_XBHEzQ "Assign the Vulnerability Response persona roles to groups or users with Setup Assistant."). For more information about managing granular roles, see [Manage persona and granular roles for Vulnerability Response](https://servicenow-prod.fluidtopics.net/WeKNf9YHNMJmJIA6yCsRvA "After you complete your initial assignment of persona roles using Setup Assistant, manage additional granular role assignments to users or groups from the User Administration module in your instance.").

## About this task

As a Vulnerability Analyst you can view unmatched CIs.

The reclassify action is available only on sn_sec_cmn_unmatched_ci class CIs, when you have either the itil or asset roles. Once a CI has been reclassified, it cannot be reclassified using the UI. You can
reclassify, from the CI form or the CI list view, by changing the class value. For more information, see [Reclassify a CI](https://www.servicenow.com/docs/access?context=t_ManuallyReclassifyCI&version=australia&pubname=australia-servicenow-platform&ft:locale=en-US).

## Procedure

1. Navigate to AllSecurity OperationsCMDBDiscovered Items.
2. To review, click each item.
3. To make corrections to the information in the Discovered Item form fields, edit in this page, and right-click Save.  
   Any data added to or left in these fields is transferred to the resulting Configuration Item when it is reclassified.
4. If everything looks correct, click Reclassify.
5. From the choice list, select a Class Name and click Submit.  
   The Discovered Item Class is updated, the State field is changed to Reclassified, and all data is in the CMDB.
**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**   

* [Reconcile unmatched discovered items](https://servicenow-prod.fluidtopics.net/XRpmXjp2BwfNkGu9fKxV5g "Create a scheduled job to reconcile unmatched discovered items.")
* [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