Qualys Patch Management
2026-10-28-18de7ca7 commercialThe section your link pointed to isn't on Qualys Patch Management's page any more, so we've brought you to the top.
Qualys Patch Management is a cloud-based tool that automates the discovery, prioritization, and deployment of patches across IT assets to reduce vulnerabilities.
Summary
Qualys Patch Management is a commercial vulnerability-management product delivered as part of the Qualys cloud platform, run through the same agent and console model as its other modules rather than installed as standalone software. It links vulnerability findings directly to remediation, letting a team patch, isolate, or replace a workload the moment a confirmed finding appears, and offers compensating mitigation when a patch itself isn't yet ready to ship. It's built for the people who own the patch cycle after a scan runs — vulnerability and IT operations teams working through remediation backlogs — and it extends into orchestration work like Windows 11 upgrade rollout, using patch reliability scoring drawn from deployment telemetry to decide what can go out automatically versus what needs review.
Qualys Patch Management is a cloud-based tool that automates the discovery, prioritization, and deployment of patches across IT assets to reduce vulnerabilities.
How Qualys Patch Management helps
Which confirmed vulnerability findings can be closed out without waiting for a manual patch cycle?
triggers remediation, mitigation, container image replacement, workload isolation, or firewall policy updates directly from the finding at machine speed
What should we do about a vulnerability when the vendor patch isn't ready yet?
applies a patchless compensating mitigation action to cut down the exposure window until a permanent fix ships
Which patches are safe to push automatically versus which ones need a human to look first?
scores each patch for reliability from crowd-sourced deployment sentiment and Qualys telemetry on rollback and reopen rates, letting high-reliability patches go out automatically while low-reliability ones are flagged for review
Which endpoints can move to Windows 11 with the least disruption, and which need a different path?
separates the fleet into enablement-package candidates, ISO-based feature update candidates, and direct Windows 10-to-11 upgrade candidates, and finds the matching patches or scripts for each
Did a deployed cumulative update actually finish remediating the endpoint, including the reboot?
reports the true remediation state after deployment so a team can confirm KEV deadline compliance instead of assuming success from deployment status alone
Can a specific CVE be remediated right now on the affected assets?
deploys the patch for that CVE immediately from the vulnerability finding itself, without a separate scheduling step
Screenshots
From the release notes, newest first. Click one to see it full size.Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
Five scores for Qualys Patch Management, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail Qualys Patch Management puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Website history
qualys.com, every changeQualys's home page and 40 more pages as they looked each month from August 2021 to October 2026: 155 renders, 84 changes of tagline or palette. Step through them, play them, or put any two months side by side.
Website history is included with Researcher and Business.
See plans → Already subscribed? Sign in →← → or h l a month · Shift a year · [ ] previous / next change · Space play · 1 2 3 page · T whole page · C compare · F full size
← → or h l the right month · Shift the left · S swap · W wipe · T whole page · Esc back
Rebranding timeline
Dates bound when a change appeared between captures. Possible rebrands are AI suggestions; a redesign alone does not establish a rebrand.
Coverage
Missing something? Tell us
What Qualys Patch Management connects to, runs on and detects, read from its release notes and docs. So far: 1 new vulnerability check.
1 change, tracked since Oct 28, 2026.
-
Oct 282026
new Node.js vulnerability detections (QIDs)
Rescan with Cloud Agent or Container Security and confirm the detection QIDs are closed.
Nothing first seen in this window. That doesn't mean Qualys Patch Management shipped nothing, only that we found no record of it.
How we count
Read from 5 of 8 release notes and docs updates we hold for Qualys Patch Management. "First seen" is the earliest note that names something; "last" is the latest. Our history may start partway through Qualys Patch Management's life, so an old integration can show a recent first-seen date.
Each change counts once: "added 40 checks" is one line, so the numbers measure how often coverage moves, not how big the catalogue is or how well it detects.
Releases
8 entries
No entries match these filters.
- October 20263
- September 20262
- August 20261
- July 20262
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.