Share via

Fix MSFT Defender Vuln Info - STALE & OUTDATED

Michael O'Hara 0 Reputation points
2026-03-10T23:01:40.45+00:00

Just found out that the reporting of the 1900 device vulns in MSFT DEF is grossly wrong.

There are a ton of vulns that are very, very clearly stale. This would have an adverse impact on SecureScore - and that is a huge problem as that's a core Security KPI.

Will anyone from MSFT Support address this or am I at the mercy of the forum? :-)

Microsoft Security | Microsoft Defender | Microsoft Defender for Cloud

2 answers

Sort by: Most helpful
  1. Michael O'Hara 0 Reputation points
    2026-03-26T11:37:46.48+00:00

    We'll try steps recommended by Shubham - will close this for now.


  2. Shubham Sharma 12,765 Reputation points Microsoft External Staff Moderator
    2026-03-23T10:04:06.0566667+00:00

    Hello Michael O'Hara

    Thank you for reaching out to Microsoft Q&A.

    Here’s some guidance on how Defender pulls in and updates those findings, plus a few things you can try to clean up the noise:

    1. Verify your vulnerability pipeline • Make sure the Microsoft Defender for Endpoint extensions (MDE.Windows or MDE.Linux) are installed and healthy on all your machines. Defender for Cloud relies on those agents to surface vulnerability data. • Go into the Azure portal → your VM → Extensions, confirm the MDE agent is running without errors. • In Defender for Cloud, open the "Machines should have a vulnerability assessment solution" recommendation—your VMs should show up under “Healthy.”
    2. Force a fresh scan • By default, Defender Vulnerability Management re-scans every 4 hours, but you can trigger an on-demand scan from the MDE portal to grab the latest patch/CVE status. This often clears out findings that linger past the fix date.
    3. Bulk-dismiss or suppress known-good findings • If you have a batch of CVEs that truly aren’t applicable—even though Defender still flags them—you can use the Defender Vulnerability Management dashboard or API to “dismiss” or “suppress” those findings in bulk. That way they won’t impact your Secure Score. • Look for the “Vulnerability exceptions” feature in the MDE portal: you can create exception rules by CVE, package, or tag and have them automatically excluded.
    4. Validate update catalogs and definitions • Check that your machines are pulling in the latest Windows or Linux update catalogs. Sometimes a missed software repository or WSUS sync issue can leave old CVEs in play.

    Reference docs:

    • Monitor vulnerabilities using Defender Vulnerability Management https://docs.microsoft.com/azure/defender-for-cloud/deploy-vulnerability-assessment-tvm

    • Integrate Defender for Cloud with Defender for Endpoint https://docs.microsoft.com/azure/defender-for-cloud/integration-defender-for-endpoint

    • What is Defender Vulnerability Management? https://docs.microsoft.com/microsoft-365/security/defender-endpoint/next-gen-threat-and-vuln-mgt

    Let us know if the above steps help

    Thanks

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.