Use more than a severity score
A vendor severity score helps teams compare risk, but it does not show whether a system meets the advisory’s preconditions. Check internet exposure, enabled features, data access and business role.
For example, a vendor may say an edge appliance is affected in every configuration, while other findings apply only when a named service is enabled. Keep those distinctions in the work plan.
Assign an owner and a deadline
For each affected asset, record its owner, current build, fixed build, maintenance window and validation steps. Prioritize systems that are internet-facing or support sign-in and remote access.
If a patch must wait, record the reason, temporary access controls and the person who will review the decision.
Verify completion with evidence
Check the installed version after the change and test the business service. A completed deployment task is not enough if a standby node or offline device was missed.
Keep the evidence with the asset record. Use the same process for phones, application runtimes and network appliances.
