(Lack of) Patch Management Highlighted in US Congress

“Cloud Musings” Named A “Top 50 Blog”

By G C Network | August 27, 2010

My appreciation and thanks goes out to Jeremy Geelan for including “Cloud Musings” on his list of the Top 50 Cloud Computing Blogs. Thanks is also in order for “HighTechDad”…

Will Oracle Buy Informatica?

By G C Network | August 25, 2010

According to 1,250 ERP Software Advice readers that will be Oracle’s next acquisition. Terradata came in a close second in this race, suggesting that Oracle will “…play it safe next time…

What’s Next For Oracle?

By G C Network | August 14, 2010

Watching Larry Ellison and Oracle over the years as it has morphed itself is a real study in market dynamics.  It’s transformation from database company through middleware provider to now…

Enterprise Architecture Enables Innovation: Melvin Greer, Lockheed Martin

By G C Network | August 11, 2010

Earlier this week, my good fried and NCOIC colleage, Melvin Greer was interviewed by Rutrell Yasin of Government Computer News. In the interview, Mel focused on the importantance of entrprise…

Are You A Cloud Architect? NJVC Needs YOU!!

By G C Network | July 31, 2010

If you are a cloud computing architect, have I got news for you!  NJVC, one of the largest IT solutions providers supporting the U.S. Department of Defense (DoD), is building…

“Army Private Cloud” RFP Released

By G C Network | July 28, 2010

Last week the US Army released  a procurement solicitation for the Army Private Cloud.  This $249M solicitation calls for a 1-year base period with four, 1-year options. Department of the…

Cloud Musings Direct Launches

By G C Network | July 15, 2010

In response to request, the inaugural “Cloud Musings Direct” newsletter was launched this week.  This bi-weekly electronic newsletter will highlight important government cloud computing industry trends and events.  If you…

CloudExpo Europe 2010: Not Your Father’s Prague

By G C Network | June 30, 2010

When my good friend Jeremy Geelan invited me to speak at CloudExpo Europe in Prague, Czech Republic my imagination went into overdrive.  Being a child of the 60’s and a…

NCOIC Plenary Highlights Collaboration and Interoperability

By G C Network | June 29, 2010

Last week in Brussels, Belgium, the Network Centric Operations Industry Consortium highlighted it’s support of collaboration and interoperability through an information exchange session with the National Geospatial-Intelligence Agency (NGA) and…

GovLoop “Member of the Week”

By G C Network | June 22, 2010

Thank you to Radiah Givens-Nunez and GovLoop for the honor of being their Member of the Week for June 21-25, 2010. Created in 2008, GovLoop is an online social network…

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