Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated
Patch management is the routine of applying fix programs completely and on time. A patch is an update distributed to close a hole that has been found. It is not a single task. Its feature is that it keeps a cycle running: finding, deciding the order, applying, and checking.
How does patch management work?
Even if a car recall notice arrives, the faulty part stays in the car unless you take it to the dealer. Receiving the notice, deciding the order, actually fixing, and confirming it is fixed together make one job.
NIST's SP 800-40 Rev. 4 places patch management as an important part of the preventive maintenance that keeps computer technology in good order, and advises having a strategy for the organization. The document also touches on a gap in awareness of the value of patching between business leaders and technology and security staff.
OWASP Top 10:2021 gives, as an example of a risky state, postponing updates by bundling them into a monthly or quarterly routine. Among its measures is having a patch management process. Where gaps in updating arise is explained on the unpatched software page.
Why does patch management matter?
A hole stays where it is after a fix is out unless it is applied. MIC's material explains that vulnerabilities are hard to prevent completely and new ones keep being found, so you need to keep checking update information and apply fixes as early as possible. A published vulnerability gets a CVE number, which makes it easier to look up whether it applies to the software you use.
In practice, first keep a list of the software and parts you use. Next, check published vulnerability information at set intervals. The score of CVSS, which shows severity, is material for deciding what to apply first.
After applying, check that the site works correctly. For parts you cannot patch, OWASP says to consider a virtual patch, an emergency step before a fixed version appears. Writing down the person in charge, the deadline, and how exceptions are handled makes the work less likely to stall.
To go over how updates are handled on your site, contact us.
Related terms
- Vulnerability: a weakness in a program or setting that can become an entry for attack.
- CVE: a common number given to a published vulnerability.
- CVSS: a score showing how severe a vulnerability is.
- Virtual patch: an emergency step that blocks only the traffic exploiting a hole until a fixed version exists.
- Zero-day: an attack on a hole before a fix has been distributed.
Next step
How updates get missed, and what to check, is on the unpatched software page. Preparation against hacking in general is in hacking measures. The free URL check shows only what is visible from outside. For reviewing how you run updates, contact us.
Frequently asked questions
Can applying a patch stop the site from working?
It can. OWASP also says developers should check that the updated parts work correctly. Before applying to production, try it in a test environment, or with a backup taken.
How do we protect against a hole before a patch is out?
Until a fix comes out, protect temporarily with a virtual patch that blocks traffic exploiting the hole, or similar. MIC's material advises checking the content of the published vulnerability and avoiding dangerous operations. Apply the fix promptly once it is out.
Frequently asked questions
Can applying a patch stop the site from working?
It can. OWASP also says developers should check that the updated parts work correctly. Before applying to production, try it in a test environment, or with a backup taken.
How do we protect against a hole before a patch is out?
Until a fix comes out, protect temporarily with a virtual patch that blocks traffic exploiting the hole, or similar. MIC's material advises checking the content of the published vulnerability and avoiding dangerous operations. Apply the fix promptly once it is out.