How it works
Patches fix known weaknesses. Good patching includes scheduling, testing, tracking, and prioritizing the highest-risk systems first.
If a device is busy, schedule maintenance rather than ignoring the update forever.
Common error
Unofficial downloads can create more risk than the vulnerability they claim to fix.
Worked example
Prioritize approved updates using exposure and consequences.
Evidence
A: internet-facing service, high-risk known flaw
B: isolated test device, low-impact flaw
C: staff laptop, routine updateInvestigate and prioritize A because of exposure and impact, using the approved risk assessment and change process. Test the update, preserve a rollback plan, deploy through trusted channels, and verify success. An urgent risk may also require a temporary approved mitigation.
Exercises
4.2.1
Why should a patch downloaded from an unverified forum not be trusted merely because it claims to fix an urgent flaw?
Show solution
The source or file may be malicious or incorrect. Obtain updates through trusted vendor or organizational channels and validate the deployment.
4.2.2
List three pieces of evidence that show a patch process is complete.
Show solution
Record the installed version or update status, verification that the targeted weakness is addressed as expected, and a successful required-workflow test. Track failed or deferred devices separately.