Defender for Cloud – Qualys retirement plan for Vulnerability assessment on cloud workloads

This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Community Hub.

At Ignite 2023, we unveiled a strategic decision to consolidate our vulnerability assessment engine to the cutting-edge Microsoft Defender Vulnerability Management offering. This strategic shift empowers security administrators with Microsoft's unparalleled threat intelligence, breach likelihood predictions, and business contexts, facilitating the identification, assessment, prioritization, and remediation of vulnerabilities. It also helps simplify how security admins manage an expanded attack surface, reduce overall cloud risk across the software development lifecycle, and cut remediation time and costs. To explore the advantages of our new unified vulnerability assessment offering, we recommend reviewing our dedicated blog post on the subject. 


While our collaboration with Qualys has been instrumental in providing vulnerability assessment solutions to thousands of customers, we are retiring the built-in Qualys vulnerability assessments offering to fully focus our efforts on the enhanced unified vulnerability assessments offering, thereby expediting the creation of additional value for our customers. 


Effective May 1st, 2024, the built-in Qualys offering within the Defender for Servers plan will be retired. Any new Defender for Servers customers will be offered the built-in Qualys option until January 15th, 2024. Post retirement, customers who wish to continue using Qualys can choose to subscribe to Qualys Vulnerability Management, available as Bring Your Own License (BYOL) option. Similarly, within the Defender for Containers plan, built-in Qualys offering will be retired by March 1st, 2024. All new customers will automatically benefit from Defender Vulnerability Management. 


We encourage our customers that are currently using the built-in Qualys offering to start planning for the upcoming retirement by following a few easy transition guidelines for servers and containers 

Leave a Reply

Your email address will not be published. Required fields are marked *


This site uses Akismet to reduce spam. Learn how your comment data is processed.