You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/defender-for-cloud/transition-to-defender-vulnerability-management.md
+23-3Lines changed: 23 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Transition to Microsoft Defender Vulnerability Management
3
3
description: Learn how to transition to Microsoft Defender Vulnerability Management in Microsoft Defender for Cloud.
4
4
ms.topic: how-to
5
-
ms.date: 11/23/2023
5
+
ms.date: 01/08/2024
6
6
---
7
7
8
8
# Transition to Microsoft Defender Vulnerability Management
@@ -37,9 +37,9 @@ If your organization is ready to transition to container vulnerability assessmen
37
37
|[Azure registry container images should have vulnerability findings resolved (powered by Microsoft Defender Vulnerability Management)-Preview](https://ms.portal.azure.com/#view/Microsoft_Azure_Security_CloudNativeCompute/PhoenixContainerRegistryRecommendationDetailsBlade/assessmentKey/c0b7cfc6-3172-465a-b378-53c7ff2cc0d5)| Container image vulnerability assessment scans your registry for commonly known vulnerabilities (CVEs) and provides a detailed vulnerability report for each image. Resolving vulnerabilities can greatly improve your security posture, ensuring images are safe to use prior to deployment. | c0b7cfc6-3172-465a-b378-53c7ff2cc0d5 |
38
38
|[Azure running container images should have vulnerability findings resolved (powered by Microsoft Defender Vulnerability Management)](https://ms.portal.azure.com/#view/Microsoft_Azure_Security_CloudNativeCompute/ContainersRuntimeRecommendationDetailsBlade/assessmentKey/c609cf0f-71ab-41e9-a3c6-9a1f7fe1b8d5)| Container image vulnerability assessment scans your registry for commonly known vulnerabilities (CVEs) and provides a detailed vulnerability report for each image. This recommendation provides visibility to vulnerable images currently running in your Kubernetes clusters. Remediating vulnerabilities in container images that are currently running is key to improving your security posture, significantly reducing the attack surface for your containerized workloads. | c609cf0f-71ab-41e9-a3c6-9a1f7fe1b8d5 |
39
39
40
-
### Disable using the Qualys recommendations
40
+
### Disable using the Qualys recommendations for Azure commercial clouds
41
41
42
-
To disable the above Qualys recommendations using the Defender for Cloud UI:
42
+
To disable the above Qualys recommendations for Azure commercial clouds using the Defender for Cloud UI:
43
43
44
44
1. In the Azure portal, navigate to Defender for Cloud and open the **Recommendations** page.
45
45
@@ -59,6 +59,26 @@ To disable the above Qualys recommendations using the Defender for Cloud UI:
59
59
60
60
1. Fill out the remaining details and select create. Wait up to 30 minutes for the exemptions to take effect.
61
61
62
+
### Disable using the Qualys recommendations for national clouds
63
+
64
+
To disable the above Qualys recommendations for national clouds (Azure Government and Azure operated by 21Vianet) using the Defender for Cloud UI:
65
+
66
+
1. Go to **Environment settings** and select the relevant subscription you want to disable the recommendation on.
67
+
68
+
:::image type="content" source="media/transition-to-defender-vulnerability-management/environment-settings.png" alt-text="Screenshot showing how to select subscription in environment settings." lightbox="media/transition-to-defender-vulnerability-management/environment-settings.png":::
69
+
70
+
1. In the **Settings** pane, go to **Security policy**, and select the initiative assignment.
71
+
72
+
:::image type="content" source="media/transition-to-defender-vulnerability-management/security-policy.png" alt-text="Screenshot of security policy settings." lightbox="media/transition-to-defender-vulnerability-management/security-policy.png":::
73
+
74
+
1. Search for the Qualys recommendation and select **Manage effect and parameters**.
75
+
76
+
:::image type="content" source="media/transition-to-defender-vulnerability-management/qualys-recommendation.png" alt-text="Screenshot of Qualys recommendation." lightbox="media/transition-to-defender-vulnerability-management/qualys-recommendation.png":::
77
+
78
+
1. Change to **Disabled**.
79
+
80
+
:::image type="content" source="media/transition-to-defender-vulnerability-management/select-disabled.png" alt-text="Screenshot of disable button." lightbox="media/transition-to-defender-vulnerability-management/select-disabled.png":::
81
+
62
82
## Step 3: (optional) Update REST API and Azure Resource Graph queries
63
83
64
84
If you're currently accessing container vulnerability assessment results powered by Qualys programmatically, either via the Azure Resource Graph (ARG) Rest API or Subassessment REST API or ARG queries, you need to update your existing queries to match the new schema and/or REST API provided by the new container vulnerability assessment powered by Microsoft Defender Vulnerability Management.
0 commit comments