(Lack of) Patch Management Highlighted in US Congress

US Army Cloud Computing Class at Ft. Gordon, GA

By G C Network | June 24, 2011

A few weeks ago I had the distinct pleassue of teaching yet another US Army cloud computing class.  This time the venue was Ft. Gordon, GA and the students definitely…

78 Agency Services Identified for Cloud Transition

By G C Network | May 29, 2011

The Office of Management and Budget recently released a list of 78 projects slated for transition to cloud over the next year. The most common application, according to a FierceGovernmentIT,…

NGA Sets GEOINT Strategic Direction with Earth Builder

By G C Network | May 15, 2011

Last month Google and the National Geospatial Intelligence Agency started sharing details about their “GEOINT on Demand” collaboration. The project, named Earth Builder, was built specifically to enable NGA to…

Teleology Systems Introduces CloudeFX at DoDIIS

By G C Network | April 27, 2011

Next week at DoDIIS, NJVC will be showcasing a few of our government cloud computing partners. One of the most exciting of these is the Cloud Service Orchestration Framework by…

Cloud Computing Highlighted at DoDIIS 2011

By G C Network | April 27, 2011

Are you going to DoDIIS? Schedule for May 1-5, 2011 in Detroit, Michigan, the conference highlights the Defense Intelligence Agency’s (DIA) commitment to developing and maintaining secure and reliable networks for…

Washington DC a Cloud Computing Trendsetter!

By G C Network | April 16, 2011

A TechJournal South article last week named Washington, DC as a leading trendsetter in cloud computing. Citing a Microsoft sponsored survey, conducted by 7th Sense research, D.C. was highlighted as particullarly receptive…

Melvin Greer Cited by IBM for Cloud Computing Innovation

By G C Network | April 5, 2011

Congratulations to my good friend Melvin Greer for being awarded IBM’s first ever ACE Award!! “Melvin Greer, Lockheed Martin Senior Fellow has won IBM’s first ever Awarding Customer Excellence (ACE)…

“GovCloud: The Book” Launched at National Press Club Event

By G C Network | March 30, 2011

As many of you know, today marked the official launch of my first book – GovCloud: Cloud Computing for the Business of Government. Today’s venue was the National Press Club…

“Cloud Musings on Forbes” Launched!!

By G C Network | March 24, 2011

Today I published my first post on Forbes.com!! At the invitation of Bruce Upbin, Forbes.com editor, I will be contributing posts monthly. I see this not only as an honor,…

Tech America and INSA Form Cloud Computing Advisory Groups

By G C Network | March 6, 2011

Last week TechAmerica announced the formation of a “cloud computing commission” to advise the White House on the current plans to steer more than $20B worth of IT services toward…

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