Blog Post

Microsoft Defender Vulnerability Management Blog
2 MIN READ

Leverage authenticated scans to prevent attacks on your Windows devices

Yossi Basha's avatar
Yossi Basha
Icon for Microsoft rankMicrosoft
Jan 26, 2023

Many of our customers face challenges installing agents on all of their devices and in some cases, not all Windows-based devices support the agent if they are using older versions of Windows.

To combat these challenges, we’re excited to share a new capability within Microsoft Defender Vulnerability Management to remotely scan Windows-based devices that do not have agents installed. Authenticated scans for Windows provide the ability to remotely target by IP\range or hostname and scan Windows services by equipping the tool with credentials to remotely access the machines. This is applicable for devices that do not have the Defender Vulnerability Management or Defender for Endpoint agent deployed so organizations like yours can get complete vulnerability assessment coverage without reliance on an agent. Defender Vulnerability Management add-on and standalone customers can take advantage of this new feature today.

 

Along with the release of the ability to remotely scan Windows devices, we have made updates and added new functionality to the remote scan capability (some of which are already available for network devices).

 

One place for managing authenticated scans

 

You can access authenticated scans in the Microsoft 365 Defender Portal through Settings > Device Discovery. This makes managing discovery and scanning of non-Microsoft Defender for Endpoint onboarded devices easier under the same location.

 

Create an authenticated scan for Windows devices

 

Once in the authenticated scan section, select “add new scan” to create an authenticated scan for Windows.

New fields for authenticated scans allows for customization to fully support your organization's needs

 

  • Define scan interval – provides ability to configure an interval per authenticated scan or set it to run once. 
  • Windows authenticated scan gMSA support - For better security we have moved to using a  Account (gMSA) instead of username\password. 
  • Define scan targets by hostname or upload a CSV
  • Azure Key Vault support
  • Scan definition API improvements
  • Scan history for an ability to better understand scans

 

Set up your scanner device and devices to be scanned

To set up your scanner device and the devices to be scanned, you’ll need to use a gMSA account. To create a gMSA for scanning please see create a scanning account in our documentation.

 

The gMSA is then used by the scanning device to authenticate and remotely access the devices to be scanned. Further configurations for the gMSA account are also required on the devices to be scanned. For more information, see devices to be scanned section in our documentation.

 

We hope you enjoy this new feature. See below for more information about authenticated scans for Windows:

__

Microsoft Defender Vulnerability Management is in public preview. Explore premium capabilities of Microsoft Defender Vulnerability Management such as this one and more by signing up for a free trial of Defender Vulnerability Management add-on and standalone here. 

Updated Jan 26, 2023
Version 3.0
  • Hank1080's avatar
    Hank1080
    Copper Contributor

    Is anyone else getting this error. My scans were running perfectly but since 3day ago I can't view my old scans or create a new one all am getting is this error.

  • dangibbons's avatar
    dangibbons
    Copper Contributor

    Is this feature available with an E5 license? Or does it require additional licensing? Thanks

  • Hi dangibbonsDefender Vulnerability Management add-on and standalone customers can take advantage of this new feature.
    Microsoft Defender Vulnerability Management is in public preview. Explore premium capabilities of Microsoft Defender Vulnerability Management such as this one and more by signing up for a free trial of Defender Vulnerability Management add-on and standalone here. 

  • Dean_Gross's avatar
    Dean_Gross
    Silver Contributor

    dangibbons this is another example of the new trend to provide additional security and compliance services that are not included in the E5 licensing. There is now the Oauth add-on for MDCA, this VulnManagement, a few new options in Compliance (Priva and some others), Entra (Permissions Management and Workload Identities) and some others that I am forgetting.

     

    It looks like they are laying the groundwork for an E6 or 7 bundle. 

  • JLaughlin's avatar
    JLaughlin
    Copper Contributor

    What needs to be licensed, though? Does every discovered network device need to have a license tied to it?

  • VejaGCT's avatar
    VejaGCT
    Copper Contributor

    Hi 

    I have tried setting this up, but I have a challenge with the last step when I test the scan I can't seem to connect to my targeted remote devices.

    I have opened a support ticket, but we have not found the reason why it fails would really appreciate any assistance. 

    thanks.

  • jtheum's avatar
    jtheum
    Copper Contributor

    Hello all, does anyone know if this scanner can only scan Entra ID joined devices? from the documentations that doesn't seem to be the case but, I was also wondering how others experience with it has been when you compare it to a tool like the nessus scanner.