CMS Security Handbook: The Comprehensive Guide for WordPress®, Joomla!®, Drupal™, and Plone®

CHAPTER 7

Patching Process

If you have used a Windows desktop, then you are already familiar with the idea of patching, which Microsoft refers to as an update. These updates download automatically (assuming you have set it up to do so) on a regular basis and then are applied. This helps keep the operating system at its safest level. The patching process is built into modern versions of Windows, giving Microsoft a great method to help all Windows users stay safe.

Likewise, a similar process is built into distributions of Linux. For example, in CentOS, you use the yum command, which checks predetermined repositories for updates. If it finds them, it will ask you whether you want to download and apply them. Although this process can be automated, it's often done manually.

As you'll see in this chapter, the process of patching a CMS does not necessarily work in the same manner. In fact, most of the time (with rare exception), you must conduct this process manually. The patching process consists of a methodology to monitor, test, apply, and document. The actual application of the patch is nearly the last step in the process.