Skip to content

Commit 0641674

Browse files
author
David Curwin
committed
remove deprecation
1 parent c1609a9 commit 0641674

File tree

4 files changed

+5
-39
lines changed

4 files changed

+5
-39
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 (Deprecated)
599+
- name: Vulnerability assessment for Azure powered by Qualys
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/defender-for-containers-vulnerability-assessment-azure.md

Lines changed: 3 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -1,24 +1,14 @@
11
---
2-
title: Vulnerability assessment for Azure powered by Qualys (Deprecated)
2+
title: Vulnerability assessment for Azure powered by Qualys
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
6-
ms.date: 12/14/2023
6+
ms.date: 12/19/2023
77
ms.topic: how-to
88
ms.custom: ignite-2022, build-2023
99
---
1010

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).
11+
# Vulnerability assessment for Azure powered by Qualys
2212

2313
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.
2414

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

Lines changed: 1 addition & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -9,16 +9,7 @@ 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 ship and runtime scenarios. As part of this change, we're retiring our built-in vulnerability assessments offering powered by Qualys.
13-
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.
12+
Microsoft Defender Vulnerability Management integrates across many cloud native use cases, such as containers ship and runtime scenarios.
2213

2314
## Step 1: Verify that scanning is enabled
2415

articles/defender-for-cloud/upcoming-changes.md

Lines changed: 0 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,6 @@ If you're looking for the latest release notes, you can find them in the [What's
2525

2626
| Planned change | Announcement date | Estimated date for change |
2727
|--|--|--|
28-
| [Deprecation of the Defender for Cloud Containers Vulnerability Assessment powered by Qualys](#deprecation-of-the-defender-for-cloud-containers-vulnerability-assessment-powered-by-qualys) | December 19, 2023 | March 2024 |
2928
| [Deprecation of two DevOps security recommendations](#deprecation-of-two-devops-security-recommendations) | November 30, 2023 | January 2024 |
3029
(#public-preview-of-windows-support-for-containers-vulnerability-assessment-powered-by-microsoft-defender-vulnerability-management) | November 27, 2023 | December 2023 |
3130
| [Consolidation of Defender for Cloud's Service Level 2 names](#consolidation-of-defender-for-clouds-service-level-2-names) | November 1, 2023 | December 2023 |
@@ -39,20 +38,6 @@ If you're looking for the latest release notes, you can find them in the [What's
3938
| [Deprecating two security incidents](#deprecating-two-security-incidents) | | November 2023 |
4039
| [Defender for Cloud plan and strategy for the Log Analytics agent deprecation](#defender-for-cloud-plan-and-strategy-for-the-log-analytics-agent-deprecation) | | August 2024 |
4140

42-
## Deprecation of the Defender for Cloud Containers Vulnerability Assessment powered by Qualys
43-
44-
**Announcement date: December 19, 2023**
45-
46-
**Estimated date for change: March 2024**
47-
48-
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).
49-
50-
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).
51-
52-
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).
53-
54-
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).
55-
5641
## Deprecation of two DevOps security recommendations
5742

5843
**Announcement date: November 30, 2023**

0 commit comments

Comments
 (0)