Patching is important, and should be done regularly and as quickly as possible after the patch is released. There are exceptions; the risks associated with this should be carefully considered, and mitigations put in place.
Patching becomes more difficult as the size of the system and the number of components grows. Proper processes and documentation should be put in place to manage it, and dedicated patch management applications considered.
So, in this guide, we have discussed what patching is, what should be patched and why. We’ve outlined
some of the issues that people responsible for patching can face.
We’ve described the steps involved in a patch management strategy, and in creating both a standard
patch release and an emergency patch release.
Then we discussed what to do if you are unable to patch an asset, described virtual patching, and
the steps involved in setting up a virtual patch.
If you are wondering how best to implement patching in your organisation, contact us on 0113 733 6230.