Microsoft Defender Vulnerability Management is used by companies that don't want to share their data and identities outside the company.
I am using Microsoft Threat Intelligence Vulnerability Management for customers; it's only within customer environments. We also discussed attack surface reduction and managing Defender Endpoint and MDA solutions for our customers.
The solutions we utilize are capable of detecting risks even when users are not connected to the corporate network. We are using DC sync and AD hybrid projects, along with Defender for Identities and Defender Cloud App, which was previously known as Cloud App Security; we have also used Cloud Access Security Broker for shadow IT scenarios.
I can provide an example of how risk creation affects my work. Microsoft 365 E5, as well as Microsoft 365 E3 and other packages such as Defender for Endpoint Plan 1 or Plan 2, and Windows 10 or Office 365 E3, present substantial capabilities for the next generation available for our customers. We also discuss components such as Azure Security Center, which influences vulnerability and overall security strategy.
My customers utilize agent-based scans; it's primarily agent-based. Assessing scans across cloud workloads is achieved through proactive security; all capabilities are effectively utilized in agent-based scenarios.