Measure the whole patch path
Record when an advisory appears, when your team identifies affected assets, when a fix is approved and when it is installed. Track when the application or device is restarted if that is required.
Include vendor-managed services, containers, test environments and software bundled inside products. A patch that exists in a package repository does not protect a system that still runs an old process.
Prioritise based on evidence
Prioritise internet-facing systems and flaws with evidence of exploitation. Consider the data and service at risk. Use a supported mitigation when an immediate update is not possible and set a review date.
Keep a named owner for each exception. Do not close a patch task only because an update was scheduled or downloaded.
Verify what is running
Check the installed package or runtime version after the change. Confirm that all relevant workers and appliances loaded the update. Review service health and application logs.
Use a current asset inventory and a repeatable patch process. A server assessment can help find internet-facing systems that have no clear patch owner.
