Skip to content

Commit be39def

Browse files
committed
Learn Editor: Update release-notes.md
1 parent f89ace2 commit be39def

File tree

1 file changed

+12
-3
lines changed

1 file changed

+12
-3
lines changed

articles/defender-for-cloud/release-notes.md

Lines changed: 12 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -23,15 +23,21 @@ If you're looking for items older than six months, you can find them in the [Arc
2323
## April 2024
2424
|Date | Update |
2525
|--|--|
26-
| April 1| [Containers multi cloud recommendations (GA)](#containers-multi-cloud-recommendations-ga) |
27-
26+
| April 2| [Containers multi cloud recommendations (GA)](#containers-multi-cloud-recommendations-ga) |
2827

2928
### Containers multi cloud recommendations (GA)
3029

31-
April 1, 2024
30+
April 2, 2024
3231

3332
As part of Defender for Containers multi cloud general availability, following recommendations are announced GA as well:
3433

34+
- For Azure
35+
36+
| **Recommendation** | **Description** | **Assessment Key** |
37+
| ------------------ | --------------- | ------------------ |
38+
| Azure registry container images should have vulnerabilities resolved| CContainer 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 |
39+
| Azure running container images should have vulnerabilities resolved| 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 |
40+
3541
- For GCP
3642

3743
| **Recommendation** | **Description** | **Assessment Key** |
@@ -45,6 +51,9 @@ As part of Defender for Containers multi cloud general availability, following r
4551
| ------------------ | --------------- | ------------------ |
4652
| AWS registry container images should have vulnerability findings resolved (powered by Microsoft Defender Vulnerability Management) | Scans your GCP registries container images 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. Scans your AWS registries container images 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. | c27441ae-775c-45be-8ffa-655de37362ce |
4753
| AWS 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 currently running in your Elastic 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. | 682b2595-d045-4cff-b5aa-46624eb2dd8f |
54+
55+
Please note that those recommendations would affect the secure score calculation.
56+
4857
## March 2024
4958

5059
|Date | Update |

0 commit comments

Comments
 (0)