Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is Qualys VMDR?

Qualys VMDR is a cloud vulnerability management platform that combines asset discovery, scanning, risk-based prioritisation, and patch deployment in a single workflow.

Illustration for the cybersecurity term Qualys VMDR
Home / Blog / Cybersecurity Terms / What Is Qualys VMDR?
17 November 2026

What Is Qualys VMDR?

What Is Qualys VMDR?

Qualys VMDR stands for Vulnerability Management, Detection and Response. It is a software-as-a-service platform that discovers what you own, scans it for weaknesses, ranks the findings by actual risk rather than raw severity, and then deploys the patches. The name describes an intent as much as a product: close the loop between finding a problem and fixing it, inside one console.

Qualys has been running cloud-based scanning since 1999, and VMDR is the current packaging of that work. Competitors occupy the same space, notably Tenable and Rapid7, while open-source users typically run OpenVAS instead.

Collecting the Data

The platform depends on sensors, and the choice of sensor usually determines how good the results are.

SensorWhere it fits
Cloud AgentInstalled on endpoints and servers; reports continuously and works wherever the device is
Scanner applianceVirtual or physical, for authenticated and unauthenticated scanning inside a network
External scannersQualys-hosted, for internet-facing assets and PCI scanning
Passive sensorWatches network traffic to find devices that no scan reaches
Cloud connectorsReads AWS, Azure, and Google Cloud inventory through provider APIs
Container sensorAssesses images in registries and running containers

The agent model is the one that changed how most organisations work. A home-based laptop that never connects to the corporate network still reports its patch state, which was the gap that traditional scheduled scanning could never close.

QIDs and TruRisk

Qualys identifies each check by its own QID rather than only by CVE, because a single QID may cover several CVEs or a configuration issue that has no CVE at all. Reports therefore reference both, and automation that matches only on CVE will miss findings.

Prioritisation uses TruRisk, which blends the CVSS base score with exploit availability, malware and ransomware association, threat intelligence on active exploitation, and the criticality you assign to the asset. The practical effect is that a list of 4,000 findings shrinks to a few dozen that genuinely need attention this week. That matters because CVSS alone is a poor queue: a high proportion of published vulnerabilities are never exploited, while a handful are weaponised within days.

The Response Half

The patch management module turns a finding into a deployment job, mapping vulnerabilities to the specific patch that resolves them and pushing it through the same agent that reported the issue. Where patching is not possible, the platform supports documented exceptions with expiry dates, which is what auditors ask for.

Integration matters more than the console. Most organisations push findings into ServiceNow or Jira so remediation runs through normal change processes, and feed data to a SIEM for correlation with detection telemetry.

UK Compliance Angles

Two use cases come up repeatedly with UK clients. Qualys is a PCI Approved Scanning Vendor, so external quarterly scans performed through the platform produce the attestation that PCI DSS requires, which self-hosted scanners cannot. For Cyber Essentials Plus, authenticated agent data evidences that devices are patched within the required window and that unsupported software has been removed, which makes assessment considerably less painful than collecting screenshots.

Organisations under the NIS Regulations or working to ISO 27001 use the platform’s historical reporting to demonstrate that vulnerability management is continuous rather than annual. Note the data protection point: the platform processes asset and configuration data in Qualys-operated cloud regions, so confirm which region your subscription uses and record the transfer position in your UK GDPR documentation.

What It Does Not Do

VMDR finds known issues at scale. It does not find flaws in your own application logic, broken access control between user roles, or chained weaknesses that only matter in combination. No scanner does. It will also report findings that are not exploitable in your architecture, which is why triage still needs a person who understands the environment.

Treat the platform as the continuous layer and penetration testing as the periodic depth check. Our Continuous Vulnerability Scanning Services operate platforms of this kind on behalf of clients and convert the output into a prioritised remediation plan rather than another dashboard.

FAQ – Frequently Asked Questions

What Is the Difference Between a QID and a CVE?

A CVE is a public identifier for a specific vulnerability, assigned by the CVE programme. A QID is Qualys’ own identifier for a detection check. One QID can map to several CVEs, and some QIDs cover configuration weaknesses or missing hardening that have no CVE at all. Reporting and automation should handle both identifiers rather than assuming they match.

Do I Need Cloud Agents or Scanners?

Most organisations run both. Agents give continuous coverage of laptops and servers wherever they are, including remote workers who rarely touch the corporate network, and they provide authenticated data without credential management. Scanner appliances still matter for devices that cannot take an agent, such as network equipment, printers, and operational technology, and for external perimeter testing.

Can Qualys VMDR Satisfy PCI DSS Scanning Requirements?

Yes for external scanning, because Qualys is a PCI Approved Scanning Vendor and the platform produces the attestation reports the standard requires each quarter. Internal scanning and segmentation testing have separate requirements, and PCI DSS also expects annual penetration testing, so the platform covers part of the obligation rather than all of it.

How Does TruRisk Differ from CVSS?

CVSS describes the technical severity of a vulnerability in the abstract. TruRisk combines that score with real-world signals such as whether working exploit code exists, whether ransomware operators are using it, and how important the affected asset is to your business. The result is a queue that reflects likelihood as well as impact, which usually shortens the urgent list dramatically.

Related Terms

You May Be Interested In These

What Is a Self-Signed Certificate?

Cybersecurity Terms

17 November 2026

What Is a Self-Signed Certificate?

Read More
What Are Crisis Communication Templates?

Cybersecurity Terms

17 November 2026

What Are Crisis Communication Templates?

Read More