Patch management software finds missing updates across your devices and deploys them on a schedule. What the tools actually do, the process around them, and why patching fails for organisational reasons rather than technical ones.
Patch management software discovers the devices and applications an organisation runs, identifies missing security and functional updates, and deploys them in controlled waves. Every serious breach report contains at least one system that was missing a patch published months earlier — not because nobody had the tool, but because nobody owned the schedule, the exceptions, or the servers that could not be rebooted. Patch management software solves the mechanics; the process around it decides whether patching actually happens.
The devices missing from the report matter more than the ones failing in it. An agent that stopped reporting six weeks ago looks like compliance, because a device with no findings appears clean.
Almost never because the software cannot deploy an update. It fails because a critical application is only certified on an old version, because a server cannot be rebooted without approval nobody wants to give, because third-party applications are not in scope, or because the exception granted for one quarter became permanent. Each of those is a decision, not a technical limit, which is why patch compliance belongs on the risk register with a named owner rather than in the IT team's private backlog.
Ettex Records can hold the parts the tooling does not: the exception register with owners and expiry dates, the list of systems with special handling, and a monthly compliance figure per platform. Keeping that alongside the asset inventory means the awkward question — which devices are not covered at all — has an answer.
Set the cycle by severity rather than by calendar habit: critical vulnerabilities in days, routine updates monthly. What matters is a published target and measurement against it.
For workstations, largely yes, with rings and a pause mechanism. For servers and specialist equipment, test first — the cost of an unplanned outage can exceed the risk the patch removes.
Patch management deploys updates. Vulnerability management finds and prioritises weaknesses, some of which have no patch and need configuration changes or compensating controls instead.
Mobile device management for small business does not require an enterprise platform. What to enforce on phones and laptops, how to handle personal devices, and what to do before someone leaves.
Space management is the discipline of matching the property you pay for to the way it is used. What to measure, how to read occupancy data honestly, and what to do before signing or renewing a lease.
Contractor management is the process of approving contractors, checking their documents stay valid, and controlling what they do on site. What to verify, how to stop expired insurance slipping through, and what to record.