Direct answer: "Fully patched" in a board report should never be a single number on its own. A patch percentage can hide third-party applications that Patch Tuesday doesn't cover, devices that installed an update but haven't restarted, laptops that rarely check in, applications on shared servers that nobody owns, and exceptions agreed months ago that are still open. Show the board four edges alongside the figure: what it covers, what it excludes, which devices it couldn't see, and how old the oldest exception is.
Microsoft's November security updates arrived on Patch Tuesday, 10 November, and are listed in Microsoft's Security Update Guide. In the days that follow, most IT teams produce a compliance figure, and before long it appears in a board pack as a percentage, often with the words "fully patched" nearby.
The figure is usually accurate for what it measures. The question is what it measures. Patch Tuesday covers Microsoft products. The applications that sit alongside them, and the devices the reporting can't see, are often outside the number altogether.
A board can't ask about what it isn't shown. So the job of the report is to show the edges.
Browsers, PDF readers, remote-access tools, runtimes and line-of-business applications all need patching, and none of them is covered by Microsoft's monthly release. They need their own owners, their own update sources and their own cadence. If the report only counts Microsoft updates, a strong Patch Tuesday result can sit on top of an estate full of unpatched third-party software.
Many updates aren't applied until the device restarts. A device that has downloaded and installed an update but hasn't restarted is still exposed, and depending on how compliance is measured, it can still show as patched. Servers are the usual offenders, because restarts need a window someone has to agree.
Laptops in drawers, spare devices and machines used once a month drop out of reporting because they aren't online when the data is collected. They can either disappear from the count, flattering the figure, or drag it down without explanation. Either way, the number doesn't tell the board what it needs to know.
Applications on shared servers often fall between teams. The infrastructure team patches the operating system; the application team assumes someone else handles the application. Without a named update owner, the application doesn't get patched, and nobody reports it.
Some devices and applications are deliberately excluded from patching: a system that can't be restarted during trading hours, an application that breaks on the latest version. Exceptions are legitimate. Exceptions agreed months ago, with no end date and no owner, are a risk the board hasn't been told about.
The answer isn't a longer report. It's a figure with its edges drawn in.
With those four edges, "98% compliant" becomes a statement a board can actually test. (Illustrative figure.)
Not every missing patch carries the same risk. Severity scores describe potential harm; they don't say whether a vulnerability is being used in real attacks. The US Cybersecurity and Infrastructure Security Agency publishes a Known Exploited Vulnerabilities catalogue listing vulnerabilities with evidence of active exploitation.
Check outstanding vulnerabilities against that catalogue and patch those first. In the board report, show how many known-exploited vulnerabilities remain open and for how long. That single line often says more about real exposure than the overall percentage. (For how patching fits into the wider discipline, see the difference between patch management and vulnerability management.)
Device-level reporting tells you where the gaps are. Owner-level reporting tells you who will close them. Give every application, including those on shared servers, a named update owner, include applications in the patch schedule, and report outstanding patches by owner.
Gaps stop falling between teams when every gap has a name next to it.
A useful board patch report fits on one page:
It takes no more space than a single percentage with a traffic light, and it answers the questions a board should be asking. For the programme that sits behind the report, see our patch management guide for enterprise IT teams.
We help enterprises and SMEs make patching dependable and patch reporting honest, using our Sync, Align, Optimise approach.
No. Microsoft's monthly release covers Microsoft products. Other vendors' applications, from PDF readers to remote-access tools and line-of-business software, need their own update sources, owners and schedule.
Many updates only take effect after a restart. Depending on how compliance is measured, a device that has installed an update but not restarted can be counted as compliant while it is still exposed.
A public list, maintained by the US Cybersecurity and Infrastructure Security Agency, of vulnerabilities with evidence of active exploitation. It's a practical way to decide what to patch first, whatever a vulnerability's severity score says.
The headline figure with its coverage stated, Microsoft and third-party compliance shown separately, pending restarts and unseen devices, open exclusions with the age and owner of the oldest, known-exploited vulnerabilities still open, and the trend over recent months.
Request a 30-minute discovery conversation with our team. We'll help you see what your patch percentage includes, and what it leaves out.