Skip to content

Commit c1609a9

Browse files
author
David Curwin
committed
update dec 18 b
1 parent ca57a31 commit c1609a9

6 files changed

+85
-53
lines changed

articles/defender-for-cloud/TOC.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -596,7 +596,7 @@
596596
- name: How does Defender for Containers work?
597597
displayName: containers
598598
href: defender-for-containers-architecture.md
599-
- name: Vulnerability assessment for Azure powered by Qualys
599+
- name: Vulnerability assessment for Azure powered by Qualys (Deprecated)
600600
displayName: ACR, registry, images, qualys
601601
href: defender-for-containers-vulnerability-assessment-azure.md
602602
- name: Vulnerability assessments powered by Microsoft Defender Vulnerability Management

articles/defender-for-cloud/common-questions-microsoft-defender-vulnerability-management.md

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -28,19 +28,19 @@ Vulnerability assessment for runtime supports both agentless and agent-based dep
2828

2929
## Is there any difference in supported environments between the Qualys and Microsoft Defender Vulnerability Management powered offerings?
3030

31-
Both offerings support registry scan for Azure Container Registry and runtime vulnerability assessment for Azure Kubernetes Services.
31+
Both offerings support registry scan for ACR and ECR as well as runtime vulnerability assessment for AKS and EKS.
3232

3333
## How complicated is it to enable container vulnerability assessment powered by Microsoft Defender Vulnerability Management?
3434

35-
The Microsoft Defender Vulnerability Management powered offering is already enabled by default in all supported plans. For instructions on how to re-enable Microsoft Defender Vulnerability Management with a single click if you previously disabled this offering, see [Enabling vulnerability assessments in Azure powered by Microsoft Defender Vulnerability Management](enable-vulnerability-assessment.md).
35+
The Microsoft Defender Vulnerability Management powered offering is already enabled by default in all supported plans. For instructions on how to re-enable Microsoft Defender Vulnerability Management with a single click if you previously disabled this offering, see [Enabling vulnerability assessments powered by Microsoft Defender Vulnerability Management](enable-vulnerability-assessment.md).
3636

3737
## How long does it take for a new image to be scanned with the Microsoft Defender Vulnerability Management powered offering?
3838

39-
In Azure, new images are typically scanned in a few minutes, and it might take up to an hour in rare cases.
39+
In Azure, new images are typically scanned in a few minutes, and it might take up to an hour in rare cases. In AWS, new images are typically scanned within a few hours, and might take up to a day in rare cases.
4040

4141
## Is there any difference between scanning criteria for the Qualys and Microsoft Defender Vulnerability Management offerings?
4242

43-
Container vulnerability assessment powered by Microsoft Defender Vulnerability Management supports all scan triggers supported by Qualys, and in addition also supports scanning of all images pushed in the last 90 days to a registry. For more information, see [scanning triggers for Microsoft Defender Vulnerability Management](agentless-container-registry-vulnerability-assessment.md#scan-triggers).
43+
Container vulnerability assessment powered by Microsoft Defender Vulnerability Management for Azure supports all scan triggers supported by Qualys, and in addition also supports scanning of all images pushed in the last 90 days to a registry. For more information, see [scanning triggers for Microsoft Defender Vulnerability Management for Azure](agentless-vulnerability-assessment-azure.md#scan-triggers). Container vulnerability assessment powered by Microsoft Defender Vulnerability Management for AWS supports a subset of the scanning criteria. For more information, see [scanning triggers for Microsoft Defender Vulnerability Management for AWS](agentless-vulnerability-assessment-aws.md#scan-triggers).
4444

4545
## Is there a difference in rescan period between the Qualys and Microsoft Defender Vulnerability Management offerings?
4646

@@ -64,4 +64,5 @@ There's no difference for coverage of language specific packages between the Qua
6464
## Next steps
6565

6666
- Learn about [Defender for Containers](defender-for-containers-introduction.md)
67-
- Learn more about [container image vulnerability assessment scanning powered by Microsoft Defender Vulnerability Management](agentless-container-registry-vulnerability-assessment.md)
67+
- Learn more about [Vulnerability assessments for Azure with Microsoft Defender Vulnerability Management](agentless-vulnerability-assessment-azure.md)
68+
- Learn more about [Vulnerability assessments for AWS with Microsoft Defender Vulnerability Management](agentless-vulnerability-assessment-aws.md)

articles/defender-for-cloud/defender-for-containers-vulnerability-assessment-azure.md

Lines changed: 12 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Vulnerability assessment for Azure powered by Qualys
2+
title: Vulnerability assessment for Azure powered by Qualys (Deprecated)
33
description: Learn how to use Defender for Containers to scan images in your Azure Container Registry to find vulnerabilities.
44
author: dcurwin
55
ms.author: dacurwin
@@ -8,7 +8,17 @@ ms.topic: how-to
88
ms.custom: ignite-2022, build-2023
99
---
1010

11-
# Vulnerability assessment for Azure powered by Qualys
11+
# Vulnerability assessment for Azure powered by Qualys (Deprecated)
12+
13+
> [!IMPORTANT]
14+
>
15+
> The Defender for Cloud Containers Vulnerability Assessment powered by Qualys is now on a retirement path completing on **March 1st, 2024**. If you are currently using container vulnerability assessment powered by Qualys, start planning your transition to [Vulnerability assessments for Azure with Microsoft Defender Vulnerability Management](agentless-vulnerability-assessment-azure.md) or [Vulnerability assessments for AWS with Microsoft Defender Vulnerability Management](agentless-vulnerability-assessment-aws.md).
16+
>
17+
> - For more information about our decision to unify our vulnerability assessment offering with Microsoft Defender Vulnerability Management, see [this blog post](https://techcommunity.microsoft.com/t5/microsoft-defender-for-cloud/defender-for-cloud-unified-vulnerability-assessment-powered-by/ba-p/3990112).
18+
>
19+
> - For more information about migrating to our new container vulnerability assessment offering powered by Microsoft Defender Vulnerability Management, see [Transition from Qualys to Microsoft Defender Vulnerability Management](transition-to-defender-vulnerability-management.md).
20+
>
21+
> - For common questions about the transition to Microsoft Defender Vulnerability Management, see [Common questions about the Microsoft Defender Vulnerability Management solution](common-questions-microsoft-defender-vulnerability-management.md).
1222
1323
Vulnerability assessment for Azure, powered by Qualys, is an out-of-box solution that empowers security teams to easily discover and remediate vulnerabilities in Linux container images, with zero configuration for onboarding, and without deployment of any agents.
1424

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

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,13 +24,46 @@ If you're looking for items older than six months, you can find them in the [Arc
2424

2525
| Date | Update |
2626
|--|--|
27+
| December 14 | [General availability of Containers Vulnerability Assessment powered by Microsoft Defender Vulnerability Management in Azure Government and Azure operated by 21Vianet](#general-availability-of-containers-vulnerability-assessment-powered-by-microsoft-defender-vulnerability-management-in-azure-government-and-azure-operated-by-21vianet) |
28+
| December 14 | [Public preview of Windows support for Containers Vulnerability Assessment powered by Microsoft Defender Vulnerability Management](#public-preview-of-windows-support-for-containers-vulnerability-assessment-powered-by-microsoft-defender-vulnerability-management) |
2729
| December 13 | [Retirement of AWS container vulnerability assessment powered by Trivy](#retirement-of-aws-container-vulnerability-assessment-powered-by-trivy) |
2830
| December 13 | [Agentless container posture for AWS in Defender for Containers and Defender CSPM (Preview)](#agentless-container-posture-for-aws-in-defender-for-containers-and-defender-cspm-preview) |
2931
| December 13 | [Deny effect - replacing deprecated policies](#deny-effect---replacing-deprecated-policies) |
3032
| December 13 | [General availability (GA) support for PostgreSQL Flexible Server in Defender for open-source relational databases plan](#general-availability-support-for-postgresql-flexible-server-in-defender-for-open-source-relational-databases-plan) |
3133
| December 12 | [Container vulnerability assessment powered by Microsoft Defender Vulnerability Management now supports Google Distroless](#container-vulnerability-assessment-powered-by-microsoft-defender-vulnerability-management-now-supports-google-distroless) |
3234
| December 4 | [Defender for Storage alert released for preview: malicious blob was downloaded from a storage account](#defender-for-storage-alert-released-for-preview-malicious-blob-was-downloaded-from-a-storage-account) |
3335

36+
## General availability of Containers Vulnerability Assessment powered by Microsoft Defender Vulnerability Management in Azure Government and Azure operated by 21Vianet
37+
38+
December 14, 2023
39+
40+
Vulnerability assessment (VA) for Linux container images in Azure container registries powered by Microsoft Defender Vulnerability Management is released for General Availability (GA) in Azure Government and Azure operated by 21Vianet. This new release is available under the Defender for Containers and Defender for Container Registries plans.
41+
42+
As part of this change, the following recommendations are released for GA, and are included in secure score calculation:
43+
44+
| Recommendation name | Description | Assessment key |
45+
| ------------------------------------------------------------ | ------------------------------------------------------------ | ------------------------------------ |
46+
| Azure registry container images should have vulnerabilities resolved (powered by Microsoft Defender Vulnerability Management) | Container image vulnerability assessments scan your registry for commonly known vulnerabilities (CVEs) and provide 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 |
47+
| Running container images should have vulnerability findings resolved (powered by Microsoft Defender Vulnerability Management) | Azure running container images should have vulnerabilities resolved (powered by Microsoft Defender Vulnerability Management). <br /><br />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 |
48+
49+
Container image scan powered by Microsoft Defender Vulnerability Management now also incurs charges according to [plan pricing](https://azure.microsoft.com/pricing/details/defender-for-cloud/?v=17.23h#pricing).
50+
51+
> [!NOTE]
52+
> Images scanned both by our container VA offering powered by Qualys and Container VA offering powered by Microsoft Defender Vulnerability Management will only be billed once.
53+
54+
The following Qualys recommendations for Containers Vulnerability Assessment are renamed and continue to be available for customers who enabled Defender for Containers on any of their subscriptions prior to this release. New customers onboarding Defender for Containers after this release will only see the new Container vulnerability assessment recommendations powered by Microsoft Defender Vulnerability Management.
55+
56+
| Current recommendation name | New recommendation name | Description | Assessment key |
57+
| ------------------------------------------------------------ | ------------------------------------------------------------ | ------------------------------------------------------------ | ------------------------------------ |
58+
| Container registry images should have vulnerability findings resolved (powered by Qualys) | Azure registry container images should have vulnerabilities resolved (powered by Qualys) | Container image vulnerability assessment scans your registry 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. | dbd0cb49-b563-45e7-9724-889e799fa648 |
59+
| Running container images should have vulnerability findings resolved (powered by Qualys) | Azure running container images should have vulnerabilities resolved - (powered by Qualys) | 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. | 41503391-efa5-47ee-9282-4eff6131462 |
60+
61+
## Public preview of Windows support for Containers Vulnerability Assessment powered by Microsoft Defender Vulnerability Management
62+
63+
December 14, 2023
64+
65+
Support for Windows images was released in public preview as part of Vulnerability assessment (VA) powered by Microsoft Defender Vulnerability Management for Azure container registries and Azure Kubernetes Services.
66+
3467
### Retirement of AWS container vulnerability assessment powered by Trivy
3568

3669
December 13, 2023

articles/defender-for-cloud/transition-to-defender-vulnerability-management.md

Lines changed: 17 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -9,28 +9,37 @@ ms.date: 11/23/2023
99

1010
Microsoft Defender for Cloud is unifying all vulnerability assessment solutions to utilize the Microsoft Defender Vulnerability Management vulnerability scanner.
1111

12-
Microsoft Defender Vulnerability Management integrates across many cloud native use cases, such as containers build/runtime scenarios, agentless scanning for Virtual Machines (VM) and more.
12+
Microsoft Defender Vulnerability Management integrates across many cloud native use cases, such as containers ship and runtime scenarios. As part of this change, we're retiring our built-in vulnerability assessments offering powered by Qualys.
1313

14-
## Step 1: Enable Microsoft Defender Vulnerability Management scanning for container images
14+
> [!IMPORTANT]
15+
> The Defender for Cloud Containers Vulnerability Assessment powered by Qualys is now on a retirement path completing on **March 1st, 2024**.
16+
>
17+
> Customers that onboarded at least one subscription to Defender for Containers prior to **November 15th, 2023** can to continue to use Container Vulnerability Assessment powered by Qualys until **March 1st, 2024**.
18+
>
19+
> For more information about the change, see see [Defender for Cloud unifies Vulnerability Assessment solution powered by Microsoft Defender Vulnerability Management](https://techcommunity.microsoft.com/t5/microsoft-defender-for-cloud/defender-for-cloud-unified-vulnerability-assessment-powered-by/ba-p/3990112).
20+
21+
If you're currently using the built vulnerability assessment solution powered by Qualys, start planning for the upcoming deprecations by following the steps on this page.
22+
23+
## Step 1: Verify that scanning is enabled
1524

1625
Container vulnerability assessment scanning powered by Microsoft Defender Vulnerability Management is enabled by default for Defender for Containers, Defender for Container Registries (deprecated) and Defender Cloud Security Posture Management. Organizations that disabled it need to re-enable the **Agentless container vulnerability assessment** toggle in one of the plans. It reflects automatically to any of the mentioned plans enabled.
1726

1827
:::image type="content" source="media/transition-to-defender-vulnerability-management/enable-agentless-container-vulnerability-assessment.png" alt-text="Screenshot of enabling “Agentless container vulnerability assessment” in settings." lightbox="media/transition-to-defender-vulnerability-management/enable-agentless-container-vulnerability-assessment.png":::
1928

20-
For more information on enabling Microsoft Defender Vulnerability Management scanning, see [Enable vulnerability assessment in Azure powered by Microsoft Defender Vulnerability Management](enable-vulnerability-assessment.md).
29+
For more information on enabling Microsoft Defender Vulnerability Management scanning, see [Enable vulnerability assessment powered by Microsoft Defender Vulnerability Management](enable-vulnerability-assessment.md).
2130

22-
## Step 2: Transition to only view Microsoft Defender Vulnerability Management recommendations
31+
## Step 2: Disable Qualys recommendations
2332

24-
If your organization is ready to transition to container vulnerability assessment scanning powered by Microsoft Defender Vulnerability Management and no longer receive results from the Qualys recommendations, you can go ahead and disable the recommendations reporting on Qualys scanning results. Following are recommendation names and assessment keys to be referenced throughout this guide.
33+
If your organization is ready to transition to container vulnerability assessment scanning powered by Microsoft Defender Vulnerability Management and no longer receive results from the Qualys recommendations, you can go ahead and disable the recommendations reporting on Qualys scanning results. Following are the recommendation names and assessment keys referenced throughout this guide.
2534

26-
### Qualys recommendations and Assessment Keys
35+
### Qualys recommendations and assessment Keys
2736

2837
| Recommendation | Description | Assessment Key
2938
|--|--|--|
3039
| [Azure registry container images should have vulnerability findings resolved (powered by Qualys)](https://ms.portal.azure.com/#view/Microsoft_Azure_Security_CloudNativeCompute/ContainerRegistryRecommendationDetailsBlade/assessmentKey/dbd0cb49-b563-45e7-9724-889e799fa648)| Container image vulnerability assessment scans your registry 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. | dbd0cb49-b563-45e7-9724-889e799fa648 |
3140
| [Azure running container images should have vulnerability findings resolved (powered by Qualys)](https://ms.portal.azure.com/#view/Microsoft_Azure_Security_CloudNativeCompute/KubernetesRuntimeVisibilityRecommendationDetailsBlade/assessmentKey/41503391-efa5-47ee-9282-4eff6131462c)| 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. | 41503391-efa5-47ee-9282-4eff6131462c |
3241

33-
### Microsoft Defender Vulnerability Management recommendations and Assessment Keys
42+
### Microsoft Defender Vulnerability Management recommendations and assessment keys
3443

3544
| Recommendation | Description | Assessment Key
3645
|--|--|--|
@@ -268,7 +277,7 @@ The workbook provides results from both Qualys and Microsoft Defender Vulnerabil
268277

269278
:::image type="content" source="media/transition-to-defender-vulnerability-management/exploitable-vulnerabilities-dashboard.png" alt-text="Screenshot of exploitable vulnerabilities dashboard." lightbox="media/transition-to-defender-vulnerability-management/exploitable-vulnerabilities-dashboard.png":::
270279

271-
- **Additional ARG queries**: You can use this workbook to view additional examples of how to query ARG data between Qualys and Microsoft Defender Vulnerability Management. For more information on how to edit workbooks, see [Workbooks gallery in Microsoft Defender for Cloud]( custom-dashboards-azure-workbooks.md#workbooks-gallery-in-microsoft-defender-for-cloud).
280+
- **Additional ARG queries**: You can use this workbook to view more examples of how to query ARG data between Qualys and Microsoft Defender Vulnerability Management. For more information on how to edit workbooks, see [Workbooks gallery in Microsoft Defender for Cloud]( custom-dashboards-azure-workbooks.md#workbooks-gallery-in-microsoft-defender-for-cloud).
272281

273282
## Next steps
274283

0 commit comments

Comments
 (0)