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

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia Security Management

ft:clusterId :

    - security

bundleId :

    - security

workflow :

    - Technology


---

# CI lookup rules

# CI Lookup Rules for identifying configuration items from Configuration Compliance third-party vulnerability integrations {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 min. de leitura

When data is imported from a third-party integration, Configuration Compliance automatically uses host data to search for matches in the Configuration Management Database (CMDB). It does this using CI Lookup Rules. These rules are used to identify configuration items (CIs) and add them to the test result record to aid in
remediation.

As assets are imported, a lookup is performed first on the Discovered Items list using third-party IDs to find matches to configuration item (CIs) from prior imports. When a host ID match is found, it is used
as the Configuration item field in the test result record.

You can see how imported assets are mapped to CIs using the Discovered Items list. If a match is not found, or the cmdb_ci field is empty, the rules use the other host information to attempt to correctly
identify the CI. If a match is still not found, a placeholder CI is created and is designated as an Unmatched CI. See Unmatched CIs for more information on how those CIs are handled.

A new discovered item is created and mapped to this CI.  
Nota:  
CI lookup rules are available only for the Qualys Integration for Security Operations.  
CI lookup rules can be domain separated and are source-specific. Each source can have multiple deployments. Qualys can have multiple deployments of the Qualys Integration. Each deployment has its own set of CI Lookup Rules.  
Nota:  
CI lookup rules are shared by all deployments of the vulnerability integration. If a rule is deleted or modified, the deletion or changes affect all deployments of the vulnerability integration.  
When attempting a match, the first step is a vendor ID lookup for an exact match across source, source_instance, and vendor ID. Then, lookup rules are run in order, from lowest to highest and stop when a rule returns just a single CI as a match. If a rule is created in such a way that it returns more than one CI, only the first match is used.  
Nota:  
To avoid matching on low-level networking elements, if a matched CI is one of `dscy_switchport`, `cmdb_ci_network_adapter`, `cmdb_ci_nic`, or `cmdb_ci_ip_address`, the parent CI is returned.

A system property to exclude CI classes is available. This property is not available with upgrade. See [Ignore CI classes](https://servicenow-prod.fluidtopics.net/C_F5V0u~Hj1Du_9WZKVNRQ "To ignore some configuration item (CI) classes, for example Load Balancer [cmdb_ci_lb], when running CI Lookup Rules, set the ignoreCIClass [sn_sec_cmn.ignoreCIClass] system property.") for upgrade information and instructions on setting the property.

To make it easier to find matching issues, when a match is found, the CI lookup rule used to find it is added to the Discovered Item record in the CI matching rule field. Lookup rules are evaluated by lowest
Order value first.  
Some of the Qualys CI lookup rules shipped with the base system are:

* QUALYS HOST ID
* FQDN
* NetBIOS
* DNS
* IP
{#cc-ci-identifier-rules__ul_dms_5km_n1b}  
Some of the Microsoft Defender CI lookup rules shipped with the base system are:

* S3 Bucket
* Name
* Resource Id
{#cc-ci-identifier-rules__ul_pky_s3t_hvb}  
Some of the Palo Alto Prisma Cloud CI lookup rules shipped with the base system are:

* S3 Bucket
* Name
* Resource Id
{#cc-ci-identifier-rules__ul_kfb_t3t_hvb}

Importing test results data can be taxing on an instance and performance issues with resources can occur if rules are not carefully constructed. The logic used to iterate through and perform matching within the CMDB can result in lengthy processing times. To avoid any potential degradation of resources or performance complications, test any custom-written CI Lookup Rules or modifications to pre-defined
CI Lookup Rules. See [Steps to help prevent duplicate or orphaned records after running Vulnerability Response CI lookup rules](https://servicenow-prod.fluidtopics.net/eMY0emO8jGq6blA2BX8VtA "Take steps to help prevent duplicate or orphan records resulting from matching (configuration items (CIs) within the CMDB.") for more information on preventing duplicate orphan records, deleting data, and cleaning up data.

## Reapplying updated CI lookup rules {#cc-ci-identifier-rules__section_ad2_lpj_j4b}

When you change a CI lookup rule, click Apply Changes on the CI Lookup Rules list page to rerun all the rules on the discovered items that:

* Were matched by the updated rules
* Are not matched by any rule

{#cc-ci-identifier-rules__ul_byw_hrj_j4b} If the configuration item (CI) changes after reapplying the lookup rules, the discovered items are updated with the new CI. The test results are also updated. For more information, see [CI changes for discovered items for Configuration Compliance](https://servicenow-prod.fluidtopics.net/vBMxfn5sfFos3Ezu4SbVrQ "The default value of the property sn_sec_cmn.update_on_ci_change is true. So, when the configuration item (CI) for a discovered item is updated, the test results are updated as well.").