"Patches" se usa más que "mejoras" o "correcciones"

La normativa de manejo de parches/actualizaciones al software de clientes consiste en una serie de reglas que se deben cumplir respecto a la identificación, los equipos involucrados, la historia de los parches, cumplimiento de viabilidad, seguridad y otros temas de cumplimiento.

Microsoft Environment Using Desktop Patch Management-2009
Microsoft System Center Configuration Manager 2012 Beta 2 helps IT empower people to use the devices and applications they need to be productive, while maintaining corporate compliance and control. The boundaries between work and life have blurred to where people expect reliable, consistent access to corporate services from wherever they are, on any device they're using. Using System Center Configuration Manager 2012, organizations can:

· Empower people to be productive from anywhere on whatever device they choose. This includes the wide range of devices that connect to Exchange ActiveSync, including Windows Phone, Symbian, iOS, and Android-based devices. Through the new application model, the best application experience can be delivered to the user based on their identity, their device, and their connection.

· Streamline operations with a unified infrastructure that integrates client management and protection across mobile, physical, and virtual environments. Improved capabilities such as Forefront Endpoint Protection integration, role based administration, and virtualization scenario support will simplify both infrastructure and processes for IT.

organisational efficiency for IT with improved visibility and enforcement options for maintaining system compliance. This means fewer mouse clicks to accomplish tasks and higher degrees of automation in activities such as patch management and settings enforcement<b/>.


--------------------------------------------------
Note added at 1 day11 hrs (2014-11-11 22:26:18 GMT)
--------------------------------------------------

Patch management
A few years ago, patch management was barely a blip on the radar screens of most security and IT personnel. 'Install and forget' was a fairly common practice; once deployed, many systems were infrequently or never updated. Obviously, for a number of reasons, this approach is no longer an option. The rise of widespread worms and malicious code targeting known vulnerabilities on unpatched systems, and the resultant downtime and expense they bring, is probably the biggest reason so many organizations are focusing on patch management. Along with these threats, increasing concern around governance and regulatory compliance (e.g. HIPAA, Sarbanes-Oxley) has pushed enterprises to gain better control and oversight of their information assets. Add in increasingly interconnected partners and customers and the rise of broadband connections and remote workers, and you have the perfect storm that has thrust patch management to the forefront of many organizations' list of security priorities


--------------------------------------------------
Note added at 1 day11 hrs (2014-11-11 22:28:22 GMT)
--------------------------------------------------

It's obvious that patch management is a critical issue. What is also clear is the main objective of a patch management program: to create a consistently configured environment that is secure against known vulnerabilities in operating system and application software. Unfortunately, as with many technology-based problems, good, practical solutions aren't as apparent. Managing updates for all the applications and operating system versions used in a small company is fairly complicated, and the situation only becomes more complex
when additional platforms, availability requirements, and remote offices and workers are factored in.

http://www.patchmanagement.org/pmessentials.asp