Skip to content

Windows patch level

Windows hosts are common in industrial plants: engineering workstations, historians, HMI servers, domain controllers. They get a CVE list of their own every month, and generic CVE matching handles them badly.

The problem with matching Windows by name

Many CVE records list a Windows release ("Windows Server 2019") with no build limit. Matched by name, every Windows Server 2019 host would show every such CVE forever, even after it installed the update that fixes them. That is thousands of findings that do not apply.

What BreachSpider does instead

Microsoft publishes, for every CVE and every Windows build line, the fixed build and the update (KB) that delivers it. BreachSpider holds that data (about 235,000 fix records on 2026-11-08) and decides each CVE per host:

Windows family How a CVE is decided
Cumulative Windows (Windows 10, Windows 11, Server 2016 and later) The host's full build (10.0.17763.6189) is compared with Microsoft's fixed build for that CVE on that build line. At or above means patched; below means open
Older Windows (Windows 7, Server 2008 R2, Server 2012 R2) The installed updates are checked against the fix KB. A later monthly rollup, or a KB Microsoft lists as replacing the fix, also counts. For CVEs published after end of support, enrollment in Extended Security Updates decides
Build and update list disagree Needs review. It is never guessed
No build, or just "Windows" Not patch-resolved; the host stays at product level, and the result says what to send

The result for each host is a count of open, patched and needs review CVEs, each open CVE with its fixed build, its KB and the Microsoft source, and the update that closes the most.

What you need to send

The host's product name, edition, full build (with the update revision, the last number) and architecture, plus installed updates for older Windows. Never a host name, IP address, MAC address or serial number: BreachSpider refuses those. The fields and the collection commands are in Windows patch level (API v2).

Two ways to use it

  • Stored: hosts are kept in your organization with history, and appear on the Windows screen and in reports (POST /api/v2/assets/correlate, needs a write key).
  • Stateless: nothing about the hosts is stored (POST /api/v2/assets/check-windows). This is what the SDK's bs.windows.check() and the MCP tool check_windows_host use.

Why the update that closes the most matters

Cumulative updates include all earlier fixes. The engine computes the update that closes the most CVEs over every update, not only the most recent one. On a real host this moved the answer from an older update that closed 87 CVEs to the latest cumulative update, which closed 750.