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/upcoming-changes.md
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -118,14 +118,16 @@ The following security recommendations will be released as GA and replace the V1
118
118
119
119
**Estimated date for change: May 2023**
120
120
121
-
We're announcing the release of Vulnerability Assessment for images in Azure container registries powered by Microsoft Defender Vulnerability Management (MDVM). This change includes the Public Preview release of two new container recommendations:
121
+
We're announcing the release of Vulnerability Assessment for images in Azure container registries powered by Microsoft Defender Vulnerability Management (MDVM). Within Defender for CSPM, findings used in the Security Explorer and attack paths rely on MDVM vulnerability assessment instead of the Qualys platform.
122
+
123
+
This change includes the Public Preview release of two new container recommendations within Defender CSPM:
122
124
123
125
|Recommendation | Description | Assessment Key|
124
126
|--|--|--|
125
-
| Container registry images should have vulnerability findings resolved (powered by Microsoft Defender Vulnerability Management)| 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. | XXX
126
-
| Running container images should have vulnerability findings resolved (powered by Microsoft Defender Vulnerability Management)| Container image vulnerability assessment scans container images running on your Kubernetes clusters for security vulnerabilities and exposes detailed findings for each image. Resolving the vulnerabilities can greatly improve your containers' security posture and protect them from attacks. | XXX
127
+
| Container registry images should have vulnerability findings resolved (powered by Microsoft Defender Vulnerability Management)| 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
128
+
| Running container images should have vulnerability findings resolved (powered by Microsoft Defender Vulnerability Management)| 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 that are currently running in your Kubernetes clusters. Remediating vulnerabilities in container images that are currently running is key to improving your security posture, significantly reducing attack surfaces for your containerized workloads within Kubernetes clusters. | XXX
127
129
128
-
In addition, the release includes renaming the current existing container recommendations as follows:
130
+
In addition, the release includes renaming the current existing container recommendations in Defender for Containers as follows:
129
131
130
132
- Container registry images should have vulnerability findings resolved (powered by Qualys)
131
133
- Running container images should have vulnerability findings resolved (powered by Qualys)
0 commit comments