Defender P2 Qualys Deprecation -> switch to MDE for MDVM

BartDecker-8243 175 Reputation points
2024-04-18T05:07:22.7233333+00:00

Qualys is being deprecated to be used together with Cloud Defender for Servers Plan 2.

In the documentation I read that MDVM is part of MDE, either plan 1 or plan 2.

Plan 1 has basic vulnerability scanning and p2 supplies addons to that basic vulnerability scanning such as agentless scanning and some features which can be controlled via the Microsoft security portal.

Now I wonder which plan for MDE reflects the same functionality as the Qualys which was delivered in plan 2. I ask the question because none of the add-on capabilities which are in P2 for MDVM were actually capabilities of the Qualys extension.

So my question here is if Cloud Defender for Servers Plan 1 replaces Qualys as previously supplied by the P2 plan?

Microsoft Defender for Cloud
Microsoft Defender for Cloud
An Azure service that provides threat protection for workloads running in Azure, on-premises, and in other clouds. Previously known as Azure Security Center and Azure Defender.
1,196 questions
0 comments No comments
{count} votes

Accepted answer
  1. Stanislav Zhelyazkov 21,256 Reputation points MVP
    2024-04-18T07:40:45.64+00:00

    Hi,

    The exact feature that replaces Qualys vulnerability assessment is Vulnerability assessment for machines:

    User's image

    It is available for both P1 and P2 plans. Vulnerability assessment agent details.. You can find more information about the feature here. There you will find all the documentation about it + the deprecated Qualys which was used for the same feature. There is even Common questions document. There are certain capabilities of Vulnerability assessment that are only available in P2.

    Please "Accept the answer" if the information helped you. This will help us and others in the community as well.


1 additional answer

Sort by: Most helpful
  1. BartDecker-8243 175 Reputation points
    2024-04-25T06:17:07.11+00:00

    The answer of Stanislav was validated with MS in a ticket

    1 person found this answer helpful.
    0 comments No comments