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

 Release :

    - zurich

ft:locale :

    - en-US

ft:publication_title :

    - Zurich Security Management

ft:clusterId :

    - security

bundleId :

    - security

workflow :

    - Technology


---

# Integration imports

# Configuration Compliance imported data for Microsoft Defender for Cloud Integration {#ariaid-title1}

* Release version: Zurich
* 
* Updated July 29, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read

Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Configuration Compliance imported data for Microsoft Defender for Cloud Integration

Configuration Compliance imports and organizes security policies, tests, authoritative sources, and test results from Microsoft Defender for Cloud within ServiceNow.
This integration enables you to view and remediate configuration compliance data efficiently by leveraging scheduled jobs that retrieve and update relevant compliance information from Microsoft Defender for Cloud.
Show full answer Show less  

## Key Features

* **Terminology updates:** Since version 14.9, terms such as Test Result Group and Rules have been renamed to Remediation Task Group and Remediation Task Rules to better reflect their purposes.
* **Test Groups and Tests:** Test groups are collections of configuration tests linked to authoritative documents. Tests organize asset scans and define governance controls. Scheduled jobs like Policy Definitions Integration and Assessment Metadata Integration import this data. Running these jobs in sequence ensures up-to-date data.
* **Authoritative Sources:** These sources provide mappings to industry standards (e.g., ISO 27001, PCI DSS) and are imported via the Compliance Standards \& Controls Integration scheduled job to support vulnerability alerts and compliance validation.
* **Asset Data and Cloud Attributes:** Resource tags and cloud attributes from Defender for Cloud are imported, enabling filtering and grouping in compliance assignments and remediation tasks. Tags are stored case-insensitively and intended for use in condition builders.
* **Test Results Import:** Test results are imported by the Assessment Integration scheduled job, which uses a Start Time parameter to incrementally fetch status changes. A weekly Comprehensive Assessment Integration imports all non-passed test results from the past seven days to maintain accuracy.
* **CI Lookup Rules:** These rules automatically identify and link configuration items (CIs) in the CMDB to imported test results using resource data like Resource ID and Name, facilitating remediation.
* **Container Vulnerability Items:** Container image vulnerabilities are imported using a dedicated scheduled job. The job can import all data or only data updated after a specified start time, allowing flexible data ingestion control.

## Practical Benefits

* Enables centralized visibility of Microsoft Defender for Cloud compliance data within ServiceNow Configuration Compliance.
* Automates data synchronization through scheduled jobs, ensuring compliance policies, tests, authoritative sources, and test results remain current.
* Supports detailed filtering and grouping of assets using cloud attributes and resource tags to tailor compliance assignments and remediation.
* Facilitates accurate CI association in the CMDB to streamline remediation workflows and track configuration compliance effectively.
* Improves container security management by integrating container vulnerability data for vulnerability tracking and remediation.

## Usage Recommendations

* Run integrations in the recommended sequence: Policy Definitions Integration, then Assessment Metadata Integration, followed by Compliance Standards \& Controls Integration, and finally Assessment Integration.
* Utilize the Start Time parameter in Assessment and Container Image Vulnerabilities integrations to control incremental data updates and optimize performance.
* Monitor scheduled jobs within ServiceNow to ensure successful data imports and troubleshoot any issues promptly.  
Configuration Compliance imports policies, tests, authoritative sources, and test results from third-party integrations and stores them in modules for viewing.  
Note:  
Starting with v14.9 of Configuration Compliance, the following terms have been renamed:{#cc-asc-policies__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]

## Test groups {#cc-asc-policies__section_jcn_mbs_kbb}

A group of configuration tests constitutes a test group. Test groups are related to authoritative documents and test records, and they can be modified to meet the needs of your organization. One configuration test can belong to
multiple test groups.  
If the Microsoft Defender for Cloud Integration is installed, test groups are retrieved and populated by the Policy Definitions Integration scheduled job. Navigate to AllMicrosoft Defender for Cloud IntegrationAdministrationIntegrationsPolicy Definitions Integration to view the scheduled job.  
Note:  
If you choose to run the integration manually, run the Policy Definitions Integration first.

## Tests {#cc-asc-policies__section_cx4_nbs_kbb}

Tests are libraries of data records that organize scans of computing assets. Configuration tests define how assets must be governed.

A Configuration Compliance test is the mechanism third-party integration applications use to group assets by test results type.  
If the Microsoft Defender for Cloud Integration is installed, the Assessment Metadata Integration scheduled job retrieves the tests. Navigate to AllIntegrationPrimary IntegrationsAssessment Metadata Integration to view the scheduled job.  
Note:  
If you choose to run the integration manually, run the Assessment Metadata Integration after the Policy Definitions Integration.

The test group to which a test belongs is populated in the Test Groups column of the Tests list.

## Authoritative sources {#cc-asc-policies__section_isy_nbs_kbb}

Configuration Compliance uses authoritative sources and citations when generating vulnerability alerts for tests. Authoritative sources usually map to sections of published industry standards, such as ISO 27001 and PCI DSS 3.2.1.

These source records contain references to information about known software and hardware configuration issues from experts in the field of computer security. They define requirements for security policies and procedures.  
If the Microsoft Defender for Cloud Integration is installed, the Compliance Standards \& Controls scheduled job retrieves the authoritative sources and citations. Navigate to AllMicrosoft Defender for Cloud IntegrationIntegrationsCompliance Standards \& Controls Integration to view this scheduled job.  
Note:  
If you choose to run the integration manually, run the Compliance Standards \& Controls Integration after the Assessment Metadata Integration.

## Assets {#cc-asc-policies__section_vqb_nvl_mqb}

The Assessment integration provides vital information such as resource tags and cloud attributes. This information is displayed in the Discovered Item form.  It is used primarily for filtering in  Configuration Compliance Assignment and Remediation Task Rules.

* Resource tags: All cloud resource tags are imported as host tags as part of the  Assessment integration. The cloud tags for any cloud resource type are stored here, whether the resource is a host or not.
  * Tag storage is not case-sensitive. If a  Tokyo  tag is created, then a  TOKYO  tag cannot be stored in the Host tag table. Tokyo and TOKYO are considered to be the same host tag. Whichever tag was imported first wins.
  * Using host tags as a group key in a group rule can have unexpected results. Host tags are intended for use only in the condition builder.
  {#cc-asc-policies__ul_lgd_rnc_htb}
* Cloud attributes for assets: Following are the cloud attributes that the integrations retrieve from Microsoft Defender for Cloud:
  * Cloud Account
  * Cloud Region
  * Cloud Resource Type
  * Cloud Service Provider
  {#cc-asc-policies__ul_vmk_14c_htb}
{#cc-asc-policies__ul_llk_zmc_htb}

## Test results {#cc-asc-policies__section_zfx_b1t_kbb}

Configuration Compliance does not calculate the test results, but imports them as part of a third-party integration. Once they are viewable in Configuration Compliance, they are remediated using Remediation Tasks.

If the Microsoft Defender for Cloud integration is installed, the Assessment Integration scheduled job retrieves the test results. Navigate to AllMicrosoft Defender for Cloud IntegrationIntegrationsAssessment Integration to view this scheduled job.

The Assessment Integration import is the only integration that uses the Start Time parameter in the Integration Details tab. All other Configuration Compliance imports bring in all available data regardless of Start Time.

When the Assessment Integration import is complete, an event is started to trigger end-of-import calculations.

The Assessment Integration pulls the data assessments only if there is a status change from the last successful integration run for the last one day by default. So, if the assessment fails continuously for
the past few days, the integration will not fetch the assessment as there is no status change for the assessment. To keep the test results up to date with the defender assessments, a new Comprehensive Assessment Integration is added which pulls the data from the past seven days. It runs weekly and pulls all the test results, which are not passed.

## CI lookup rules for identifying CIs from Microsoft Defender for Cloud integrations {#cc-asc-policies__section_psy_q34_2rb}

When data is imported from a third-party integration, Configuration Compliance automatically uses resource data to search for matches in the Configuration Management Database (CMDB), using CI Lookup Rules. These rules are used to identify the configuration items (CIs) and add them to the test result record to aid in remediation. Base system CI lookup rules are
available for Resource ID, Name, and S3 Bucket. For more information on CI lookup rules, see [CI lockup rules for Microsoft Defender for Cloud Integration for Security Operations](https://www.servicenow.com/docs/OAj3Tj8ELAcLYAEXeJ_glw "You can use the configuration item (CI) lookup rules for the Microsoft Defender for Cloud Integration and Palo Alto Prisma Cloud integrations to find a correct match to commonly used resource types in the Configuration Management Database (CMDB).").

## Container vulnerability item {#cc-asc-policies__var.mstv-sem}

When the Microsoft Defender for Cloud integration is configured, the Container Image Vulnerabilities scheduled job retrieves container vulnerable items.

Navigate to AllMicrosoft Defender Integration for Security Exposure ManagementMicrosoft Defender for Cloud IntegrationIntegrationsContainer Image Vulnerabilities Integration.  
The Container Image Vulnerabilities Integration import uses the Start time parameter on the Integration Details tab to control data ingestion:

* If Start time is empty, the integration imports all available container vulnerability data.
* If Start time is set, the integration imports only data created or updated after the specified time.

*[\>]: and then