---
sourceDocument: Xanadu Security Management
sourceDocumentLink: https://www.servicenow.com/docs/r/xanadu/security-management

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu Security Management

ft:clusterId :

    - security

bundleId :

    - security

workflow :

    - Technology


---

# CI changes for discovered items for Configuration Compliance

# CI changes for discovered items for Configuration Compliance {#ariaid-title1}

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

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.  
Note:  
Starting with v14.9 of Configuration Compliance, the following terms have been renamed:{#reapply-discovered-items-ci-changes-cc__entry__2}

| Terminology prior to v14.9 | Terminology v14.9 onwards |
|-|-|
| Test Result Group | Remediation Task |
| Group Rules | Remediation Task Rules |
| Policy | Test group |
[Table 1. Changes in terminology]

The external ID for the test result is updated and the risk score, assignment rules, remediation task rules, remediation target rule are reevaluated. If a test result exists with the same test and CI, the test results are updated
with the existing test result and the current test result is closed with the substate `invalidCI`. Work notes are added accordingly.

If you do not want to update the CI for the existing test result, set the property to false. In this case, if a CI changes, a new test result is created and the existing one is closed as an `invalidCI`.

