---
title: Vulnerability Response patch orchestration integration with Microsoft SCCM
description: The Vulnerability Response integration with the Microsoft System Center Configuration Manager \(SCCM\) supports patch management and deployment for critical vulnerabilities across your assets.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/security-management/vulnerability-response/mspatch-integration.html
release: australia
product: Vulnerability Response
classification: vulnerability-response
topic_type: concept
last_updated: "2026-07-23"
reading_time_minutes: 6
breadcrumb: [Vulnerability Response integrations, Vulnerability Response, Unified Security Exposure Management, Security Operations]
---

# Vulnerability Response patch orchestration integration with Microsoft SCCM

The Vulnerability Response integration with the Microsoft System Center Configuration Manager \(SCCM\) supports patch management and deployment for critical vulnerabilities across your assets.

## Patch orchestration with Vulnerability Response

Patch orchestration with Vulnerability Response uses scheduled imports from third-party solution integrations, patch vendors, and vulnerability scanners. Scanner detection data matches the assets in your environment to vulnerabilities and to the patch updates that can fix them. You submit patch requests for approval, schedule patch updates to resolve vulnerable items, and monitor remediation progress all from your ServiceNow AI Platform® instance.

The integration uses two separate connections to communicate with Microsoft SCCM. A JDBC connection retrieves ingestion data \(collections, devices, patches, and deployments\) directly from the SCCM database. A WMI connection uses the Microsoft SCCM API to deploy patches to target machines.

## Key capabilities

When the Vulnerability Response Patch Orchestration with the Microsoft SCCM application is used with the ServiceNow® Vulnerability Solution Management, Patch Orchestration, and Vulnerability Response applications, vulnerability managers and analysts can perform the following tasks:

-   View context and information about patch types and vendor solutions.
-   View and monitor vulnerability and solution data and remediation progress from records in the Vulnerability Response Workspaces.

IT specialists and remediation owners can perform the following tasks:

-   Deploy patches supported by the Microsoft SCCM product for their Windows, CentOS, macOS, Oracle, and other assets at regular, scheduled intervals during off-hours to avoid conflicts with work.
-   Identify unpatched assets with vulnerabilities, or assets that or were not successfully updated by scheduled patches from imported detection data from third-party scanners.
-   Schedule available patches from either the IT Remediation Workspace or from the classic UI for vulnerable, unpatched assets from patch update, remediation task, and discovered item records.
-   Starting with the September 2026 release, deploy multiple patches to multiple collections in a single deployment, instead of one patch to one collection at a time. Multi-patch deployments automatically create a Software Update Group in Microsoft SCCM to bundle the patches.

## Key terms in the Vulnerability Response and Microsoft SCCM applications

<table id="table_btn_pvx_zjc"><thead><tr><th>

Term

</th><th>

Description

</th></tr></thead><tbody><tr><td>

Configuration item \(CI\)

</td><td>

Existing assets listed in your Configuration Management Database \(CMDB\). Microsoft SCCM calls CIs devices.

</td></tr><tr><td>

Collections and device collections

</td><td>

A group of assets in the Microsoft SCCM product.

</td></tr><tr><td>

Vulnerable item

</td><td>

An imported vulnerability that matches an existing asset in your CMDB.

</td></tr><tr><td>

Instance

</td><td>

A distinct account of the Microsoft SCCM application. Each user account can be an instance in the Microsoft SCCM application. This term also refers to a unique, secure web address for a ServiceNow AI Platform instance.

</td></tr><tr><td>

Integration

</td><td>

A scheduled job in the ServiceNow AI Platform that retrieves information from a third-party source, such as the Microsoft SCCM integration.

</td></tr><tr><td>

JDBC connection

</td><td>

The connection the integration uses to retrieve ingestion data \(collections, devices, patches, and deployments\) directly from the SCCM SQL Server database, established over Java Database Connectivity \(JDBC\) and resolved on the MID Server.

</td></tr><tr><td>

WMI connection

</td><td>

The connection the integration uses to deploy patches to target machines through the Microsoft SCCM API over Windows Management Instrumentation \(WMI\), resolved on the MID Server.

</td></tr><tr><td>

Solution

</td><td>

There are two types of solutions: potential and preferred. A potential solution might address a vulnerability. Vulnerabilities often have many potential solutions. A preferred solution is the most effective solution for a specific, detected vulnerability.

</td></tr><tr><td>

Patches

</td><td>

Software updates that fix vulnerabilities. In the Microsoft SCCM application, patches are called Patches. For example, Microsoft SCCM has patches for Windows, CentOS, macOS, Oracle, and other products.

</td></tr><tr><td>

Preferred patch

</td><td>

Software updates that fix specific vulnerabilities. After deployment, patches map to the vulnerable items related to specific vulnerabilities and fix them.

</td></tr><tr><td>

Remediation task \(vulnerability groups before v15.0 of Vulnerability Response\)

</td><td>

Lists of vulnerable items in the Vulnerability Response application that require action to fix vulnerabilities.

</td></tr><tr><td>

Deployment

</td><td>

For this integration, deployment refers to applying, initiating, or scheduling a patch to a machine. Deploy patches downloaded from Microsoft SCCM in your ServiceNow AI Platform by selecting discovered items, patches, or remediation tasks from individual records in Vulnerability Response. Deploy patches with scheduled jobs to individual machines or computer groups. Deployment in the ServiceNow AI Platform can also refer to an integration that supports multi-source. A single integration instance is referred to as a deployment. A deployment refers to the integrations and products across your environment. For example, you might have multiple deployments of the Microsoft SCCM Vulnerability integration in your environment.

</td></tr></tbody>
</table>## Vulnerability Solution Management and the Vulnerability Response patch orchestration integration with Microsoft SCCM

The Vulnerability Solution Management application is a ServiceNow AI Platform application that correlates your vulnerability findings with the breakdown of the solutions \(patches\) that remediate them. Identify the software patches from third parties for products and services, configuration updates, and other controls that have the highest impact for your organization. Along with third-party scanner information, the Solution Management for Vulnerability Response, Vulnerability Response, and the Vulnerability Response Patch Orchestration with Microsoft SCCM applications work together to roll preferred patches up from the solution, to the vulnerability, to the vulnerable item to help you fix and close vulnerabilities to your environment. The Solution Management for Vulnerability Response, Vulnerability Response, and the Vulnerability Response Patch Orchestration Microsoft SCCM integration applications are all available in the ServiceNow® Store.

## Required ServiceNow AI Platform roles

The integration installation, configuration, and remediation tasks require the following roles in your  ServiceNow AI Platform instance.

|Role|Description|
|----|-----------|
|admin|Obtains entitlements for applications in the ServiceNow Store and installs them on ServiceNow AI Platform instances.|
|sn\_vul.vulnerability\_admin|Activates applications in the ServiceNow AI Platform instance and completes configuration of the Vulnerability Response application. This role has complete access to the Vulnerability Response \(VR\) application and its records. This admin user configures all VR applications, rules, and third-party integrations.|
|sn\_vul\_sccm.configure\_integration|Configures the Microsoft SCCM Patch Orchestration Integration application. This role contains the sn\_vul\_sccm.read\_integration granular role.|
|sn\_vul\_sccm.read\_integration|Provides read-only access to records in the Vulnerability Response and Microsoft SCCM Patch Orchestration Integration application and patch orchestration data.|
|sn\_vul\_patch\_orch.configure\_patch|Configures and applies patches.|
|sn\_vul\_patch\_orch.read\_patch|Provides read-only access to patch information.|
|Approvers|Assign users to the Approver level 1 and Approver level 2 approver groups to require approval of submitted patch requests before deployment.|

For more information about assigning these roles using the Setup Assistant, see [Assign the Vulnerability Response persona roles using Setup Assistant](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-response/vr-assign-personas_SA.md).

## CI lookup rules

When data is imported from the Microsoft SCCM application, the Vulnerability Response application automatically searches for matches in the Configuration Management Database \(CMDB\) using Resource ID data. CI lookup rules are used to identify CIs \(assets\) and add them automatically to vulnerable item \(VI\) records when VIs are created. The following CI lookup rules are shipped with the base system and are used to identify CIs \(assets\) and add them to the discovered items.

This lookup rule relies on the data brought in by the Service graph connector with SCCM. Install and run the CMDB integration before running the SCCM integrations. If you have multiple installations of the SCCM server, you can configure the Service graph connector connection alias in the SCCM patch orchestration configuration page.

## MID Server

The Vulnerability Response Patch Orchestration with Microsoft SCCM is an on-premises integration. It requires a standalone Windows MID Server that is not part of a MID Server cluster.

Starting August 2026 release, the MID Server is used differently depending on what the integration is doing:

-   For data ingestion \(collections, devices, patches, and deployments\), the integration connects directly to the SCCM database using Java Database Connectivity \(JDBC\) over a SQL Server connection resolved on the MID Server. JDBC ingestion doesn't require opening a firewall port for Windows Management Instrumentation \(WMI\) remote procedure calls.
-   For patch deployment, the integration continues to use the Microsoft SCCM API over WMI, run through the same MID Server.

Both connections are configured on the Microsoft SCCM Patch management Integration configuration form, on separate JDBC Connection and WMI Connection tabs. See [Configure Microsoft SCCM Patch Orchestration](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-response/vr-mspatch-config.md).

**Related topics**  


[Prepare for the Vulnerability Response patch orchestration integration with Microsoft SCCM](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-response/vr-mspatch-setup-checklist.md)