(Lack of) Patch Management Highlighted in US Congress

March 9, 2018 / G C Network / Comments Off on (Lack of) Patch Management Highlighted in US Congress

The Endpoint Imperative: In a Software World, Hardware Does Matter

By G C Network | January 9, 2018

Hardware matters. From productivity to security to innovation, make sure your machines can keep up. Intel’s Sarah Wieskus joins The End Point Imperative: A Podcast series from Intel to discuss…

IT Transformation with Watson

By G C Network | January 5, 2018

Credit: Shutterstock by Kevin Jackson & Dez Blanchfield   IBM recently launched an exciting new project in the form of a podcast series produced and hosted Dez Blanchfield, appropriately titled the…

The Endpoint Imperative: A Form Factor Renaissance

By G C Network | December 22, 2017

Workplace expectations are changing, and along with them, the devices we use to do our jobs. In this episode of “The End Point Imperative”, Intel’s Sarah Wieskus tells us about…

Cloud Storage 2.0 Set To Dominate Market

By G C Network | December 19, 2017

The enterprise data storage marketplace is poised to become a battlefield. No longer the quiet backwater of cloud computing services, the focus of this global transition is now going from…

Top “Cloud Musings” Posts For 2017

By G C Network | December 17, 2017

    ( This content is being syndicated through multiple channels. The opinions expressed are solely those of the author and do not represent the views of GovCloud Network, GovCloud…

The Endpoint Imperative: ID’ing and Overcoming the Stumbling Blocks to Digital Transformation

By G C Network | December 6, 2017

Digital Transformation is the No 1 priority for organizations large and small. It’s imperative that IT remove any obstacles to digital transformation success – including outdated PCs and mobile devices.…

Industry Verticals Tackle Unstructured Data

By G C Network | December 1, 2017

  Organizations around the world are struggling to cope with the current data explosion. A vital characteristic of this data is that it is unstructured and represents things like email,…

The Endpoint Imperative: The Perimeter is Dead; Long Live the Perimeter!

By G C Network | November 27, 2017

Cloud, mobility and the Internet of Things have obliterated the traditional perimeter that protected organizations. The result: Higher productivity, but bigger challenges for security, data protection, and mobile device management.…

The Data Storage Explosion

By G C Network | November 25, 2017

Cloud computing innovation will power enterprise transformation in 2018.  Cloud growth is also driving a rapid rise in the storage market, exacerbating the enterprise challenge around storage cost and complexity.…

Digital Transformation Drives Mainframe’s Future

By G C Network | November 15, 2017

  Digital Transformation is amplifying mainframe as mission critical to business growth more than ever before. With 70% of the world’s corporate data and over half of the world’s enterprise…

According to the former Equifax CEO’s testimony to Congress, one of the primary causes of this now infamous data breach was the company’s failure to patch a critical vulnerability in the open source Apache Struts Web application framework. Equifax also waited a week to scan its network for apps that remained vulnerable.[1]Would you like to appear at the next Congressional hearing on patch management?

Patch management is the process of identifying, acquiring, installing, and verifying patches for products and systems. Patches not only correct security and functionality problems in software and firmware, but they also introduce new, and sometimes mandatory, capabilities into the organization’s IT environment.  It is so useful, the CERT® Coordination Center (CERT®/CC) claims that 95 percent of all network intrusions are avoidable by using proper patch management to keep systems up-to-date.
This nightmare true story and compelling endorsement from CERT®/CC, however, masks the ugly operational patch management implementation complexities. Key enterprise challenges include:
  • Timing, prioritization, and testing of patches often present conflicting requirements. Competitive prioritization of IT resources, business imperative, andbudget limitations often leave patching tasks on the back burner
  • Technical mechanisms and requirements for applying patches may also conflict and may include:
    • Software that updates itself with little or no enterprise input
    • Use of a centralized management tool
    • Third-party patch management applications
    • Negative or unknown interactions with network access control, health check functions, and other similar technologies
    • User initiated manual software updates
    • User-initiatedpatches or version upgrades
  • Typical enterprise heterogeneous environment that includes
    • Unmanaged or user managed hosts
    • Non-standard IT components that require vendor patching or cannot be patched
    • Enterprise owned assets that typically operate on non-enterprise networks
    • Smartphones, tablets, and other mobile devices
    • Patching of rehydrating virtual machines
    • Firmware updates

 

Piling up on these purely operational tasks are the change management steps associated with:
  • Maintaining current knowledge of available patches;
  • Deciding what patches are appropriate for particular systems;
  • Ensuring proper installation of patches;
  • Testing systems after installation; and
  •  Documenting all procedures and any specific configurations.

 

This challenge can also be significantly exacerbated in an IT environment that blends legacy, outsourced and cloud service provider resources. Environment heterogeneity and the sheer volume of patches released is why any patching strategy that primarily relies solely on manual implementation is untenable.

According to the SANS Institute, meeting the patch management challenge requires the creation of a patch management methodology and the automation of that methodology.[2]The methodology itself should include:
  • A detailed inventory of all hardware, operating systems, and applications that exist in the network and the creation of the process to keep the inventory up-to-date.
  • A process to identify vulnerabilities in hardware, operating systems, andapplications.
  • Risk assessment and buy-in from management and business owners.
  • A detailed procedure for testing patches before deployment.
  • A detailed process for deploying patches and service packs, as well as a process for verification of deployment.

 

As for the automation component, it should deliver an automated, comprehensive server lifecycle approach that can provision and configure software, update patches and implement configurations that can improve security and compliance across physical, virtual and cloud servers.
It should also encompass a policy-based approach with support for all major operating systems on physical servers and leading virtualization and cloud platforms. An ability to automate continuous compliance checks and remediate any security or regulatory shortcoming is also paramount. If appropriately implemented, IT Staff should be able to manage patching via a web interface. Having this feature increases server to admin ratio, enhances operational productivity, accelerates audit timelines and reduces incident response latency.
A leading solution in this space is BladeLogicServer Automation by BMC. It was specifically designed to address the dual enterprise requirements of (1) ensuring compliance with rules and regulations and (2) software patching to reduce security vulnerabilities.  In the market for over 10 years, it is a comprehensive server lifecycle automation solution that helps organizations provision and configure software, update patches and configurations to improve security and compliance across physical, virtual and cloud servers. Advanced capabilities include script automation, compliance tracking and the ability to stage and test patches before committing them. The latter feature is used to copy patch bundles to the targeted servers before maintenance windows open.The full-function suite integrates with change management systems to facilitate change record creation. Vulnerability management and remediation are automated by importing vulnerability management scan data from vendors like Qualys, Tenable and Rapid 7, and mapping the vulnerabilities back to underlying patches in BladeLogic.
Secure IT operations start with the identification and prioritization of critical vulnerabilities paired with the capability to deliver multi-tier remediation.  These reinforcing goals are why an advance patch automation solution is a “must have” for today’s modern enterprise.

This post is brought to you by BMC and IDG. The views and opinions expressed herein are those of the author and do not necessarily represent the views and opinions of BMC.
Cloud Musings

( Thank you. If you enjoyed this article, get free updates by email or RSS – © Copyright Kevin L. Jackson 2016-2018)

Follow me at https://Twitter.com/Kevin_Jackson
Posted in

G C Network

Cloud Computing

Cybersecurity