ABSTRACT
The typical way manufacturers address technological change is through the distribution of patches, software updates, and full-scale new product releases. Considering the time and expense necessary to deploy a new product release, it is no wonder companies opt to remain on their legacy systems. A new application goes into production and no one wants to touch it, fearing system downtime: unfortunately, this sometimes includes patching and vulnerability management. The typical way manufacturers address technological change is through the distribution of patches, software updates, and full-scale new product releases. Once vendor support ceases, third-party support is basically focused on keeping the software functional. There is no emphasis or concern on possible security flaws within the software. Patching is just one piece necessary for the maintenance of the foundation. Other vulnerabilities that must be corrected by means other than patching exist, much like a road that has potholes and a fallen tree branch across it.
