Microsoft Defender Vulnerability Management
GeneralSoftware components in Microsoft Defender Vulnerability Management
In brief
The article now explains how to identify vulnerable components, review affected devices, and find remediation guidance. It also clarifies why the security recommendation uses the Owning app label.
What Defender admins need to know
Administrators have clearer guidance for assessing remediation impact across the organization.
Summaries are generated from the documentation change itself.
Documentation change
View on Microsoft LearnThe comparison below shows only the changed extract. Use the full-page view for complete context.
Software components in Microsoft Defender Vulnerability Management
With visibility into which software components are present on a device, security administrators can focus their attention and resources on taking steps to reduce the associated risks.
This article explains how to use the Software components page in Defender Vulnerability Management to identify vulnerable components, review affected devices, and find remediation guidance.
When you select a security recommendation, you'll see in the flyout pane that the security recommendation is of type Owning app.
The security recommendation is labeled Owning app because there's no easy way to fix or patch a software component. The Owning app label allows security administrators to use the information about the software component to evaluate the effect of any proposed remediation on the whole organization.
View software components on devices
@@ -9,14 +9,14 @@ ms.collection: - m365-security - Tier1 ms.topic: how-to-ms.date: 06/12/2026+ms.date: 07/02/2026 appliesto: - Microsoft Defender Vulnerability Management - Microsoft Defender for Endpoint Plan 2 - Microsoft Defender XDR - Microsoft Defender for Servers Plan 1 & 2 ai-usage: ai-assisted-ms.custom: msecd-doc-authoring-1014+ms.custom: msecd-doc-authoring-1016 --- # Software components in Microsoft Defender Vulnerability Management@@ -29,6 +29,8 @@ It's becoming increasingly difficult for security administrators to identify and With visibility into which software components are present on a device, security administrators can focus their attention and resources on taking steps to reduce the associated risks. +This article explains how to use the **Software components** page in Defender Vulnerability Management to identify vulnerable components, review affected devices, and find remediation guidance.+ > [!NOTE] > The **Vulnerable components** page has been renamed to **Software components**. @@ -116,7 +118,7 @@ Or select **Open component page** from the component flyout pane and select the When you select a security recommendation, you'll see in the flyout pane that the security recommendation is of type **Owning app**. -This is because there's no easy way to fix or patch a software component. The **Owning app** label allows security administrators to use the information about the software component to evaluate the effect of any proposed remediation on the whole organization.+The security recommendation is labeled **Owning app** because there's no easy way to fix or patch a software component. The **Owning app** label allows security administrators to use the information about the software component to evaluate the effect of any proposed remediation on the whole organization. <a name="software-components-on-devices"></a> ### View software components on devices