Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Five Essential Criteria for Effective Patch Management

DZone's Guide to

Five Essential Criteria for Effective Patch Management

Keeping track of the patches that come out for all your applications and operating systems would be a full-time job. Learn how to automate the process.

· Security Zone
Free Resource

Discover an in-depth knowledge about the different kinds of iOS hacking tools and techniques with the free iOS Hacking Guide from Security Innovation.

The WannaCry ransomware attack, which was one of the largest cyber attacks faced recently, was based on the exploit of a Windows OS vulnerability. Just a couple of months earlier, Microsoft had released patches in its MS 17-010 security update. This ransomware that spread across hundreds of countries and infected thousands of computers could have been blocked if appropriate patches had been applied in a timely manner.

The WannaCry ransomware typically targeted older versions of the Windows operating systems, and Microsoft had stopped support for these some time back and had advised those users to upgrade to the latest Windows operating system – Windows 10. However, due to many reasons, some valid and some invalid, enterprises did not upgrade to Windows 10.

The Reasons Include:

  • Necessary upgrades of hardware which requires considerable capital investment.
  • Compatibility with existing software applications.
  • Fear of performance of the new OS.
  • Usage of unlicensed software.

However, the implications of the WannaCry ransomware attack – the ransom demand, loss of data, business down time and loss of reputation – has highlighted the importance of patch management. And a namesake patch-management system will not serve the purpose. It must be effective.

1. Versatility

The patch-management system must be compatible with multiple operating systems, applications and endpoint devices. Many types of endpoint devices are used by employees in an enterprise. Linux, Windows, Mac, and Android OSs are used in devices. Further, various third-party applications, antivirus software, etc., are used. The patch-management system must be able to manage the patches on these entities.

2. Effective Tracking

OS vendors and application vendors release updated patches from time to time or as hotfixes due to a critical emergency such as a malware outbreak. The patch-management system must check out the availability of patches for the OSs, and other applications, and download them on to the centralized management server, test them in a simulated environment for compatibility issues and then promptly roll them out to the endpoints. It is very important that the system regularly checks for availability of patches. The more frequently it does, the safer the endpoints and enterprise network become.

3. Endpoint Monitoring

All endpoints must be continuously monitored and status of their patches must be updated with the patch management server. The status must be available in real-time on the management dashboard. Whenever a new patch has been downloaded onto the management server, the endpoint must check the server for availability of new patches and immediately initiate installation of those patch updates.

4. Patch Status Monitoring

Even after deployment of the patch, the patch-management system must keep continuously monitoring the patch requirements and ensure that the endpoints are always secured with the latest patches.

5. Adherence to Regulatory Requirements

Based on regulatory requirements, compliance to necessary and defined policies must be adhered to, constantly.

Ensuring the above-mentioned criteria can ensure effective patch-management throughout the enterprise IT systems.

Learn about the importance of a strong culture of cybersecurity, and examine key activities for building – or improving – that culture within your organization.

Topics:
network security ,security ,patching ,vulnerabilites

Published at DZone with permission of Ashraf Ali. See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}